u-boot/arch/arm/mach-omap2/am33xx/Makefile

# SPDX-License-Identifier: GPL-2.0+
#
# Copyright (C) 2011, Texas Instruments, Incorporated - http://www.ti.com/

obj-$(CONFIG_AM33XX)	+= clock_am33xx.o
obj-$(CONFIG_TI814X)	+= clock_ti814x.o
obj-$(CONFIG_AM43XX)	+= clock_am43xx.o

ifneq ($(CONFIG_AM43XX)$(CONFIG_AM33XX),)
obj-y	+= clock.o
endif

obj-$(CONFIG_TI816X)	+= clock_ti816x.o
obj-y	+= sys_info.o
obj-y	+= ddr.o
ifeq ($(CONFIG_TI816X)$(CONFIG_SKIP_LOWLEVEL_INIT),)
obj-y	+= emif4.o
endif
obj-$(CONFIG_TI816X)	+= ti816x_emif4.o
obj-y	+= board.o
obj-y	+= mux.o
obj-y	+= prcm-regs.o
obj-y	+= hw_data.o
obj-y	+= fdt.o

obj-$(CONFIG_CLOCK_SYNTHESIZER)	+= clk_synthesizer.o

obj-$(CONFIG_AM33XX_CHILISOM) += chilisom.o
SPDX: Convert all of our single license tags to Linux Kernel style 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> 2018-05-06 21:58:06 +00:00			`# SPDX-License-Identifier: GPL-2.0+`
ARM:AM33XX: Added support for AM33xx This patch adds basic support for AM33xx which is based on ARMV7 Cortex A8 CPU. Signed-off-by: Chandan Nath <chandan.nath@ti.com> Signed-off-by: Sandeep Paulraj <s-paulraj@ti.com> 2011-10-14 02:58:22 +00:00			`#`
			`# Copyright (C) 2011, Texas Instruments, Incorporated - http://www.ti.com/`

armv7: convert makefiles to Kbuild style Signed-off-by: Masahiro Yamada <yamada.m@jp.panasonic.com> 2013-10-17 08:34:48 +00:00			`obj-$(CONFIG_AM33XX) += clock_am33xx.o`
			`obj-$(CONFIG_TI814X) += clock_ti814x.o`
			`obj-$(CONFIG_AM43XX) += clock_am43xx.o`
ARM: AM43xx: clocks: Add dpll and clock data Add dpll and clock data for AM43xx Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com> 2013-07-30 06:06:29 +00:00
			`ifneq ($(CONFIG_AM43XX)$(CONFIG_AM33XX),)`
armv7: convert makefiles to Kbuild style Signed-off-by: Masahiro Yamada <yamada.m@jp.panasonic.com> 2013-10-17 08:34:48 +00:00			`obj-y += clock.o`
ARM: AM43xx: clocks: Add dpll and clock data Add dpll and clock data for AM43xx Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com> 2013-07-30 06:06:29 +00:00			`endif`

armv7: convert makefiles to Kbuild style Signed-off-by: Masahiro Yamada <yamada.m@jp.panasonic.com> 2013-10-17 08:34:48 +00:00			`obj-$(CONFIG_TI816X) += clock_ti816x.o`
			`obj-y += sys_info.o`
			`obj-y += ddr.o`
ti816x: Rework DDR initialization sequence The ti816x/am389x SoC is the first generation in what U-Boot calls the "am33xx" family. In the first generation of this family the DDR initialization sequence is quite different from all of the subsequent generations. Whereas with ti814x (second generation) we can easily work the minor differenced between that and am33xx (third generation), our attempts to do this for ti816x weren't sufficient. Rather than add a large amount of #ifdef logic to make this different sequence work we add a new file, ti816x_emif4.c to handle the various required undocumented register writes and sequence and leverage what we can from arch/arm/mach-omap2/am33xx/ddr.c still. As DDR2 has similar problems today but I am unable to test it, we drop the DDR2 defines from the code rather than imply that it works by leaving it. We also remove a bunch of other untested code about changing the speed the DDR runs at. Signed-off-by: Tom Rini <trini@konsulko.com> 2017-05-16 18:46:35 +00:00			`ifeq ($(CONFIG_TI816X)$(CONFIG_SKIP_LOWLEVEL_INIT),)`
armv7: convert makefiles to Kbuild style Signed-off-by: Masahiro Yamada <yamada.m@jp.panasonic.com> 2013-10-17 08:34:48 +00:00			`obj-y += emif4.o`
ti816x: Rework DDR initialization sequence The ti816x/am389x SoC is the first generation in what U-Boot calls the "am33xx" family. In the first generation of this family the DDR initialization sequence is quite different from all of the subsequent generations. Whereas with ti814x (second generation) we can easily work the minor differenced between that and am33xx (third generation), our attempts to do this for ti816x weren't sufficient. Rather than add a large amount of #ifdef logic to make this different sequence work we add a new file, ti816x_emif4.c to handle the various required undocumented register writes and sequence and leverage what we can from arch/arm/mach-omap2/am33xx/ddr.c still. As DDR2 has similar problems today but I am unable to test it, we drop the DDR2 defines from the code rather than imply that it works by leaving it. We also remove a bunch of other untested code about changing the speed the DDR runs at. Signed-off-by: Tom Rini <trini@konsulko.com> 2017-05-16 18:46:35 +00:00			`endif`
			`obj-$(CONFIG_TI816X) += ti816x_emif4.o`
