13 Jan, 2021

1 commit


03 Nov, 2020

2 commits


29 Oct, 2020

8 commits


19 Oct, 2020

2 commits


09 Oct, 2020

2 commits


29 Sep, 2020

9 commits


28 Sep, 2020

1 commit


18 Sep, 2020

4 commits


10 Sep, 2020

1 commit


08 Sep, 2020

2 commits

  • This patch add base support for LX2162AQDS board.
    LX2162AQDS board supports LX2162A family SoCs.
    This patch add basic support of platform.

    Signed-off-by: Ioana Ciornei
    Signed-off-by: Zhao Qiang
    Signed-off-by: hui.song
    Signed-off-by: Manish Tomar
    Signed-off-by: Vikas Singh
    Signed-off-by: Meenakshi Aggarwal
    Signed-off-by: Priyanka Jain

    Meenakshi Aggarwal
     
  • LX2162 is LX2160 based SoC, it has same die as of LX2160
    with different packaging.

    LX2162A support 64-bit 2.9GT/s DDR4 memory, i2c, micro-click module,
    microSD card, eMMC support, serial console, qspi nor flash, qsgmii,
    sgmii, 25g, 40g, 50g network interface, one usb 3.0 and serdes
    interface to support three PCIe gen3 interface.

    Signed-off-by: Meenakshi Aggarwal

    Meenakshi Aggarwal
     

07 Sep, 2020

1 commit


02 Sep, 2020

1 commit

  • Configure DWC3's cache type to 'cacheable' for better
    performance. Actually related register definition and values are SoC
    specific, which means this setting is only applicable to Layerscape SoC,
    not generic for all platforms which have integrated DWC3 IP.

    Signed-off-by: Ran Wang

    Ran Wang
     

27 Aug, 2020

4 commits

  • The sdhc_adapter of global data has not been used, and we
    do not have to use it as global data even we may need it
    in the future.

    Signed-off-by: Yangbo Lu
    Reviewed-by: Peng Fan
    Reviewed-by: Priyanka Jain

    Yangbo Lu
     
  • This patch is to define esdhc_status_fixup function for ls1028a to disable
    SDHC1/SDHC2 status in device tree node if not selected.

    Signed-off-by: Yinbo Zhu
    Signed-off-by: Xiaowei Bao
    Signed-off-by: Yangbo Lu
    Reviewed-by: Priyanka Jain

    Yinbo Zhu
     
  • In the current implementation, u-boot creates iommu mappings only
    for PCI devices enumarated at boot time thus does not take into
    account more dynamic scenarios such as SR-IOV or PCI hot-plug.
    Add an u-boot env var and a device tree property (to be used for
    example in more static scenarios such as hardwired PCI endpoints
    that get initialized later in the system setup) that would allow
    two things:
    - for a SRIOV capable PCI EP identified by its B.D.F specify
    the maximum number of VFs that will ever be created for it
    - for hot-plug case, specify the B.D.F with which the device
    will show up on the PCI bus
    More details can be found in the included documentation:
    arch/arm/cpu/armv8/fsl-layerscape/doc/README.pci_iommu_extra

    Signed-off-by: Laurentiu Tudor

    Laurentiu Tudor
     
  • Add flash node under dspi into fsl-lx2160a-qds.dtsi

    Signed-off-by: Zhao Qiang

    Zhao Qiang
     

04 Aug, 2020

2 commits