diff options
63 files changed, 1596 insertions, 1118 deletions
diff --git a/Documentation/devicetree/bindings/arm/omap/dsp.txt b/Documentation/devicetree/bindings/arm/omap/dsp.txt new file mode 100644 index 000000000000..d3830a32ce08 --- /dev/null +++ b/Documentation/devicetree/bindings/arm/omap/dsp.txt | |||
| @@ -0,0 +1,14 @@ | |||
| 1 | * TI - DSP (Digital Signal Processor) | ||
| 2 | |||
| 3 | TI DSP included in OMAP SoC | ||
| 4 | |||
| 5 | Required properties: | ||
| 6 | - compatible : Should be "ti,omap3-c64" for OMAP3 & 4 | ||
| 7 | - ti,hwmods: "dsp" | ||
| 8 | |||
| 9 | Examples: | ||
| 10 | |||
| 11 | dsp { | ||
| 12 | compatible = "ti,omap3-c64"; | ||
| 13 | ti,hwmods = "dsp"; | ||
| 14 | }; | ||
diff --git a/Documentation/devicetree/bindings/arm/omap/iva.txt b/Documentation/devicetree/bindings/arm/omap/iva.txt new file mode 100644 index 000000000000..6d6295171358 --- /dev/null +++ b/Documentation/devicetree/bindings/arm/omap/iva.txt | |||
| @@ -0,0 +1,19 @@ | |||
| 1 | * TI - IVA (Imaging and Video Accelerator) subsystem | ||
| 2 | |||
| 3 | The IVA contain various audio, video or imaging HW accelerator | ||
| 4 | depending of the version. | ||
| 5 | |||
| 6 | Required properties: | ||
| 7 | - compatible : Should be: | ||
| 8 | - "ti,ivahd" for OMAP4 | ||
| 9 | - "ti,iva2.2" for OMAP3 | ||
| 10 | - "ti,iva2.1" for OMAP2430 | ||
| 11 | - "ti,iva1" for OMAP2420 | ||
| 12 | - ti,hwmods: "iva" | ||
| 13 | |||
| 14 | Examples: | ||
| 15 | |||
| 16 | iva { | ||
| 17 | compatible = "ti,ivahd", "ti,iva"; | ||
| 18 | ti,hwmods = "iva"; | ||
| 19 | }; | ||
diff --git a/Documentation/devicetree/bindings/arm/omap/l3-noc.txt b/Documentation/devicetree/bindings/arm/omap/l3-noc.txt new file mode 100644 index 000000000000..6888a5efc860 --- /dev/null +++ b/Documentation/devicetree/bindings/arm/omap/l3-noc.txt | |||
| @@ -0,0 +1,19 @@ | |||
| 1 | * TI - L3 Network On Chip (NoC) | ||
| 2 | |||
| 3 | This version is an implementation of the generic NoC IP | ||
| 4 | provided by Arteris. | ||
| 5 | |||
| 6 | Required properties: | ||
| 7 | - compatible : Should be "ti,omap3-l3-smx" for OMAP3 family | ||
| 8 | Should be "ti,omap4-l3-noc" for OMAP4 family | ||
| 9 | - ti,hwmods: "l3_main_1", ... One hwmod for each noc domain. | ||
| 10 | |||
| 11 | Examples: | ||
| 12 | |||
| 13 | ocp { | ||
| 14 | compatible = "ti,omap4-l3-noc", "simple-bus"; | ||
| 15 | #address-cells = <1>; | ||
| 16 | #size-cells = <1>; | ||
| 17 | ranges; | ||
| 18 | ti,hwmods = "l3_main_1", "l3_main_2", "l3_main_3"; | ||
| 19 | }; | ||
diff --git a/Documentation/devicetree/bindings/arm/omap/mpu.txt b/Documentation/devicetree/bindings/arm/omap/mpu.txt new file mode 100644 index 000000000000..1a5a42ce21bb --- /dev/null +++ b/Documentation/devicetree/bindings/arm/omap/mpu.txt | |||
| @@ -0,0 +1,27 @@ | |||
| 1 | * TI - MPU (Main Processor Unit) subsystem | ||
| 2 | |||
| 3 | The MPU subsystem contain one or several ARM cores | ||
| 4 | depending of the version. | ||
| 5 | The MPU contain CPUs, GIC, L2 cache and a local PRCM. | ||
| 6 | |||
| 7 | Required properties: | ||
| 8 | - compatible : Should be "ti,omap3-mpu" for OMAP3 | ||
| 9 | Should be "ti,omap4-mpu" for OMAP4 | ||
| 10 | - ti,hwmods: "mpu" | ||
| 11 | |||
| 12 | Examples: | ||
| 13 | |||
| 14 | - For an OMAP4 SMP system: | ||
| 15 | |||
| 16 | mpu { | ||
| 17 | compatible = "ti,omap4-mpu"; | ||
| 18 | ti,hwmods = "mpu"; | ||
| 19 | }; | ||
| 20 | |||
| 21 | |||
| 22 | - For an OMAP3 monocore system: | ||
| 23 | |||
| 24 | mpu { | ||
| 25 | compatible = "ti,omap3-mpu"; | ||
| 26 | ti,hwmods = "mpu"; | ||
| 27 | }; | ||
diff --git a/Documentation/devicetree/bindings/arm/omap/omap.txt b/Documentation/devicetree/bindings/arm/omap/omap.txt new file mode 100644 index 000000000000..dbdab40ed3a6 --- /dev/null +++ b/Documentation/devicetree/bindings/arm/omap/omap.txt | |||
| @@ -0,0 +1,43 @@ | |||
| 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: | ||
