| Benoit Cousson | dc2d07e | 2011-08-10 13:32:08 +0200 | [diff] [blame^] | 1 | * Texas Instruments OMAP |
| 2 | |
| 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 | adresse 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. |
| 12 | |
| 13 | |
| 14 | Required 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 | |
| 21 | Optional properties: |
| 22 | - ti,no_idle_on_suspend: When present, it prevents the PM to idle the module |
| 23 | during suspend. |
| 24 | |
| 25 | |
| 26 | Example: |
| 27 | |
| 28 | spinlock@1 { |
| 29 | compatible = "ti,omap4-spinlock"; |
| 30 | ti,hwmods = "spinlock"; |
| 31 | }; |
| 32 | |
| 33 | |
| 34 | Boards: |
| 35 | |
| 36 | - OMAP3 BeagleBoard : Low cost community board |
| 37 | compatible = "ti,omap3-beagle", "ti,omap3" |
| 38 | |
| 39 | - OMAP4 SDP : Software Developement Board |
| 40 | compatible = "ti,omap4-sdp", "ti,omap4430" |
| 41 | |
| 42 | - OMAP4 PandaBoard : Low cost community board |
| 43 | compatible = "ti,omap4-panda", "ti,omap4430" |