Received-SPF: pass (google.com: domain of linux-kernel+bounces-88797-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) client-ip=2604:1380:45d1:ec00::1;
Date: Fri, 1 Mar 2024 17:07:07 +0000
From: Conor Dooley <conor@kernel.org>
To: Frank Li <Frank.li@nxp.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>, Mark Brown <broonie@kernel.org>,
	Rob Herring <robh@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 v2 3/4] ASoC: dt-bindings: fsl-sai: allow only one
 dma-names
Message-ID: <20240301-deluxe-tiptoeing-741af7d620b9@spud>
References: <20240227-asrc_8qxp-v2-0-521bcc7eb1c0@nxp.com>
 <20240227-asrc_8qxp-v2-3-521bcc7eb1c0@nxp.com>
 <20240229-husband-penalty-8c1ab0f57f55@spud>
 <20240229-rundown-isotope-954ba9ea4c57@spud>
 <ZeDdMJlxBL4SGkws@lizhi-Precision-Tower-5810>
 <20240301-crudeness-resale-3c0a1228850d@spud>
 <ZeIGXEJ3l4tgjmxT@lizhi-Precision-Tower-5810>
Precedence: bulk
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="6B1Z/Uo6ygJQ4MXY"
Content-Disposition: inline
In-Reply-To: <ZeIGXEJ3l4tgjmxT@lizhi-Precision-Tower-5810>


--6B1Z/Uo6ygJQ4MXY
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Mar 01, 2024 at 11:46:20AM -0500, Frank Li wrote:
> On Fri, Mar 01, 2024 at 04:05:25PM +0000, Conor Dooley wrote:
> > On Thu, Feb 29, 2024 at 02:38:24PM -0500, Frank Li wrote:
> > > On Thu, Feb 29, 2024 at 06:57:29PM +0000, Conor Dooley wrote:
> > > > On Thu, Feb 29, 2024 at 06:55:58PM +0000, Conor Dooley wrote:
> > > > > On Tue, Feb 27, 2024 at 03:54:11PM -0500, Frank Li wrote:
> > > > > > Some sai only connect one direction. So allow only "rx" or "tx"=
 for
> > > > > > dma-names.
> > > > >=20
> > > > > Which sai? Can you restrict this per compatible please, so that s=
omeone
> > > > > cannot add 2 dmas for ones where only the tx is supported.
> > > > >=20
> > > > > |  dmas:
> > > > > |    minItems: 1
> > > > > |    items:
> > > > > |      - description: DMA controller phandle and request line for=
 RX
> > > > > |      - description: DMA controller phandle and request line for=
 TX
> > > > >=20
> > > > > The binding already allows only one, but it documents that the fi=
rst dma
> > > > > is always the RX dma, and that doesn't change with this patch..
> > > >=20
> > > > I said "doesn't change" - but I don't think you can change this
> > > > trivially, as something could rely on the first dma being the rx on=
e.
> > > > You'd have to check that there is nothing using these using indices
> > > > rather than names before making any changes here.
> > >=20
> > > Linux driver and dts with tx only work well. Only issue is dtb_check =
will
> > > report error. I want to eliminate these DTB_CHECK warning.
> >=20
> > Linux is not the only user of these bindings, citing linux as your
> > evidence here is only sufficient if no other users exist. Do they?
>=20
> But, 'dmas' should be common property for all these bindings? I don't thi=
nk
> they use 'descriptions:' property, which should guide dts writer to write
> dts file. actually words 'DMA controller phandle and request line' just
> nonsense words. let 'regs', it'd better descript at 'reg-names' instead
> of 'regs' if reg-names exist. Only meansful words is "RX" and "TX", which
> already show at "dma-names".

None of this matters. If there's a documented order for these, which
there is, software is not obligated to use the names and can rely on the
order alone. You need to check that there are no other users which will
be broken by your proposed change.

> > > And it also reasonable, only rx or tx for a special SAI.
> > >=20
> > > Can we remove 'description'? dmas should already descripted at common=
 place
> > > and 'RX' and 'TX' are listed at 'dma-names'
> >=20
> > Removing the description has the same problem. The existing binding has
> > set a fixed order that you now want to make flexible.
>=20
> Actually original set minItems: is 1, which means allow 1 channel. but
> set items to force two channel.=20
>=20
> Does it work
>=20
> oneOf:
>   items:=20
>   	- description: TX
> 	- description: RX
>   items:
> 	- description: TX
>   items:
> 	- description: RX
>=20
> >=20
> > Thanks,
> > Conor.
>=20
>=20

--6B1Z/Uo6ygJQ4MXY
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iHUEABYIAB0WIQRh246EGq/8RLhDjO14tDGHoIJi0gUCZeILOwAKCRB4tDGHoIJi
0vPRAQD30nLmqvnQSjER93Ue59P+ueynbOrDKfMBE0R2y7D7TAD+NnAAqA7ycgcG
24A0m2khdUZJAoZ7TGqfgOL5wSHiMww=
=Mxzk
-----END PGP SIGNATURE-----

--6B1Z/Uo6ygJQ4MXY--