07 Dec, 2017

2 commits

  • Existing MC driver framework is based on MC-9.x.x flib. This patch
    migrates MC obj (DPBP, DPNI, DPRC, DPMAC etc) to use latest MC flib
    which is MC-10.3.0.

    Changes introduced due to migration:
    1. To get OBJ token, pair of create and open API replaces create APIs
    2. Pair of close and destroy APIs replaces destroy APIs
    3. For version read, get_version APIs replaces get_attributes APIs
    4. dpni_get/reset_statistics APIs replaces dpni_get/set_counter APIs
    5. Simplifies struct dpni_cfg and removes dpni_extended_cfg struct
    6. Single API dpni_get_buffer_layout/set_buffer_layout replaces
    dpni_get_rx/set_rx, tx related, tx_conf_buffer_layout related APIs.
    New API takes a queue type as an argument.
    7. Similarly dpni_get_queue/set_queue replaces
    dpni_get_rx_flow/set_rx_flow , tx_flow related, tx_conf related
    APIs

    Signed-off-by: Yogesh Gaur
    Signed-off-by: Priyanka Jain
    Reviewed-by: York Sun

    Yogesh Gaur
     
  • Unset USE_BOOTCOMMAND for all ls1088 defconfig files to fix
    redefinition error. USE_BOOTCOMMAND was introduced in commit
    b6251db8c3f ("Kconfig: Introduce USE_BOOTCOMMAND and migrate
    BOOTCOMMAND").

    Signed-off-by: Ashish Kumar
    Reviewed-by: York Sun

    Ashish Kumar
     

05 Dec, 2017

1 commit


04 Dec, 2017

27 commits


03 Dec, 2017

5 commits

  • The u-boot.sym file is scanned to find unit test suites for execution. At
    present it only finds those whose names start with 'dm' or 'env'. This
    code is buried in the bowels of the test code so when adding a new suite
    it is not easy to discover why it is ignored by the test framework.

    There seems to be no need to make this restriction. Drop it.

    Signed-off-by: Simon Glass
    Acked-by: Stephen Warren

    Simon Glass
     
  • At present the test setup is somewhat mixed with the test itself. But if
    the test setup fails (which it should not) then the test is actually
    invalid. Put all the test buffers and sizes in a struct and separate out
    the core code into a function.

    This will make it easier to move the code to use the unit test framework.

    Signed-off-by: Simon Glass

    Simon Glass
     
  • Adjust the code to use the common test-execution function.

    Signed-off-by: Simon Glass

    Simon Glass
     
  • The logic to either iterate through a list of tests or pick a named test
    is common to at lest two test suits. Move this logic into a new function
    and call it from the environment tests.

    Signed-off-by: Simon Glass

    Simon Glass
     
  • The kernel gets the ethernet MAC from the ethaddr variable, the omap boards for
    devices with USB based eth adapters just set the usbethaddr which doesn't appear
    to get passed to the kernel. The same Raspberry Pi code sets both ethaddr and
    usbethaddr so lets do that so linux (tested 4.13 and 4.14) get a static rather
    than a random MAC address, while not regressing users of usbethaddr.

    Signed-off-by: Peter Robinson

    Peter Robinson
     

02 Dec, 2017

3 commits


01 Dec, 2017

2 commits

  • On the RK3399-Q7, we want to trigger a full platform reset (so the
    various software stacks supported don't have to deal with the same
    complexities over and over again) in case that anything other than a
    power-on reset occurred.

    To do so, this defines the /config/sysreset-gpio property and has it
    point to a GPIO that will perform a power-on reset of the entire
    platform.

    Signed-off-by: Philipp Tomsich
    Tested-by: Klaus Goger

    Philipp Tomsich
     
  • The reset circuitry in the RK3399 only resets 'almost all logic' when
    a software reset is performed. To make our software maintenance
    easier in the future, we want to have the option (controlled by a DTS
    property) to force all reset causes other than a power-on reset to
    trigger a power-on reset via a GPIO trigger.

    This adds the necessary support to the rk3399-puma (i.e. RK3399-Q7)
    board-support and the documentation for the new property
    (sysreset-gpio) within the /config-node.

    Signed-off-by: Philipp Tomsich
    Tested-by: Klaus Goger
    Reviewed-by: Simon Glass

    Philipp Tomsich