-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
ARM: OMAP: omap_device: Add a method to build an omap_device from a D…
…T node Add a notifier called during device_add phase. If an of_node is present, retrieve the hwmod entry in order to populate properly the omap_device structure. For the moment the resource from the device-tree are overloaded. DT does not support named resource yet, and thus, most driver will not work without that information. Add a documentation to capture the specifics OMAP bindings needed for device-tree support. Signed-off-by: Benoit Cousson <b-cousson@ti.com> Cc: Grant Likely <grant.likely@secretlab.ca> Signed-off-by: Kevin Hilman <khilman@ti.com>
- Loading branch information
Benoit Cousson
authored and
Kevin Hilman
committed
Oct 4, 2011
1 parent
a4f6cdb
commit dc2d07e
Showing
2 changed files
with
144 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,43 @@ | ||
* 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: | ||
adresse 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" |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters