From: Rob Herring <robh@kernel.org>
To: Frank Li <Frank.li@nxp.com>
Cc: Conor Dooley <conor@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
Shengjiu Wang <shengjiu.wang@nxp.com>,
linux-sound@vger.kernel.org, devicetree@vger.kernel.org,
imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 3/4] ASoC: dt-bindings: fsl-sai: allow only one dma-names
Date: Wed, 6 Mar 2024 14:55:24 -0600 [thread overview]
Message-ID: <20240306205524.GB587561-robh@kernel.org> (raw)
In-Reply-To: <ZejDQddMp17RD6Yk@lizhi-Precision-Tower-5810>
On Wed, Mar 06, 2024 at 02:25:53PM -0500, Frank Li wrote:
> On Wed, Mar 06, 2024 at 06:45:13PM +0000, Conor Dooley wrote:
> > On Tue, Mar 05, 2024 at 12:33:04PM -0500, Frank Li wrote:
> > > Some sai only connect one direction dma (rx/tx) in SOC. For example:
> > > imx8qxp sai5 only connect tx dma channel. So allow only one "rx" or "tx"
> > > for dma-names.
> > >
> > > Remove description under dmas because no user use index to get dma channel.
> > > All user use 'dma-names' to get correct dma channel. dma-names already in
> > > 'required' list.
> >
> > Acked-by: Conor Dooley <conor.dooley@microchip.com>
> >
> > > Signed-off-by: Frank Li <Frank.Li@nxp.com>
> > > ---
> > > Documentation/devicetree/bindings/sound/fsl,sai.yaml | 13 ++++++-------
> > > 1 file changed, 6 insertions(+), 7 deletions(-)
> > >
> > > diff --git a/Documentation/devicetree/bindings/sound/fsl,sai.yaml b/Documentation/devicetree/bindings/sound/fsl,sai.yaml
> > > index 2456d958adeef..6f551c68d33db 100644
> > > --- a/Documentation/devicetree/bindings/sound/fsl,sai.yaml
> > > +++ b/Documentation/devicetree/bindings/sound/fsl,sai.yaml
> > > @@ -81,15 +81,14 @@ properties:
> > >
> > > dmas:
> > > minItems: 1
> > > - items:
> > > - - description: DMA controller phandle and request line for RX
> > > - - description: DMA controller phandle and request line for TX
> > > + maxItems: 2
> > >
> > > dma-names:
> > > - minItems: 1
> > > - items:
> > > - - const: rx
> > > - - const: tx
> > > + oneOf:
> > > + - items:
> > > + - const: rx
> > > + - const: tx
> > > + - enum: [ rx, tx ]
> >
> > I'm not entirely sure if this was Rob's suggestion, I got the impression
> > he was suggesting that in the two items case we'd not care about the
> > order. But while I think this is different to that suggestion it's also
> > not wrong.
>
> I log this at cover-letter. b4 can't support write change log at every
> patch yet.
It never will (probably). That's because it doesn't need to. You can
just do it with git. When you edit the commit message, then after the
tags, Add '---' and put whatever you want after. That works as long as
the commit is applied from a patch as 'git am' will drop it.
> Rob's suggest was not work. dt-binding check complain too long
> if there are two dma-names = "rx", "tx".
So I'm wrong or you didn't have it correct? No way to tell with your
explanation. Let me give you the exact schema:
dma-names:
minItems: 1
items:
- enum: [ rx, tx ]
- const: tx
This says we can have 1 or 2 entries. The first entry can be either rx
or tx. The 2nd entry must be tx. That's what you want. However, '"tx",
"tx"' is allowed with the above, but we enforce items to be unique
elsewhere. Or I thought we did, but we relaxed '.*-names$' at some
point. I'm going to fix that now.
Rob
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-03-06 20:55 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-05 17:33 [PATCH v4 0/4] arm64: dts: imx8qxp add asrc and sai Frank Li
2024-03-05 17:33 ` [PATCH v4 1/4] ASoC: dt-bindings: fsl,imx-asrc/spdif: Add power-domains property Frank Li
2024-03-06 18:53 ` Conor Dooley
2024-03-05 17:33 ` [PATCH v4 2/4] ASoC: dt-bindings: fsl,imx-asrc: update max interrupt numbers Frank Li
2024-03-06 18:47 ` Conor Dooley
2024-03-06 20:25 ` Rob Herring
2024-03-06 20:53 ` Frank Li
2024-03-06 23:00 ` Rob Herring
2024-03-05 17:33 ` [PATCH v4 3/4] ASoC: dt-bindings: fsl-sai: allow only one dma-names Frank Li
2024-03-06 18:45 ` Conor Dooley
2024-03-06 19:25 ` Frank Li
2024-03-06 19:45 ` Conor Dooley
2024-03-06 20:25 ` Frank Li
2024-03-06 20:55 ` Rob Herring [this message]
2024-03-06 21:19 ` Frank Li
2024-03-06 22:58 ` Rob Herring
2024-03-07 2:02 ` Frank Li
2024-03-07 18:56 ` Conor Dooley
2024-03-05 17:33 ` [PATCH v4 4/4] arm64: dts: imx8qxp: add asrc[0,1], esai0, spdif[0,1] and sai[4,5] Frank Li
2024-03-06 7:20 ` [PATCH v4 4/4] arm64: dts: imx8qxp: add asrc[0, 1], esai0, spdif[0, 1] and sai[4, 5] Alexander Stein
2024-03-06 15:19 ` Frank Li
2024-03-07 7:22 ` Alexander Stein
2024-03-07 16:26 ` Frank Li
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=20240306205524.GB587561-robh@kernel.org \
--to=robh@kernel.org \
--cc=Frank.li@nxp.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=shengjiu.wang@nxp.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).