Received-SPF: pass (google.com: domain of linux-kernel+bounces-188421-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) client-ip=2604:1380:4601:e00::3;
Content-Type: multipart/signed;
 boundary=814b05467eb5fb3d1194dffe0bcc9ad51fe1c1889dcbffafdae7b5a67172;
 micalg=pgp-sha256; protocol="application/pgp-signature"
Precedence: bulk
Mime-Version: 1.0
Date: Fri, 24 May 2024 09:52:04 +0200
Message-Id: <D1HPMKUW9LW5.2UGOGXXTNBB52@gmail.com>
Cc: <jonathanh@nvidia.com>, <robh@kernel.org>, <krzk+dt@kernel.org>,
 <conor+dt@kernel.org>, <corbet@lwn.net>, <andi.shyti@kernel.org>,
 <wsa+renesas@sang-engineering.com>, <ulf.hansson@linaro.org>,
 <adrian.hunter@intel.com>, <digetx@gmail.com>, <ldewangan@nvidia.com>,
 <mkumard@nvidia.com>
Subject: Re: [RFC PATCH 00/11] Introduce Tegra register config settings
From: "Thierry Reding" <thierry.reding@gmail.com>
To: "Krzysztof Kozlowski" <krzk@kernel.org>, "Krishna Yarlagadda"
 <kyarlagadda@nvidia.com>, <linux-tegra@vger.kernel.org>,
 <devicetree@vger.kernel.org>, <linux-doc@vger.kernel.org>,
 <linux-i2c@vger.kernel.org>, <linux-mmc@vger.kernel.org>,
 <linux-kernel@vger.kernel.org>
References: <20240506225139.57647-1-kyarlagadda@nvidia.com>
 <71c52a0d-b788-4bbd-b409-6e62e6aff222@kernel.org>
In-Reply-To: <71c52a0d-b788-4bbd-b409-6e62e6aff222@kernel.org>

--814b05467eb5fb3d1194dffe0bcc9ad51fe1c1889dcbffafdae7b5a67172
Mime-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=UTF-8

On Tue May 7, 2024 at 8:38 AM CEST, Krzysztof Kozlowski wrote:
> On 07/05/2024 00:51, Krishna Yarlagadda wrote:
> > =20
> >  Patch 01: Documentation about the device tree binding for common confi=
g framework.
> >  Patch 02: Common parser of the device tree config setting node for Teg=
ra SoC.
> >  Patch 03: Device tree binding documentation for config setting.
> >  Patch 04: Device tree binding documentation for the I2C config setting=
.
> >  Patch 05: Avoid config settings child node to be treated as I2C device=
.
> >  Patch 06: Move clock initialization code into new methods
> >  Patch 07: Using config settings in Tegra I2C driver for interface timi=
ng registers.
> >  Patch 08: Add Tegra234 I2C config settings in DT.
> >  Patch 09: Device tree binding documentation for the SDHCI config setti=
ng.
> >  Patch 10: Using config settings in Tegra SDHCI driver for tuning itera=
tion.
> >  Patch 11: Add Tegra234 SDHCI config settings in DT.
> >=20
> > Known Issues:
> >  - DTC warning for config 'missing or empty reg property for I2C nodes'
>
> Which should stop you from sending buggy code, till you fix it.

Okay, so this RFC series was meant to solicit comments on the general
approach of this. Fixing this known issue is fairly complicated and
involves patching DTC, which we would be prepared to do if this was
generally deemed acceptable, but doesn't seem like a worthwhile
undertaking until we know we can move ahead with this.

So rather than categorically NAKing something that was sent out as a
proposal looking for feedback on how to improve and turn this into
something acceptable, it'd be great to get constructive feedback on how
we can get there.

Thierry

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

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

iQIzBAABCAAdFiEEiOrDCAFJzPfAjcif3SOs138+s6EFAmZQRyUACgkQ3SOs138+
s6EYPRAApKj6TZ45ihKFbdihmJOaY25HqHqqAOmw/WIDGwBEJMrVVW41xioiMLzp
k32CEAFP5kxE3WPay97YquvQn7Vh4qhe64qYPr/UaTsr3TeklU2e/G/E1xfsTTAt
8jjR5dfSPG2uoCaHgQ5R+nOF1UTH5+1BLLPNF0rKacaFe90o/rLpH0YZG7lSH7Te
jOU8AinN/cd68weuz1aRdVcylA/XSUOy62QU6uJKAPSVNgfYMp5P1RE+drnyP15V
H5Xx9Y9QhWSfIoDVepJXLfZkz/l8MowjLxFVFg0P3On0A/rHTDilHHOntZoj1x3d
n2xFR35NZo7DdkewHcbMHUyrUrsSzTQC4JvjD7Ecx1HmpQTjo079AabM/mFdI9te
czUUPCzwlqr/GOyW8sIz00POG0+jzVLNXJKWKJOkbTJepXkR95EVSYS53wpcAUp0
oOW5dHWbl64xDCZa4BFoIJZ3N8tYnPEetfGdPxFklNnjKwvGWuFqmuHyKQb9O+Js
/bpmc+xjo4kghNnoU55N2pDzizeDahkutILnSY2pd/MdttXlfD9C7xQAYjVFPs6y
gPPHNZ9Cz8AjV3HN8N87CqB1plGzLpF9MnXZgyPS84PYDwG+G2bJAaT4vUHznr8/
RtYG3PwbFX06/nGAkYDQOmpkaK0A7L4Sz0sAdw+MkRS/xElALp4=
=AtSK
-----END PGP SIGNATURE-----

--814b05467eb5fb3d1194dffe0bcc9ad51fe1c1889dcbffafdae7b5a67172--