ARM: DRA7xx: Add CPSW and MDIO pinmux support Adding CPSW Slave 0 and MDIO pinmux support for DRA7xx EVM Change-Id: I562fecee5194f9498d1e8387e1e3888e3ebb3fbd Signed-off-by: Mugunthan V N <mugunthanvnm@ti.com> [Resolved merge conflict and added change id for gerrit] Signed-off-by: Praveen Rao <prao@ti.com>
ARM: DRA7xx: Add CPSW support to DRA7xx EVM Adding support for CPSW Ethernet support found in DRA7xx EVM Change-Id: Id68e606967aeeecaaf991eb26ef94d2119dc7a83 Signed-off-by: Mugunthan V N <mugunthanvnm@ti.com> [Resolved merge conflicts and added change id for gerrit] Signed-off-by: Praveen Rao <prao@ti.com>
drivers: net: cpsw: remove hard coding bd ram for cpsw BD ram address may vary in various SOC, so removing the hardcoding and passing the same information through platform data Change-Id: Ib36d34f66f741321abdf06575010c87c99d49085 Signed-off-by: Mugunthan V N <mugunthanvnm@ti.com> [Added change-id for gerrit] Signed-off-by: Praveen Rao <prao@ti.com>
HACK: ARM: DRA7xx: crossbar: Add support for crossbar DRA7xx has a large number of interrupts/dma requests to service the needs of its many peripherals and subsystems. All of the requests lines from the subsystems are not needed at the same time, so they have to be muxed to the controllers appropriately. In such places a interrupt/dma controllers are preceded by an IRQ/DMA CROSSBAR that provides flexibility in muxing the device requests to the controller inputs. This configures some of the MPU IRQs and SDMA DREQ at the u-boot until this functionality is available at the kernel. Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com> Signed-off-by: Suman Anna <s-anna@ti.com> Signed-off-by: Misael Lopez Cruz <misael.lopez@ti.com> Signed-off-by: Nikhil Devshatwar <nikhil.nd@ti.com> Signed-off-by: Amarinder Bindra <a-bindra@ti.com>
dra7xx_evm: add SPL API, QSPI, and serial flash support Enables support for SPI SPL, QSPI and Spansion serial flash device on the EVM. Configures pin muxes for QSPI mode. Signed-off-by: Matt Porter <matt.porter@linaro.org> Signed-off-by: Sourav Poddar <sourav.poddar@ti.com>
DRA7: Revert QSPI v1 patchset to apply v2 with code clean up This patch is a squash of 8 reverted patches as mentioned below. This was required inorder to apply a later version of the same patchset with code clean up and fixes. Revert "arm: omap5: hw_data: Enable clock selectively." Revert "board: dra7xxx: modfiy mux data." Revert "Fix offset detail and add sysboot settings" Revert "README: qspi usecase and testing documentation." Revert "drivers: mtd: spi: Modify read/write command for sfl256s flash." Revert "dra7xx_evm: add SPL API, QSPI, and serial flash support" Revert "spi: add TI QSPI driver" Revert "omap5: add qspi support"
ARM: OMAP4+: Cleanup header files After having the u-boot clean up series, there are many definitions that are unused in header files. Removing all those unused ones. Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
ARM:Panda:Fix device tree loading for the panda-es Fix the device tree loading for panda(4430) and panda-es(4460) Modify the board name if a 4460 panda or panda-es is detected at run time. In the findfdt add a check for the panda-es board name and load the panda-es device tree blob. Signed-off-by: Dan Murphy <dmurphy@ti.com>
twl6035: rename to palmas TPS659038/TWL6035/TWL6037 all belong to palmas family of TI PMICs Rename twl6035 to palmas to allow reuse across multiple current and future platforms As part of this change, change the CONFIG_TWL6035_POWER to CONFIG_PALMAS_POWER and update usage of header file accordingly. Signed-off-by: Nishanth Menon <nm@ti.com>
omap5912-osk: Fix device initialisation In the current u-boot, the device pin multiplexing and clock initialisation needs to be early during the boot process and before board_init() is called. U-boot is currently crashing on this board because this is not being done early enough. Therefore, add a s_init() function for the omap5912-osk board to do this. Also fix the stack pointer so that it is pointing to the end of the internal RAM and not the beginning as this was also causing the device to crash. Signed-off-by: Jon Hunter <jon-hunter@ti.com>
omap5912-osk: Fix booting from NOR flash The omap5912-osk board is using a RAM based address as the linker location for code. This is causing several problems when attempting to run the latest u-boot code base on this board from flash. Update the default linker location for code to be in NOR flash at address 0x00000000. The omap5912-osk board only has 32MB of RAM and so fix the comment in the omap5912-osk config.mk file as well. Signed-off-by: Jon Hunter <jon-hunter@ti.com>