forked from Minki/linux
f8974cb713
This branch contains a minor documentation addition, a utility function for parsing string properties needed by some of the new ARM platforms, disables dynamic DT code that isn't used anywhere but on a few PPC machines, and exports DT node compatible data to userspace via UEVENT properties. Nothing earth shattering here. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAABAgAGBQJPZ2KDAAoJEEFnBt12D9kBBSgP/1i4AcqErPl1Syuviai+ro0h gbQaV1qvCAHQz8YkzzGmEKUPiXGC5Qtqf/rbwIJMa+UwVgGMZaIn3HVS8lO+z5N/ SExkBAdMJPvUZQui5ZaCEtBCUSxF8cTFxXxBLQdaDGVNtli17fmhK+XeBbLAaY3H sZo0/GKzKIo7MdFnuRSRkHPP5SpX9QQEoXc//mWJAPIytX8oqGLwW0cT+8g6g11A 17IHM59Lr6hh6g9BMh3BCsulISPKqKDeHgVWgWu9Eq97EEvh9fSnTGQQMmhcCpwY diELtnbXVtM3h2ZCQSdXgiJ3BwiQn76mXqGwrNzXyPh1Tznq7l/GUZIC2bh6tpjG UJ3PyfDKcl2d6lVkPm5d2FdepW0CYeS4sNZCglbItjFHTpxwMftGqwl5H7L/7kYh MyKEYRlCyZbIqIm+OjgdMK/lN7yVJJdHgsjddZV940Stk4emjtBYC7YzBm2r/sk9 7I2RQ9TEyicnGAJ0QBd/DaZSMbsjSCHxiryX8JQd0BOGdFWn/kKO0Wfm0Xc0yCs1 /Y1ODio1r/frs30gazyTBWjrTErnOanD9ijvEzW/gJpaJZi1WNfFFhTwYQcgQ16A B5R088ry5tx0BDxsBN8/cL5EHmisNqFvYbDUMdC5IVmcVfc8OxijQkjpe1zNhpaS mCHQjbNfKfRSIq3XmpFV =kK/B -----END PGP SIGNATURE----- Merge tag 'dt-for-linus' of git://git.secretlab.ca/git/linux-2.6 Pull core device tree changes for Linux v3.4 from Grant Likely: "This branch contains a minor documentation addition, a utility function for parsing string properties needed by some of the new ARM platforms, disables dynamic DT code that isn't used anywhere but on a few PPC machines, and exports DT node compatible data to userspace via UEVENT properties. Nothing earth shattering here." * tag 'dt-for-linus' of git://git.secretlab.ca/git/linux-2.6: of: Only compile OF_DYNAMIC on PowerPC pseries and iseries arm/dts: OMAP3: Add omap3evm and am335xevm support drivercore: Output common devicetree information in uevent of: Add of_property_match_string() to find index into a string list
50 lines
1.5 KiB
Plaintext
50 lines
1.5 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"
|