[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150824132633.GF7139@leverpostej>
Date: Mon, 24 Aug 2015 14:26:33 +0100
From: Mark Rutland <mark.rutland@....com>
To: Qais Yousef <qais.yousef@...tec.com>
Cc: "alsa-devel@...a-project.org" <alsa-devel@...a-project.org>,
Rob Herring <robh+dt@...nel.org>,
Pawel Moll <Pawel.Moll@....com>,
Ian Campbell <ijc+devicetree@...lion.org.uk>,
Kumar Gala <galak@...eaurora.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 02/10] dt: add img,axd.txt device tree binding document
On Mon, Aug 24, 2015 at 01:39:11PM +0100, Qais Yousef wrote:
> Signed-off-by: Qais Yousef <qais.yousef@...tec.com>
> Cc: Rob Herring <robh+dt@...nel.org>
> Cc: Pawel Moll <pawel.moll@....com>
> Cc: Mark Rutland <mark.rutland@....com>
> Cc: Ian Campbell <ijc+devicetree@...lion.org.uk>
> Cc: Kumar Gala <galak@...eaurora.org>
> Cc: devicetree@...r.kernel.org
> Cc: linux-kernel@...r.kernel.org
> ---
> .../devicetree/bindings/sound/img,axd.txt | 34 ++++++++++++++++++++++
> 1 file changed, 34 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/sound/img,axd.txt
>
> diff --git a/Documentation/devicetree/bindings/sound/img,axd.txt b/Documentation/devicetree/bindings/sound/img,axd.txt
> new file mode 100644
> index 000000000000..6a8764a79d01
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/sound/img,axd.txt
> @@ -0,0 +1,34 @@
> +* AXD Audio Processing IP Binding *
> +
> +Required properties:
> +- compatible: "img,axd"
This sounds awfully generic. Is there not a more complete name?
> +- clocks: phandle for the clock that drives AXD.
> +- interrupts: the GIC interrupt where AXD is connected
> +- gic-irq: it takes two non-zero values, the first one is the host hwirq and
> + the second one is AXD's. Host's hwirq should match the value in
> + interrupts.
I don't understand what this gic-irq property is for; and it generally
doesn't look right.
Could you please describe what this is and why you thing it is
necessary?
> +
> +Optional properties:
> +- vpe: VPE number on which AXD should start. Must be provided if AXD is
> + running as a single VPE along Linux on the same core.
> + It can't be VPE0.
> + The VPE will be offlined before AXD is loaded.
Likewise could you please elaborate on this is?
What is a VPE number? What does it mean to start at that number?
> +- inbuf-size: size of shared input buffers area. By default it's 0x7800 bytes.
> +- outbuf-size: size of shared output buffers area. By default it's 0x3c000 bytes.
Is this something the kernel dynamically allocates? Why does this need
to be in the DT?
Thanks,
Mark.
> +
> +
> +Example:
> +
> + axdclk: axdclk@...M {
> + #clock-cells = <0>;
> + compatible = "fixed-clock";
> + clock-frequency = <400000000>;
> + };
> +
> + axd {
> + compatible = "img,axd";
> + clocks = <&axdclk>;
> + interrupts = <36 IRQ_TYPE_EDGE_RISING>;
> + gic-irq = <36 37>;
> + vpe = <1>;
> + };
> --
> 2.1.0
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists