Boris,
On Tue, Jan 13, 2015 at 07:46:18PM +0100, Boris Brezillon wrote:
> Add documentation for the dumb demuxer.
>
> Signed-off-by: Boris Brezillon <boris.brezil...@free-electrons.com>
> ---
> .../bindings/interrupt-controller/dumb-demux.txt | 34
> ++++++++++++++++++++++
> 1 file changed, 34 insertions(+)
> create mode 100644
> Documentation/devicetree/bindings/interrupt-controller/dumb-demux.txt
>
> diff --git
> a/Documentation/devicetree/bindings/interrupt-controller/dumb-demux.txt
> b/Documentation/devicetree/bindings/interrupt-controller/dumb-demux.txt
> new file mode 100644
> index 0000000..1c777ef
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/interrupt-controller/dumb-demux.txt
> @@ -0,0 +1,34 @@
> +* Generic Dumb Interrupt Demultiplexer
> +
> +This Dumb demultiplixer simply forward all incoming interrupts to its
> +enabled/unmasked children.
Please forgive the potentially naïve question, but what hardware is this
describing?
thx,
Jason.
> +
> +Required properties:
> +- compatible: Should be "irqchip-dumb-demux".
> +- interrupt-controller: Identifies the node as an interrupt controller.
> +- interrupts-extended or interrupt-parent and interrupts: Reference the
> source
> + interrupt connected to this dumb demuxer.
> +- #interrupt-cells: The number of cells to define the interrupts (should be
> 1).
> + The only cell is the IRQ number.
> +- irqs: u32 bitfield specifying the interrupts provided by the demuxer.
> +
> +Examples:
> + /*
> + * Dumb demuxer controller
> + */
> + dumb_irq1_demux: dumb-irq-demux@1 {
> + compatible = "irqchip-dumb-demux";
> + interrupt-controller;
> + #interrupt-cells = <1>;
> + interrupts-extended = <&aic 1 IRQ_TYPE_LEVEL_HIGH 7>;
> + irqs = <0x3f>;
> + };
> +
> + /*
> + * Device connected on this dumb demuxer
> + */
> + dma: dma-controller@ffffec00 {
> + compatible = "atmel,at91sam9g45-dma";
> + reg = <0xffffec00 0x200>;
> + interrupts-extended = <&dumb_irq1_demux 0>;
> + };
> --
> 1.9.1
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
