mirror of
https://github.com/torvalds/linux.git
synced 2024-12-25 20:32:22 +00:00
791d3ef2e1
'interrupt-parent' is often documented as part of define bindings, but it is really outside the scope of a device binding. It's never required in a given node as it is often inherited from a parent node. Or it can be implicit if a parent node is an 'interrupt-controller' node. So remove it from all the binding files. Cc: Mark Rutland <mark.rutland@arm.com> Cc: devicetree@vger.kernel.org Signed-off-by: Rob Herring <robh@kernel.org>
37 lines
1.3 KiB
Plaintext
37 lines
1.3 KiB
Plaintext
* Texas Instruments OMAP2+ McBSP module
|
|
|
|
Required properties:
|
|
- compatible: "ti,omap2420-mcbsp" for McBSP on OMAP2420
|
|
"ti,omap2430-mcbsp" for McBSP on OMAP2430
|
|
"ti,omap3-mcbsp" for McBSP on OMAP3
|
|
"ti,omap4-mcbsp" for McBSP on OMAP4 and newer SoC
|
|
- reg: Register location and size, for OMAP4+ as an array:
|
|
<MPU access base address, size>,
|
|
<L3 interconnect address, size>;
|
|
- reg-names: Array of strings associated with the address space
|
|
- interrupts: Interrupt numbers for the McBSP port, as an array in case the
|
|
McBSP IP have more interrupt lines:
|
|
<OCP compliant irq>,
|
|
<TX irq>,
|
|
<RX irq>;
|
|
- interrupt-names: Array of strings associated with the interrupt numbers
|
|
- ti,buffer-size: Size of the FIFO on the port (OMAP2430 and newer SoC)
|
|
- ti,hwmods: Name of the hwmod associated to the McBSP port
|
|
|
|
Example:
|
|
|
|
mcbsp2: mcbsp@49022000 {
|
|
compatible = "ti,omap3-mcbsp";
|
|
reg = <0x49022000 0xff>,
|
|
<0x49028000 0xff>;
|
|
reg-names = "mpu", "sidetone";
|
|
interrupts = <0 17 0x4>, /* OCP compliant interrupt */
|
|
<0 62 0x4>, /* TX interrupt */
|
|
<0 63 0x4>, /* RX interrupt */
|
|
<0 4 0x4>; /* Sidetone */
|
|
interrupt-names = "common", "tx", "rx", "sidetone";
|
|
interrupt-parent = <&intc>;
|
|
ti,buffer-size = <1280>;
|
|
ti,hwmods = "mcbsp2";
|
|
};
|