[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAGb2v65QP_+zO19B5zWpeww=yorXzftE2oo9kwhEY3pCVuXTnQ@mail.gmail.com>
Date: Thu, 24 Sep 2015 23:00:09 +0800
From: Chen-Yu Tsai <wens@...e.org>
To: Code Kipper <codekipper@...il.com>
Cc: Liam Girdwood <lgirdwood@...il.com>,
linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
Mark Brown <broonie@...nel.org>,
linux-sunxi <linux-sunxi@...glegroups.com>,
linux-kernel <linux-kernel@...r.kernel.org>,
alsa-devel@...a-project.org,
Maxime Ripard <maxime.ripard@...e-electrons.com>,
be17068@...rbole.bo.it
Subject: Re: [linux-sunxi][alsa-devel][PATCH 2/3] dt-binding: Add sunxi SPDIF
machine driver
On Thu, Sep 24, 2015 at 2:04 AM, <codekipper@...il.com> wrote:
> From: Marcus Cooper <codekipper@...il.com>
>
> Add device tree bindings for the SPDIF machine driver for Allwinner SoC
> devices.
Is there a particular reason for having 2 separate bindings for one piece of
hardware?
Also, both this binding and the driver bits look almost like imx-audio-spdif.
This seems like unneeded duplication. Can we generalize that and use it? Or
just use simple-card?
Regards
ChenYu
> Signed-off-by: Marcus Cooper <codekipper@...il.com>
> ---
> .../bindings/sound/sunxi-audio-spdif.txt | 36 ++++++++++++++++++++++
> 1 file changed, 36 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/sound/sunxi-audio-spdif.txt
>
> diff --git a/Documentation/devicetree/bindings/sound/sunxi-audio-spdif.txt b/Documentation/devicetree/bindings/sound/sunxi-audio-spdif.txt
> new file mode 100644
> index 0000000..b9e8152
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/sound/sunxi-audio-spdif.txt
> @@ -0,0 +1,36 @@
> +Allwinner audio complex with S/PDIF transceiver
> +
> +Required properties:
> +
> + - compatible : "Allwinner,sunxi-audio-spdif"
> +
> + - model : The user-visible name of this sound complex
> +
> + - spdif-controller : The phandle of the Allwinner S/PDIF controller
> +
> +
> +Optional properties:
> +
> + - spdif-out : This is a boolean property. If present, the
> + transmitting function of S/PDIF will be enabled,
> + indicating there's a physical S/PDIF out connector
> + or jack on the board or it's connecting to some
> + other IP block, such as an HDMI encoder or
> + display-controller.
> +
> + - spdif-in : This is a boolean property. If present, the receiving
> + function of S/PDIF will be enabled, indicating there
> + is a physical S/PDIF in connector/jack on the board.
> +
> +* Note: At least one of these two properties should be set in the DT binding.
> +
> +
> +Example:
> +
> +sound-spdif {
> + compatible = "allwinner,sunxi-audio-spdif";
> + model = "sunxi-spdif";
> + spdif-controller = <&spdif>;
> + spdif-out;
> + spdif-in;
> +};
> --
> 2.5.3
>
> --
> You received this message because you are subscribed to the Google Groups "linux-sunxi" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscribe@...glegroups.com.
> For more options, visit https://groups.google.com/d/optout.
--
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