bcm63xx/u-boot/arch/arm/include/asm/arch-omap4, branch master

i2c: omap24xx_i2c: Move away from SoC specific headers for reg offset

2018-12-10T05:09:34Z

Move away from SoC specific headers to handle different register layout. Instead use driver data to get appropriate register layouts like in the kernel. While at it, perform some mostly cosmetic alignment/cleanup in the functions being updated. Signed-off-by: Vignesh R Signed-off-by: Andreas Dannenberg Signed-off-by: Jean-Jacques Hiblot Reviewed-by: Tom Rini Reviewed-by: Heiko Schocher

SPDX: Convert all of our single license tags to Linux Kernel style

2018-05-07T13:34:12Z

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

Remove unnecessary instances of DECLARE_GLOBAL_DATA_PTR

2018-04-27T18:54:48Z

We have a large number of places where while we historically referenced gd in the code we no longer do, as well as cases where the code added that line "just in case" during development and never dropped it. Signed-off-by: Tom Rini

omap: Update the base address of the MMC controllers

2018-01-19T03:04:21Z

Align the base address defined in header files with the base address used in the DTS. This will facilitate the introduction of the DMA support. Of all HSMMC users, only omap3 doesn't have the 0x100 reserved region at the top. This region will be used to determine if the controller supports DMA transfers Signed-off-by: Jean-Jacques Hiblot Reviewed-by: Tom Rini

Convert CONFIG_SYS_I2C_BUS_MAX to Kconfig

2017-09-02T00:44:30Z

This converts the following to Kconfig: CONFIG_SYS_I2C_BUS_MAX Signed-off-by: Adam Ford Reviewed-by: Heiko Schocher [trini: Fix AM43XX drop AM44XX] Signed-off-by: Tom Rini

Configs: Migrate I2C_BUS_MAX to CONFIG_SYS_I2C_BUS_MAX

2017-09-01T21:56:20Z

For consistency with other platforms and in preparation of Kconfig migration, let's change Several TI platforms that use I2C_BUS_MAX to CONFIG_SYS_I2C_BUS_MAX Signed-off-by: Adam Ford

arm: omap: Unify get_device_type() function

2017-06-10T00:34:53Z

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 Reviewed-by: Lokesh Vutla [trini: Rework the guards as to not break TI81xx] Signed-off-by: Tom Rini

TI: Rework SRAM definitions and maximums

2016-09-06T17:41:42Z

On all TI platforms the ROM defines a "downloaded image" area at or near the start of SRAM which is followed by a reserved area. As it is at best bad form and at worst possibly harmful in corner cases to write in this reserved area, we stop doing that by adding in the define NON_SECURE_SRAM_IMG_END to say where the end of the downloaded image area is and make SRAM_SCRATCH_SPACE_ADDR be one kilobyte before this. At current we define the end of scratch space at 0x228 bytes past the start of scratch space this this gives us a lot of room to grow. As these scratch uses are non-optional today, all targets are modified to respect this boundary. Tested on OMAP4 Pandaboard, OMAP3 Beagle xM Cc: Albert Aribaud Cc: Nagendra T S Cc: Vaibhav Hiremath Cc: Lokesh Vutla Cc: Felipe Balbi Cc: Igor Grinberg Cc: Nikita Kiryanov Cc: Paul Kocialkowski Cc: Enric Balletbo i Serra Cc: Adam Ford Cc: Steve Sakoman Cc: Stefan Roese Cc: Thomas Weber Cc: Hannes Schmelzer Cc: Thomas Chou Cc: Masahiro Yamada Cc: Simon Glass Cc: Joe Hershberger Cc: Sam Protsenko Cc: Heiko Schocher Cc: Samuel Egli Cc: Michal Simek Cc: Wolfgang Denk Cc: Mateusz Kulikowski Cc: Ben Whitten Cc: Stefano Babic Cc: Bin Meng Cc: Sekhar Nori Cc: Mugunthan V N Cc: "B, Ravi" Cc: "Matwey V. Kornilov" Cc: Ladislav Michl Cc: Ash Charles Cc: "Kipisz, Steven" Cc: Daniel Allred Signed-off-by: Tom Rini Tested-by: Lokesh Vutla Acked-by: Lokesh Vutla Tested-by: Ladislav Michl

omap4: i2c: correct register offset for sync register

2016-07-26T06:39:10Z

The register offset of i2c_sysc offset is not correct as per omap4 TRM [1], correct the offsets as per the documentation. [1] - http://www.ti.com/lit/ug/swpu235ab/swpu235ab.pdf Signed-off-by: Mugunthan V N Reviewed-by: Tom Rini

omap4: Reboot mode support

2016-03-15T19:12:53Z

Reboot mode is written to SAR memory before reboot in the form of a string. This mechanism is supported on OMAP4 by various TI kernels. It is up to each board to make use of this mechanism or not. Signed-off-by: Paul Kocialkowski