From: Marek Vasut <marex@denx.de>
To: Shengjiu Wang <shengjiu.wang@gmail.com>
Cc: devicetree@vger.kernel.org, Fabio Estevam <festevam@gmail.com>,
Jaroslav Kysela <perex@perex.cz>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Nicolin Chen <nicoleotsuka@gmail.com>,
Rob Herring <robh+dt@kernel.org>, Takashi Iwai <tiwai@suse.com>,
Xiubo Li <Xiubo.Lee@gmail.com>,
alsa-devel@alsa-project.org
Subject: Re: [PATCH] ASoC: dt-bindings: fsl-sai: Convert to YAML DT schema
Date: Fri, 4 Nov 2022 12:22:13 +0100 [thread overview]
Message-ID: <55c564c9-af7a-bc34-0340-d31bf7ffb0c8@denx.de> (raw)
In-Reply-To: <CAA+D8ANyXq7N+QfupnncTiJjEb8AN7hnb6T-1Cf8xs8yfYUFfg@mail.gmail.com>
On 11/4/22 09:11, Shengjiu Wang wrote:
> On Fri, Nov 4, 2022 at 2:20 AM Marek Vasut <marex@denx.de> wrote:
>
>> Convert the SAI bindings to YAML DT schema to permit validation.
>> Add Shengjiu as maintainer, derived from sound/soc/fsl/fsl_sai.c
>> get_maintainer result.
>>
>> Describe existing used combinations of compatible strings, add the
>> missing imx7d-sai compatible string which is used on i.MX7 .
>>
>> Properties lsb-first, fsl,sai-synchronous-rx, fsl,sai-asynchronous,
>> fsl,dataline are no longer listed as required, since those are clearly
>> optional, even the description says so, so does their usage.
>>
>> Fix the undefined edma channel macro per arch/arm/boot/dts/vfxxx.dtsi ,
>> use the value itself just like in the vfxxx.dtsi .
>>
>> Document interrupts property, which was previously undocumented, but
>> it is required property of this IP.
>>
>> Document #sound-sai-cells, which should be zero for this IP.
>>
>> Document fsl,imx6ul-iomuxc-gpr and its dependency on MX6UL and
>> fsl,sai-mclk-direction-output .
>>
>> Signed-off-by: Marek Vasut <marex@denx.de>
>> ---
>> Cc: Fabio Estevam <festevam@gmail.com>
>> Cc: Jaroslav Kysela <perex@perex.cz>
>> Cc: Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
>> Cc: Liam Girdwood <lgirdwood@gmail.com>
>> Cc: Mark Brown <broonie@kernel.org>
>> Cc: Nicolin Chen <nicoleotsuka@gmail.com>
>> Cc: Rob Herring <robh+dt@kernel.org>
>> Cc: Shengjiu Wang <shengjiu.wang@gmail.com>
>> Cc: Takashi Iwai <tiwai@suse.com>
>> Cc: Xiubo Li <Xiubo.Lee@gmail.com>
>> Cc: alsa-devel@alsa-project.org
>> To: devicetree@vger.kernel.org
>> ---
>> .../devicetree/bindings/sound/fsl-sai.yaml | 188 ++++++++++++++++++
>>
>
> Documentation/devicetree/bindings/sound/fsl,sai.yaml
> I have done conversion. If there is any update/change, please send patch
> base on it.
I noticed that, thanks for that. I'll see if there is anything left to do.
prev parent reply other threads:[~2022-11-04 11:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 18:20 [PATCH] ASoC: dt-bindings: fsl-sai: Convert to YAML DT schema Marek Vasut
2022-11-03 22:24 ` Rob Herring
[not found] ` <CAA+D8ANyXq7N+QfupnncTiJjEb8AN7hnb6T-1Cf8xs8yfYUFfg@mail.gmail.com>
2022-11-04 11:22 ` Marek Vasut [this message]
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=55c564c9-af7a-bc34-0340-d31bf7ffb0c8@denx.de \
--to=marex@denx.de \
--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=krzysztof.kozlowski+dt@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=nicoleotsuka@gmail.com \
--cc=perex@perex.cz \
--cc=robh+dt@kernel.org \
--cc=shengjiu.wang@gmail.com \
--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).