- 10 Dec, 2020 1 commit
-
-
Meenakshi Aggarwal authored
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@nxp.com> [Fixed whitespace errors] Signed-off-by:
Priyanka Jain <priyanka.jain@nxp.com>
-
- 24 Jan, 2020 1 commit
-
-
Simon Glass authored
These three clock functions don't use driver model and should be migrated. In the meantime, create a new file to hold them. Signed-off-by:Simon Glass <sjg@chromium.org>
-
- 17 Jan, 2020 1 commit
-
-
Simon Glass authored
These three clock functions don't use driver model and should be migrated. In the meantime, create a new file to hold them. Signed-off-by:Simon Glass <sjg@chromium.org>
-
- 16 Jan, 2020 1 commit
-
-
Yangbo Lu authored
The eSDHC reference clocks should be provided by speed.c in arch/. And we do not need CONFIG_FSL_ESDHC_USE_PERIPHERAL_CLK option to select which clock to use. Because we can make the driver to select the periperhal clock which is better (provides higher frequency) automatically if its value is provided by speed.c. This patch is to drop this option and make driver to select clock automatically. Also fix peripheral clock calculation issue in fsl_lsch2_speed.c/fsl_lsch3_speed.c. Signed-off-by:Yangbo Lu <yangbo.lu@nxp.com>
-
- 02 Dec, 2019 1 commit
-
-
Simon Glass authored
These functions belong in cpu_func.h since they do not use driver model. Move them over. Don't bother adding comments since these functions should be deleted. Signed-off-by:
Simon Glass <sjg@chromium.org> Reviewed-by:
Tom Rini <trini@konsulko.com>
-
- 27 Nov, 2019 1 commit
-
-
Yangbo Lu authored
Although layerscape platforms reuse mxc_get_clock() of i.MX platforms, eSDHC clock getting do not have to use it. It uses global data gd->arch.sdhc_clk directly in fsl_esdhc driver. Even there are more than one eSDHC controllers on SoC, they use same reference clock. Signed-off-by:
Yangbo Lu <yangbo.lu@nxp.com> Reviewed-by:
Priyanka Jain <priyanka.jain@nxp.com>
-
- 08 Nov, 2019 1 commit
-
-
Michael Walle authored
The clocks are not dependent on the target but only on the SoC. Therefore, convert the CONFIG_TARGET_x macros to the corresponding CONFIG_ARCH_x. This will allow other targets to automatically use the common code. Otherwise every new target would have to add itself to the "#if defined(CONFIG_TARGET_x) || .." macros. Signed-off-by:
Michael Walle <michael@walle.cc> Reviewed-by:
Priyanka Jain <priyanka.jain@nxp.com>
-
- 12 Sep, 2019 1 commit
-
-
Yinbo Zhu authored
Add esdhc peripheral clock support for NXP layerscape platforms: LS1046ARDB, LS1043ARDB, LS1012ARDB, LS1028ARDB, LS1088ARDB, LX2160ARDB Signed-off-by:
Yinbo Zhu <yinbo.zhu@nxp.com> Signed-off-by:
Priyanka Jain <priyanka.jain@nxp.com>
-
- 19 Jun, 2019 1 commit
-
-
Yangbo Lu authored
Layerscape began to use two eSDHC controllers, for example, LS1028A. They are same IP block with same reference clock. This patch is to add clock support for the second eSDHC. Signed-off-by:
Yangbo Lu <yangbo.lu@nxp.com> Signed-off-by:
Yinbo Zhu <yinbo.zhu@nxp.com> Reviewed-by:
Prabhakar Kushwaha <prabhakar.kushwaha@nxp.com>
-
- 27 Sep, 2018 1 commit
-
-
Yinbo Zhu authored
This patch adds esdhc clock support for ls1088a and ls2088a. Signed-off-by:
Yinbo Zhu <yinbo.zhu@nxp.com> Reviewed-by:
York Sun <york.sun@nxp.com>
-
- 07 May, 2018 1 commit
-
-
Tom Rini authored
When U-Boot started using SPDX tags we were among the early adopters and there weren't a lot of other examples to borrow from. So we picked the area of the file that usually had a full license text and replaced it with an appropriate SPDX-License-Identifier: entry. Since then, the Linux Kernel has adopted SPDX tags and they place it as the very first line in a file (except where shebangs are used, then it's second line) and with slightly different comment styles than us. In part due to community overlap, in part due to better tag visibility and in part for other minor reasons, switch over to that style. This commit changes all instances where we have a single declared license in the tag as both the before and after are identical in tag contents. There's also a few places where I found we did not have a tag and have introduced one. Signed-off-by:Tom Rini <trini@konsulko.com>
-
- 03 Feb, 2017 1 commit
-
-
Prabhakar Kushwaha authored
IFC IP clock is always a constant divisor of platform clock pre-defined per SoC. Clock control register (CCR) used in current implementation governs IFC IP output clock. Update sys_info->freq_localbus to represent IFC input clock with value constant divisor of platform clock. Signed-off-by:
Prabhakar Kushwaha <prabhakar.kushwaha@nxp.com> Reviewed-by:
York Sun <york.sun@nxp.com>
-
- 18 Jan, 2017 1 commit
-
-
Hou Zhiqiang authored
This patch binds the sys_info->freq_systembus to Platform PLL, and implements the IPs' clock function individually. Signed-off-by:
Hou Zhiqiang <Zhiqiang.Hou@nxp.com> Reviewed-by:
York Sun <york.sun@nxp.com>
-
- 06 May, 2016 1 commit
-
-
Robert P. J. Day authored
Spelling corrections for (among other things): * environment * override * variable * ftd (should be "fdt", for flattened device tree) * embedded * FTDI * emulation * controller
-
- 06 Apr, 2016 1 commit
-
-
York Sun authored
LS2080A is the primary SoC, and LS2085A is a personality with AIOP and DPAA DDR. The RDB and QDS boards support both personality. By detecting the SVR at runtime, a single image per board can support both SoCs. It gives users flexibility to swtich SoC without the need to reprogram the board. Signed-off-by:
York Sun <york.sun@nxp.com> CC: Prabhakar Kushwaha <prabhakar.kushwaha@nxp.com> Reviewed-by:
Prabhakar Kushwaha <prabhakar.kushwaha@nxp.com>
-
- 30 Nov, 2015 1 commit
-
-
Prabhakar Kushwaha authored
LS2080A is a prime personality of Freescale’s LS2085A. It is a non-AIOP personality without support of DP-DDR, L2 switch, 1588, PCIe endpoint etc. So renaming existing LS2085A code base to reflect LS2080A (Prime personality) Signed-off-by:
Pratiyush Mohan Srivastava <pratiyush.srivastava@freescale.com> Signed-off-by:
Prabhakar Kushwaha <prabhakar@freescale.com> [York Sun: Dropped #ifdef in cpu.c for cpu_type_list] Reviewed-by:
York Sun <yorksun@freescale.com>
-
- 29 Oct, 2015 1 commit
-
-
Mingkai Hu authored
There are two LS series processors are built on ARMv8 Layersacpe architecture currently, LS2085A and LS1043A. They are based on ARMv8 core although use different chassis, so create fsl-layerscape to refactor the common code for the LS series processors which also paves the way for adding LS1043A platform. Signed-off-by:
Mingkai Hu <Mingkai.Hu@freescale.com> Signed-off-by:
Hou Zhiqiang <B48286@freescale.com> Signed-off-by:
Gong Qianyu <Qianyu.Gong@freescale.com> Reviewed-by:
York Sun <yorksun@freescale.com>
-
- 20 Jul, 2015 1 commit
-
-
Haikun Wang authored
Signed-off-by:
Haikun Wang <haikun.wang@freescale.com> Reviewed-by:
York Sun <yorksun@freescale.com>
-
- 23 Apr, 2015 2 commits
-
-
Jaiprakash Singh authored
IFC has two register pages.Till IFC version 1.4 each register page is 4KB each.But IFC ver 2.0 register page size is 64KB each.IFC regiters structure is break into two viz FCM and RUNTIME.FCM(Flash control machine) registers are defined in PAGE0 and controls IFC generic functionality. RUNTIME registers are defined in PAGE1 and controls NAND and GPCM funcinality. FCM and RUNTIME structures defination is common for IFC version 1.4 and 2.0. Signed-off-by:
Jaiprakash Singh <b44839@freescale.com> Signed-off-by:
York Sun <yorksun@freescale.com>
-
York Sun authored
Platform clock is half of platform PLL. There is an additional divisor in place. Clean up code copied from powerpc. Signed-off-by:York Sun <yorksun@freescale.com>
-
- 24 Feb, 2015 1 commit
-
-
York Sun authored
FSL-LSCH3 platforms can have multiple DDR clocks. LS2085A has one clock for general DDR controlers, and another clock for DP-DDR. DDR driver needs to change to support multiple clocks. Signed-off-by:York Sun <yorksun@freescale.com>
-
- 03 Jul, 2014 1 commit
-
-
York Sun authored
Freescale LayerScape with Chassis Generation 3 is a set of SoCs with ARMv8 cores and 3rd generation of Chassis. We use different MMU setup to support memory map and cache attribute for these SoCs. MMU and cache are enabled very early to bootst performance, especially for early development on emulators. After u-boot relocates to DDR, a new MMU table with QBMan cache access is created in DDR. SMMU pagesize is set in SMMU_sACR register. Both DDR3 and DDR4 are supported. Signed-off-by:
York Sun <yorksun@freescale.com> Signed-off-by:
Varun Sethi <Varun.Sethi@freescale.com> Signed-off-by:
Arnab Basu <arnab.basu@freescale.com>
-