1* Texas Instruments OMAP
2
3OMAP is currently using a static file per SoC family to describe the
4IPs present in the SoC.
5On top of that an omap_device is created to extend the platform_device
6capabilities and to allow binding with one or several hwmods.
7The hwmods will contain all the information to build the device:
8address range, irq lines, dma lines, interconnect, PRCM register,
9clock domain, input clocks.
10For the moment just point to the existing hwmod, the next step will be
11to move data from hwmod to device-tree representation.
12
13
14Required properties:
15- compatible: Every devices present in OMAP SoC should be in the
16  form: "ti,XXX"
17- ti,hwmods: list of hwmod names (ascii strings), that comes from the OMAP
18  HW documentation, attached to a device. Must contain at least
19  one hwmod.
20
21Optional properties:
22- ti,no_idle_on_suspend: When present, it prevents the PM to idle the module
23  during suspend.
24
25
26Example:
27
28spinlock@1 {
29    compatible = "ti,omap4-spinlock";
30    ti,hwmods = "spinlock";
31};
32
33
34Boards:
35
36- OMAP3 BeagleBoard : Low cost community board
37  compatible = "ti,omap3-beagle", "ti,omap3"
38
39- OMAP3 Tobi with Overo : Commercial expansion board with daughter board
40  compatible = "ti,omap3-tobi", "ti,omap3-overo", "ti,omap3"
41
42- OMAP4 SDP : Software Developement Board
43  compatible = "ti,omap4-sdp", "ti,omap4430"
44
45- OMAP4 PandaBoard : Low cost community board
46  compatible = "ti,omap4-panda", "ti,omap4430"
47
48- OMAP3 EVM : Software Developement Board for OMAP35x, AM/DM37x
49  compatible = "ti,omap3-evm", "ti,omap3"
50
51- AM335X EVM : Software Developement Board for AM335x
52  compatible = "ti,am335x-evm", "ti,am33xx", "ti,omap3"
53
54- AM335X Bone : Low cost community board
55  compatible = "ti,am335x-bone", "ti,am33xx", "ti,omap3"
56
57- OMAP5 EVM : Evaluation Module
58  compatible = "ti,omap5-evm", "ti,omap5"
59