armv7: convert makefiles to Kbuild style Signed-off-by: Masahiro Yamada <yamada.m@jp.panasonic.com> 2013-10-17 08:34:48 +00:00			`obj-y += board.o`
			`obj-y += mux.o`
arm: omap: Unify get_device_type() function Refactor OMAP3/4/5 code so that we have only one get_device_type() function for all platforms. Details: - Add ctrl variable for AM33xx and OMAP3 platforms (like it's done for OMAP4/5), so we can obtain status register in common way - For now ctrl structure for AM33xx/OMAP3 contains only status register address - Run hw_data_init() in order to assign ctrl to proper structure - Remove DEVICE_MASK and DEVICE_GP definitions as they are not used (DEVICE_TYPE_MASK and GP_DEVICE are used instead) - Guard structs in omap_common.h with #ifdefs, because otherwise including omap_common.h on non-omap4/5 board files breaks compilation Buildman script was run for all OMAP boards. Result output: arm: (for 38/616 boards) all +352.5 bss -1.4 data +3.5 rodata +300.0 spl/u-boot-spl:all +284.7 spl/u-boot-spl:data +2.2 spl/u-boot-spl:rodata +252.0 spl/u-boot-spl:text +30.5 text +50.4 (no errors to report) Tested on AM57x EVM and BeagleBoard xM. Signed-off-by: Sam Protsenko <semen.protsenko@linaro.org> Reviewed-by: Lokesh Vutla <lokeshvutla@ti.com> [trini: Rework the guards as to not break TI81xx] Signed-off-by: Tom Rini <trini@konsulko.com> 2017-06-02 15:00:00 +00:00			`obj-y += prcm-regs.o`
			`obj-y += hw_data.o`
arm: mach-omap2: am33xx: Add FDT fixup suport for AM33xx/AM43xx boards Similar to what is done with OMAP5 class boards we need to perform fixups common to this SoC class, add support for this here and add HS fixups. Signed-off-by: Andrew F. Davis <afd@ti.com> 2017-07-10 19:45:52 +00:00			`obj-y += fdt.o`
ARM: AM33xx: Add support for Clock Synthesizer The CDCE913 and CDCEL913 devices are modular PLL-based, low cost, high performance , programmable clock synthesizers. They generate upto 3 output clocks from a single input frequency. Each output can be programmed for any clock-frequency. Adding support for the same. Reviewed-by: Tom Rini <trini@konsulko.com> Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com> 2016-05-16 06:17:25 +00:00
			`obj-$(CONFIG_CLOCK_SYNTHESIZER) += clk_synthesizer.o`
ARM: am335x: Add support for chiliSOM chiliSOM is a System On Module (http://http://grinn-global.com/chilisom/). It can't exists on its own, but will be used as part of other boards. Hardware specification: * TI AM335x processor * 128M, 256M or 512M DDR3 memory * up to 256M NAND We place source inside arch/arm/mach-omap2/ directory and make it possible to reuse initialization code (i.e. DDR, NAND init) for all boards that use it. Signed-off-by: Marcin Niestroj <m.niestroj@grinn-global.com> Reviewed-by: Tom Rini <trini@konsulko.com> 2017-01-25 08:53:07 +00:00
			`obj-$(CONFIG_AM33XX_CHILISOM) += chilisom.o`