Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Wed, 21 Sep 2022 22:01:59 +0200
From:   Wolfram Sang <wsa+renesas@sang-engineering.com>
To:     Asmaa Mnebhi <asmaa@nvidia.com>
Cc:     Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        "robh@kernel.org" <robh@kernel.org>,
        "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
        "linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
        Khalil Blaiech <kblaiech@nvidia.com>
Subject: How to remove DT support from a driver? (was Re: [PATCH v5 8/8] i2c:
 i2c-mlxbf.c: Update binding devicetree)
Message-ID: <Yyttt3DiQpMZYejA@shikoro>
Mail-Followup-To: Wolfram Sang <wsa+renesas@sang-engineering.com>,
        Asmaa Mnebhi <asmaa@nvidia.com>,
        Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        "robh@kernel.org" <robh@kernel.org>,
        "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
        "linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
        Khalil Blaiech <kblaiech@nvidia.com>
References: <20220920174736.9766-1-asmaa@nvidia.com>
 <20220920174736.9766-9-asmaa@nvidia.com>
 <20220921065506.6cu6p2cpu3zfhtie@krzk-bin>
 <CH2PR12MB3895572575B5BED5DAFFAA29D74F9@CH2PR12MB3895.namprd12.prod.outlook.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
        protocol="application/pgp-signature"; boundary="Pm1Lj2tDeBpt8LQv"
Content-Disposition: inline
In-Reply-To: <CH2PR12MB3895572575B5BED5DAFFAA29D74F9@CH2PR12MB3895.namprd12.prod.outlook.com>
Precedence: bulk


--Pm1Lj2tDeBpt8LQv
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi,

> I have a question for you and Wolfram, we don=E2=80=99t use device trees =
and
> are not planning to use device trees; we only use ACPI tables. But I
> think when Khalil submitted the first version of the i2c-mlxbf.c
> driver, it was requested from him to add devicetree support. Do you
> know why? Is it possible to remove the device tree support and so this
> doc? or is devicetree support a requirement regardless of the actual
> implementation?=20

The first version sent from Khalil to the public I2C mailing list already
had DT bindings [1]. I don't see a sign of someone of the public list
requesting DT bindings. Maybe it was company internal?

Technically, there is no requirement to support DT, especially since you
have working ACPI. I don't know the process, though, of removing DT
support. You would basically need to be sure that no user made use of
the DT bindings introduced before. I don't know to what degree you can
assume that.

Maybe the DT list has more to add here?

Happy hacking,

   Wolfram

[1] http://patchwork.ozlabs.org/project/linux-i2c/list/?series=3D73827&stat=
e=3D*


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

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

iQIzBAABCgAdFiEEOZGx6rniZ1Gk92RdFA3kzBSgKbYFAmMrbbcACgkQFA3kzBSg
KbaIvA/9FSSkOUXl9RVM+YmOszSc7oaeV13hKjWUwmowouGcHCSMfdZKi/X9Natc
NnzoPup7TRc2DXsMhHof2QSijm2+q6SXGEqK5cdED8/O4pm5VYziNpPbvzf5l6hl
Tf9JkpTG5CuQFb9niieM+ZeZ9nyqIKkYODITcxKz8HFoijxxXa8eoN42gwVRv1Z/
R4gcqkfSU2ySBsMOvmrocmKocd6XcT+LycwGF5vODGECkKOm/9o1w5oojQh8gmMF
nF9IANO6DrZeq7MbNCBmkxJQV/RgwiHdzF91hWvWO95E4UyPe3RcC9mOgJTGP3La
1f/68TPXjDAncICLdolg7G35aotOFDkiCqyBRsNgkXM11Ms/3YG1IHtwFbIMCexm
rHqcE7KEzuzdqZJycOXfgdPPubAC6IePkpQC4OfOtH0KiIOTOw0yso8lGNylKobq
HM2Nt8SbFgHjrRER+bnvtXL9ZylS9QrjI2TEMYzubRA+Ir4BJ8yroCk/TyLcGWLm
NH2khopzyRIRC9Fsz8oFVRgMP66/rdclx3P1rx1oRWjtd9UiBzh21qZRYddfB2wN
00LCOowrR7m4BojLO2wma9Aiff+ieMFAeyBvllrRpHXgAkgckhvldj4PHdV/WfVE
f4AkGpE8Pfs0BxfdMrqLEJIYQRB3yenrp737X//sNae3QGluHuI=
=YihV
-----END PGP SIGNATURE-----

--Pm1Lj2tDeBpt8LQv--