30 Jul, 2019

6 commits


29 Jul, 2019

14 commits


28 Jul, 2019

7 commits

  • - Bring in the rest of the J271E platform
    - Various OMAP3/AM3517, DA850 fixes

    Tom Rini
     
  • ttyO2 console enables legacy CONFIG_SERIAL_OMAP driver in kernel.
    Nowadays it's preferred to use the generic CONFIG_SERIAL_8250_OMAP
    driver, which being enabled via ttyS2 console. Both drivers are enabled
    in multi_v7_defconfig and in omap2plus_defconfig, for compatibility
    reasons. Let's switch to ttyS2 console, to be sure that standard 8250
    serial driver is used.

    Similar behavior can be also achieved by enabling
    CONFIG_SERIAL_8250_OMAP_TTYO_FIXUP option in kernel, but it's better not
    to rely on that, as it can be disabled or removed after transitional
    period.

    Right now on DRA7/AM57x platforms the 8250-omap driver is being probed
    first, and omap-serial driver is only probed if the first one failed.
    It can be seen from uart3 definition in arch/arm/boot/dts/dra7-l4.dtsi:

    compatible = "ti,dra742-uart", "ti,omap4-uart";

    So the kernel already uses 8250 driver. This change basically allows
    kernel developers to throw away the omap-serial driver and associated
    compatibility options. Similar discussions [1,2] have started several
    years ago, so it should be safe to do that now.

    [1] https://patchwork.kernel.org/patch/6198471/
    [2] http://processors.wiki.ti.com/index.php/Sitara_Linux_UART_-_Switching_to_8250_Driver

    Signed-off-by: Sam Protsenko
    Reviewed-by: Andrew F. Davis
    [trini: Update omap5_uevm]
    Signed-off-by: Tom Rini

    Sam Protsenko
     
  • linux-mainline with multi_v7_defconfig + Android configs takes more
    space than regular TI Android kernel and bootm will fail to load it.
    Let's increase max kernel size up to 64 MiB to make it possible to run
    such kernel.

    Signed-off-by: Sam Protsenko
    Reviewed-by: Igor Opaniuk
    Reviewed-by: Lokesh Vutla

    Sam Protsenko
     
  • The DA8850-evm supports DM_I2C and boots with SPL_DM, so we can
    drop some of the code which disables DM_I2C in SPL. This
    patch removes some #undef's now rendered obsolete.

    Signed-off-by: Adam Ford

    Adam Ford
     
  • OHCI was added with DM_USB support, so there are a few unneeded
    items in the header file that can be removed. This also
    unifies da850evm with NOR and NAND booting options so all have
    OHCI support.

    Signed-off-by: Adam Ford
    [trini: Migrate da850_am18xxevm]
    Signed-off-by: Tom Rini

    Adam Ford
     
  • This patch enables the pinmuxing to support gpio_57 for phy reset
    and fixes the pinmuxing for the ECHI tranceiver. The clocks
    don't appear to by fully enabled yet, so OMAP-EHCI on am3517 is
    still not yet working, but we're one step closer.

    Signed-off-by: Adam Ford

    Adam Ford
     
  • The SOM-LV boards support the OMAP EHCI driver using port 2.
    With the driver updated to support device tree, this patch sets
    the corresponding pin muxing for the tranceiver as well as the
    reset pin.

    Signed-off-by: Adam Ford

    Adam Ford
     

27 Jul, 2019

8 commits

  • u-boot-imx-20190719

    - CCF for i.MX6
    - nandbcb command to write SPL into NAND
    - Switch to DM (i.MX28)
    - Boards: Toradex, engicam, DH
    - Fixes for i.MX8
    - Fixes for i.MX7ULP

    Travis: https://travis-ci.org/sbabic/u-boot-imx/builds/561147504

    Tom Rini
     
  • Add pinctrl macros for J721E SoC. These macro definitions are
    similar to that of AM6, but adding new definitions to avoid
    any naming confusions in the soc dts files.

    Signed-off-by: Lokesh Vutla
    Signed-off-by: Andreas Dannenberg

    Lokesh Vutla
     
  • Add board specific initialization for j721e evm

    Signed-off-by: Lokesh Vutla
    Signed-off-by: Jean-Jacques Hiblot
    Signed-off-by: Andreas Dannenberg

    Lokesh Vutla
     
  • TISCI protocol supports for enabling the device either with exclusive
    permissions for the requesting host or with sharing across the hosts.
    There are certain devices which are exclusive to Linux context and
    there are certain devices that are shared across different host contexts.
    So add support for getting this information from DT by increasing
    the power-domain cells to 2.

    Signed-off-by: Lokesh Vutla

    Lokesh Vutla
     
  • Certain drivers want to attach private data corresponding to each
    power domain. This data might be specific be to the drvier. So add
    a priv entry into the power_domain structure.

    Signed-off-by: Lokesh Vutla

    Lokesh Vutla
     
  • Any host while requesting for a device can request for its exclusive
    access. If an exclusive permission is obtained then it is the host's
    responsibility to release the device before the software entity on
    the host completes its execution. Else any other host's request for
    the device will be nacked. So add a command that releases all the
    exclusive devices that is acquired by the current host. This should
    be used with utmost care and can be called only at the end of the
    execution.

    Signed-off-by: Lokesh Vutla

    Lokesh Vutla
     
  • Add and expose a new processor shutdown API that wraps the two TISCI
    messages involved in initiating a core shutdown. The API will first
    queue a message to have the DMSC wait for a certain processor boot
    status to happen followed by a message to trigger the actual shutdown-
    with both messages being sent without waiting or requesting for a
    response. Note that the processor shutdown API call will need to be
    followed up by user software placing the respective core into either
    WFE or WFI mode.

    Signed-off-by: Andreas Dannenberg

    Andreas Dannenberg
     
  • Sysfw provides an option for requesting exclusive access for a
    device using the flags MSG_FLAG_DEVICE_EXCLUSIVE. If this flag is
    not used, the device is meant to be shared across hosts. Once a device
    is requested from a host with this flag set, any request to this
    device from a different host will be nacked by sysfw. Current tisci
    driver enables this flag for every device requests. But this may not
    be true for all the devices. So provide a separate commands in driver
    for exclusive and shared device requests.

    Signed-off-by: Lokesh Vutla

    Lokesh Vutla
     

26 Jul, 2019

5 commits