1 * Texas Instruments OMAP
3 OMAP is currently using a static file per SoC family to describe the
4 IPs present in the SoC.
5 On top of that an omap_device is created to extend the platform_device
6 capabilities and to allow binding with one or several hwmods.
7 The hwmods will contain all the information to build the device:
8 address range, irq lines, dma lines, interconnect, PRCM register,
9 clock domain, input clocks.
10 For the moment just point to the existing hwmod, the next step will be
11 to move data from hwmod to device-tree representation.
15 - compatible: Every devices present in OMAP SoC should be in the
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
22 - ti,no_idle_on_suspend: When present, it prevents the PM to idle the module
29 compatible = "ti,omap4-spinlock";
30 ti,hwmods = "spinlock";
36 - OMAP3 BeagleBoard : Low cost community board
37 compatible = "ti,omap3-beagle", "ti,omap3"
39 - OMAP3 Tobi with Overo : Commercial expansion board with daughter board
40 compatible = "ti,omap3-tobi", "ti,omap3-overo", "ti,omap3"
42 - OMAP4 SDP : Software Development Board
43 compatible = "ti,omap4-sdp", "ti,omap4430"
45 - OMAP4 PandaBoard : Low cost community board
46 compatible = "ti,omap4-panda", "ti,omap4430"
48 - OMAP3 EVM : Software Development Board for OMAP35x, AM/DM37x
49 compatible = "ti,omap3-evm", "ti,omap3"
51 - AM335X EVM : Software Development Board for AM335x
52 compatible = "ti,am335x-evm", "ti,am33xx", "ti,omap3"
54 - AM335X Bone : Low cost community board
55 compatible = "ti,am335x-bone", "ti,am33xx", "ti,omap3"
57 - OMAP5 EVM : Evaluation Module
58 compatible = "ti,omap5-evm", "ti,omap5"