Received-SPF: pass (google.com: domain of linux-kernel+bounces-75557-linux.lists.archive=gmail.com@vger.kernel.org designates 139.178.88.99 as permitted sender) client-ip=139.178.88.99;
Date: Wed, 21 Feb 2024 21:37:54 +0000
From: Conor Dooley <conor@kernel.org>
To: Marco Felsch <m.felsch@pengutronix.de>
Cc: jic23@kernel.org, lars@metafoo.de, robh+dt@kernel.org,
	krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
	denis.ciocca@st.com, linus.walleij@linaro.org,
	linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, kernel@pengutronix.de
Subject: Re: [PATCH] dt-bindings: iio: st-sensors: Add IIS2MDC magnetometer
Message-ID: <20240221-lubricant-machine-79054f117eb0@spud>
References: <20240221175810.3581399-1-m.felsch@pengutronix.de>
 <20240221-undecided-union-4078db711693@spud>
 <20240221191644.5r3ylr5w3cnfnrzj@pengutronix.de>
 <20240221-imitate-molar-81d93285ac77@spud>
 <20240221194518.3sm4o5i274ldpvzf@pengutronix.de>
Precedence: bulk
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="aCdhMTuN5ae1nNlN"
Content-Disposition: inline
In-Reply-To: <20240221194518.3sm4o5i274ldpvzf@pengutronix.de>


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

On Wed, Feb 21, 2024 at 08:45:18PM +0100, Marco Felsch wrote:
> Hi Conor,
>=20
> On 24-02-21, Conor Dooley wrote:
> > On Wed, Feb 21, 2024 at 08:16:44PM +0100, Marco Felsch wrote:
> > > On 24-02-21, Conor Dooley wrote:
> > > > On Wed, Feb 21, 2024 at 06:58:10PM +0100, Marco Felsch wrote:
> > > > > Add the iis2mdc magnetometer support which is equivalent to the l=
is2mdl.
> > > > >=20
> > > > > Signed-off-by: Marco Felsch <m.felsch@pengutronix.de>
> > > > > ---
> > > > >  Documentation/devicetree/bindings/iio/st,st-sensors.yaml | 1 +
> > > > >  1 file changed, 1 insertion(+)
> > > > >=20
> > > > > diff --git a/Documentation/devicetree/bindings/iio/st,st-sensors.=
yaml b/Documentation/devicetree/bindings/iio/st,st-sensors.yaml
> > > > > index fff7e3d83a02..ee593c8bbb65 100644
> > > > > --- a/Documentation/devicetree/bindings/iio/st,st-sensors.yaml
> > > > > +++ b/Documentation/devicetree/bindings/iio/st,st-sensors.yaml
> > > > > @@ -64,6 +64,7 @@ properties:
> > > > >            - st,lsm9ds0-gyro
> > > > >        - description: STMicroelectronics Magnetometers
> > > > >          enum:
> > > > > +          - st,iis2mdc
> > > >=20
> > > > Without a fallback compatible to the equivilent device, how does a
> > > > driver bind to this device?
> > >=20
> > > I skimed the datasheets and the driver already handles this binding
> > > exactly the same as the st,lis2mdl, so my assumption is they do match.
> > >=20
> > > Why do I you think we need a fallback compatible here?
> >=20
> > I didn't look at the driver, there was no mention of the driver already
> > having (undocumented) support for it. Since there was no driver change
> > alongside this patch, I thought you'd need a fallback compatible to
> > allow the driver to match against a compatible it recognises.
>=20
> I explicitly did not mention the driver in the commit message else I
> would have got a response like "dt-bindings have no dependency to
> drivers" ;)

Putting it under the --- line is always an option. Where there are
existing users but the compatible is just undocumented, this it's
helpful to do.

> > Besides, having fallback compatibles is the norm when one device has the
> > same programming model as another.
>=20
> Not for this binding according the driver.

If they don't have the same programming model, then describing them as
"equivalent" wouldn't be correct. That said, they seem to use the same
sensor settings when alls said and done (see st_magn_sensors_settings),
so I think they are actually compatible even if the driver has separate
match data for each.

Cheers,
Conor.

--aCdhMTuN5ae1nNlN
Content-Type: application/pgp-signature; name="signature.asc"

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

iHUEABYIAB0WIQRh246EGq/8RLhDjO14tDGHoIJi0gUCZdZtMgAKCRB4tDGHoIJi
0mhFAP4uPT1KilNvuJy11JVEqyK46NkPn3I0vD5H1rPev9iSUQD/c2IAJZDAfJpg
j6ckgYP2rWSx/t9GqIONxFD8RfJMegM=
=nU5D
-----END PGP SIGNATURE-----

--aCdhMTuN5ae1nNlN--