f01b9b73f5
Pull support for three new arm SoC types from Arnd Bergmann: - The mvebu platform includes Marvell's Armada XP and Armada 370 chips, made by the mvebu business unit inside of Marvell. Since the same group also made the older but similar platforms we call "orion5x", "kirkwood", "mv78xx0" and "dove", we plan to move all of them into the mach-mvebu directory in the future. - socfpga is Altera's platform based on Cortex-A9 cores and a lot of FPGA space. This is similar to the Xilinx zynq platform we already support. The code is particularly clean, which is helped by the fact that the hardware doesn't do much besides the parts that are expected to get added in the FPGA. - The OMAP subarchitecture gains support for the latest generation, the OMAP5 based on the new Cortex-A15 core. Support is rather rudimentary for now, but will be extended in the future. * tag 'newsoc' of git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc: (25 commits) ARM: socfpga: initial support for Altera's SOCFPGA platform arm: mvebu: generate DTBs for supported SoCs ARM: mvebu: MPIC: read number of interrupts from control register arm: mach-mvebu: add entry to MAINTAINERS arm: mach-mvebu: add compilation/configuration change arm: mach-mvebu: add defconfig arm: mach-mvebu: add documentation for new device tree bindings arm: mach-mvebu: add support for Armada 370 and Armada XP with DT arm: mach-mvebu: add source files arm: mach-mvebu: add header clocksource: time-armada-370-xp: Marvell Armada 370/XP SoC timer driver ARM: Kconfig update to support additional GPIOs in OMAP5 ARM: OMAP5: Add the build support arm/dts: OMAP5: Add omap5 dts files ARM: OMAP5: board-generic: Add device tree support ARM: omap2+: board-generic: clean up the irq data from board file ARM: OMAP5: Add SMP support ARM: OMAP5: Add the WakeupGen IP updates ARM: OMAP5: l3: Add l3 error handler support for omap5 ARM: OMAP5: gpmc: Update gpmc_init() ... Conflicts: Documentation/devicetree/bindings/arm/omap/omap.txt arch/arm/mach-omap2/Makefile drivers/clocksource/Kconfig drivers/clocksource/Makefile
56 lines
1.6 KiB
Plaintext
56 lines
1.6 KiB
Plaintext
* Texas Instruments OMAP
|
|
|
|
OMAP is currently using a static file per SoC family to describe the
|
|
IPs present in the SoC.
|
|
On top of that an omap_device is created to extend the platform_device
|
|
capabilities and to allow binding with one or several hwmods.
|
|
The hwmods will contain all the information to build the device:
|
|
address range, irq lines, dma lines, interconnect, PRCM register,
|
|
clock domain, input clocks.
|
|
For the moment just point to the existing hwmod, the next step will be
|
|
to move data from hwmod to device-tree representation.
|
|
|
|
|
|
Required properties:
|
|
- compatible: Every devices present in OMAP SoC should be in the
|
|
form: "ti,XXX"
|
|
- ti,hwmods: list of hwmod names (ascii strings), that comes from the OMAP
|
|
HW documentation, attached to a device. Must contain at least
|
|
one hwmod.
|
|
|
|
Optional properties:
|
|
- ti,no_idle_on_suspend: When present, it prevents the PM to idle the module
|
|
during suspend.
|
|
|
|
|
|
Example:
|
|
|
|
spinlock@1 {
|
|
compatible = "ti,omap4-spinlock";
|
|
ti,hwmods = "spinlock";
|
|
};
|
|
|
|
|
|
Boards:
|
|
|
|
- OMAP3 BeagleBoard : Low cost community board
|
|
compatible = "ti,omap3-beagle", "ti,omap3"
|
|
|
|
- OMAP4 SDP : Software Developement Board
|
|
compatible = "ti,omap4-sdp", "ti,omap4430"
|
|
|
|
- OMAP4 PandaBoard : Low cost community board
|
|
compatible = "ti,omap4-panda", "ti,omap4430"
|
|
|
|
- OMAP3 EVM : Software Developement Board for OMAP35x, AM/DM37x
|
|
compatible = "ti,omap3-evm", "ti,omap3"
|
|
|
|
- AM335X EVM : Software Developement Board for AM335x
|
|
compatible = "ti,am335x-evm", "ti,am33xx", "ti,omap3"
|
|
|
|
- AM335X Bone : Low cost community board
|
|
compatible = "ti,am335x-bone", "ti,am33xx", "ti,omap3"
|
|
|
|
- OMAP5 EVM : Evaluation Module
|
|
compatible = "ti,omap5-evm", "ti,omap5"
|