From: Rob Herring <robh@kernel.org>
To: Shengjiu Wang <shengjiu.wang@nxp.com>
Cc: lgirdwood@gmail.com, broonie@kernel.org, perex@perex.cz,
tiwai@suse.com, timur@kernel.org, nicoleotsuka@gmail.com,
Xiubo.Lee@gmail.com, festevam@gmail.com, shawnguo@kernel.org,
s.hauer@pengutronix.de, kernel@pengutronix.de, linux-imx@nxp.com,
linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org,
linuxppc-dev@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 2/2] ASoC: dt-bindings: imx-akcodec: Add binding doc for akcodec machine driver
Date: Mon, 3 May 2021 12:00:30 -0500 [thread overview]
Message-ID: <20210503170030.GA1987906@robh.at.kernel.org> (raw)
In-Reply-To: <1619157107-3734-2-git-send-email-shengjiu.wang@nxp.com>
On Fri, Apr 23, 2021 at 01:51:47PM +0800, Shengjiu Wang wrote:
> Imx-akcodec is a new added machine driver for supporting
> ak4458/ak5558/ak5552/ak4497 codec on i.MX platforms.
>
> Signed-off-by: Shengjiu Wang <shengjiu.wang@nxp.com>
> ---
> .../bindings/sound/imx-audio-akcodec.yaml | 60 +++++++++++++++++++
> 1 file changed, 60 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/sound/imx-audio-akcodec.yaml
>
> diff --git a/Documentation/devicetree/bindings/sound/imx-audio-akcodec.yaml b/Documentation/devicetree/bindings/sound/imx-audio-akcodec.yaml
> new file mode 100644
> index 000000000000..7419bf7224e9
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/sound/imx-audio-akcodec.yaml
> @@ -0,0 +1,60 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/sound/imx-audio-akcodec.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: NXP i.MX audio complex with AK4458/AK5558/AK5552/AK4497 codec
Looks like the existing fsl-asoc-card.txt? You should convert to schema
and use that. Otherwise, my comments are based on this all being 'new'.
> +
> +maintainers:
> + - Shengjiu Wang <shengjiu.wang@nxp.com>
> +
> +properties:
> + compatible:
> + enum:
> + - fsl,imx8mq-audio-ak4458
> + - fsl,imx8mq-audio-ak4497
> + - fsl,imx8mq-audio-ak5558
> + - fsl,imx-audio-ak4497
> + - fsl,imx-audio-ak4458
> + - fsl,imx-audio-ak5558
> + - fsl,imx-audio-ak5552
I continue to not understand why audio bindings need the codec(s) in the
compatible strings. Can't you look up the codec thru the audio-codec
property?
> +
> + model:
> + $ref: /schemas/types.yaml#/definitions/string
> + description: User specified audio sound card name
> +
> + audio-cpu:
> + $ref: /schemas/types.yaml#/definitions/phandle
> + description: The phandle of a CPU DAI controller
> +
> + audio-codec:
> + description: The phandle of Codec DAI controllers, there are two
> + controllers maximum.
We have the common 'sound-dai' property. See the simple-card.yaml
binding.
> +
> + audio-asrc:
> + $ref: /schemas/types.yaml#/definitions/phandle
> + description: The phandle of ASRC. It can be absent if there's no
> + need to add ASRC support via DPCM.
Needs a vendor prefix.
> +
> + fsl,tdm:
> + $ref: /schemas/types.yaml#/definitions/flag
> + description: |
> + This is a boolean property. If present, the TDM mode is enabled.
But this one seems like something that could or should be common.
> +
> +required:
> + - compatible
> + - model
> + - audio-cpu
> + - audio-codec
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + sound-ak4458 {
> + compatible = "fsl,imx-audio-ak4458";
> + model = "ak4458-audio";
> + audio-cpu = <&sai1>;
> + audio-codec = <&ak4458_1>, <&ak4458_2>;
> + };
> --
> 2.17.1
>
next prev parent reply other threads:[~2021-05-03 17:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-23 5:51 [PATCH 1/2] ASoC: imx-akcodec: Add imx-akcodec machine driver Shengjiu Wang
2021-04-23 5:51 ` [PATCH 2/2] ASoC: dt-bindings: imx-akcodec: Add binding doc for akcodec " Shengjiu Wang
2021-05-03 17:00 ` Rob Herring [this message]
2021-05-08 11:14 ` Shengjiu Wang
2021-05-04 6:57 ` [PATCH 1/2] ASoC: imx-akcodec: Add imx-akcodec " Marco Felsch
2021-05-08 11:11 ` Shengjiu Wang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210503170030.GA1987906@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=Xiubo.Lee@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=nicoleotsuka@gmail.com \
--cc=perex@perex.cz \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=shengjiu.wang@nxp.com \
--cc=timur@kernel.org \
--cc=tiwai@suse.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).