u-boot.git/arch/arm/include/asm/ti-common, branch v2017.09

ARM: omap2+: rename config to ARCH_OMAP2PLUS and consolidate Kconfig

2017-04-27T20:49:08Z

In Linux, CONFIG_ARCH_OMAP2PLUS is used for OMAP2 or later SoCs. Rename CONFIG_ARCH_OMAP2 to CONFIG_ARCH_OMAP2PLUS to follow this naming. Move the OMAP2+ board/SoC choice down to mach-omap2/Kconfig to slim down the arch/arm/Kconfig level. Signed-off-by: Masahiro Yamada Reviewed-by: Tom Rini

ti: wdt: common: Make the wdt IP defines common for the TI platform

2017-04-09T01:32:48Z

Signed-off-by: Lukasz Majewski Reviewed-by: Tom Rini

TI: Remove CONFIG_OMAP_COMMON in favor of CONFIG_ARCH_OMAP2

2016-11-21T19:07:29Z

With the move to arch/arm/mach-omap2 there are now very few uses of CONFIG_OMAP_COMMON and further they can all be replaced with CONFIG_ARCH_OMAP2, so do so. Signed-off-by: Tom Rini

ARM: keystone: rename clk_get_rate() to ks_clk_get_rate()

2016-10-08T13:33:13Z

The KeyStone platform has its own clk_get_rate() but its prototype is different from that of the common-clk (clk-uclass) framework. Prefix the KeyStone specific implementation with ks_ in order to avoid name-space conflict. Signed-off-by: Masahiro Yamada Reviewed-by: Simon Glass Acked-by: Lokesh Vutla Reviewed-by: Tom Rini

Fix to davinci_nand.h to place CEnCFG registers at correct

2016-06-06T17:39:12Z

Signed-off-by: Peter Howard

driver: net: keystone_net: add support for rgmii phy

2015-10-22T18:22:23Z

In K2G, Ethernet doesn't support SGMII instead it support RGMII, adding support to the driver to connect to RGMII phy. Signed-off-by: Vitaly Andrianov Signed-off-by: Mugunthan V N Signed-off-by: Lokesh Vutla

driver: net: keystone_net: fix phy mode configuration

2015-10-22T18:22:22Z

Phy mode is a board property and it can be different between multiple board and ports, so it should not be hardcoded in driver to one specific mode. So adding a field in eth_priv_t structure to pass phy mode to driver. Signed-off-by: Mugunthan V N Signed-off-by: Lokesh Vutla

ARM: k2g: Add clock information

2015-10-22T18:22:16Z

Add clock information for Galileo Signed-off-by: Vitaly Andrianov Signed-off-by: Lokesh Vutla Signed-off-by: Mugunthan V N

dma: ti-edma3: Add helper function to support edma3 transfer

2015-08-17T17:59:15Z

Signed-off-by: Vignesh R Reviewed-by: Jagan Teki

omap-common: Common boot code OMAP3 support and cleanup

2015-07-27T19:02:03Z

This introduces OMAP3 support for the common omap boot code, as well as a major cleanup of the common omap boot code. First, the omap_boot_parameters structure becomes platform-specific, since its definition differs a bit across omap platforms. The offsets are removed as well since it is U-Boot's coding style to use structures for mapping such kind of data (in the sense that it is similar to registers). It is correct to assume that romcode structure encoding is the same as U-Boot, given the description of these structures in the TRMs. The original address provided by the bootrom is passed to the U-Boot binary instead of a duplicate of the structure stored in global data. This allows to have only the relevant (boot device and mode) information stored in global data. It is also expected that the address where the bootrom stores that information is not overridden by the U-Boot SPL or U-Boot. The save_omap_boot_params is expected to handle all special cases where the data provided by the bootrom cannot be used as-is, so that spl_boot_device and spl_boot_mode only return the data from global data. All of this is only relevant when the U-Boot SPL is used. In cases it is not, save_boot_params should fallback to its weak (or board-specific) definition. save_omap_boot_params should not be called in that context either. Signed-off-by: Paul Kocialkowski