From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 606FB10EF for ; Mon, 19 Dec 2022 09:39:59 +0000 (UTC) Received: from lhrpeml500005.china.huawei.com (unknown [172.18.147.201]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4NbF213xkJz6HJd5; Mon, 19 Dec 2022 17:35:53 +0800 (CST) Received: from localhost (10.45.149.76) by lhrpeml500005.china.huawei.com (7.191.163.240) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.34; Mon, 19 Dec 2022 09:39:49 +0000 Date: Mon, 19 Dec 2022 09:39:46 +0000 From: Jonathan Cameron To: Krzysztof Kozlowski CC: Han Xu , Jonathan Cameron , "Rob Herring" , Krzysztof Kozlowski , Lars-Peter Clausen , Sean Nyekjaer , Nuno =?ISO-8859-1?Q?S=E1?= , Matti Vaittinen , "Haibo Chen" , Miquel Raynal , "Clark Wang" , , , Subject: Re: [PATCH v3 3/4] dt-bindings: iio: accel: fxls8962af: add new compatible string Message-ID: <20221219093946.00007411@Huawei.com> In-Reply-To: <76c5cdd9-7b90-7ce5-02c4-a2a6e5bb3a30@linaro.org> References: <20221213171536.1880089-1-han.xu@nxp.com> <20221213171536.1880089-5-han.xu@nxp.com> <76c5cdd9-7b90-7ce5-02c4-a2a6e5bb3a30@linaro.org> Organization: Huawei Technologies Research and Development (UK) Ltd. X-Mailer: Claws Mail 4.1.0 (GTK 3.24.33; x86_64-w64-mingw32) Precedence: bulk X-Mailing-List: imx@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Originating-IP: [10.45.149.76] X-ClientProxiedBy: lhrpeml500001.china.huawei.com (7.191.163.213) To lhrpeml500005.china.huawei.com (7.191.163.240) X-CFilter-Loop: Reflected On Wed, 14 Dec 2022 10:54:32 +0100 Krzysztof Kozlowski wrote: > On 13/12/2022 18:15, Han Xu wrote: > > Add new compatible string for the NXP FXLS8967AF accelerometer sensor. > > > > Signed-off-by: Han Xu > > > > --- > > changes in v3 > > - Start commit message in capital > > - Describe all these chips are compatible > > --- > > .../devicetree/bindings/iio/accel/nxp,fxls8962af.yaml | 4 ++++ > > 1 file changed, 4 insertions(+) > > > > diff --git a/Documentation/devicetree/bindings/iio/accel/nxp,fxls8962af.yaml b/Documentation/devicetree/bindings/iio/accel/nxp,fxls8962af.yaml > > index 65ce8ea14b52..8f07ade21abb 100644 > > --- a/Documentation/devicetree/bindings/iio/accel/nxp,fxls8962af.yaml > > +++ b/Documentation/devicetree/bindings/iio/accel/nxp,fxls8962af.yaml > > @@ -14,12 +14,16 @@ description: | > > SPI and I2C interface. > > https://www.nxp.com/docs/en/data-sheet/FXLS8962AF.pdf > > https://www.nxp.com/docs/en/data-sheet/FXLS8964AF.pdf > > + https://www.nxp.com/docs/en/data-sheet/FXLS8967AF.pdf > > > > properties: > > compatible: > > + description: > > + These chips are compatible with each other, just have different IDs. > > As pointed in other mail, the chips are not compatible, so drop the comment. The difference is an ID register. Given we have had a bunch of cases of board manufacturers swapping parts that aren't always compatible we have an old pattern that we are fixing of rejecting unmatched who am I registers. This driver should be relaxed to just print a message when the value doesn't match - that was the compromise we reached with still pointing out possible compatibility problems, whilst assuming the dts is correct. Even better would be to make it a little more clever so it doesn't bother moaning about part changes if the driver knows the new ID is compatible. Once that's done the comment would reflect how we treat it in the driver (which shouldn't matter to the binding anyway). I'm not entirely sure why this driver has handling to allow for different channel sets, but assume there are more parts to be upstreamed where that flexibility will be useful. Jonathan > > Best regards, > Krzysztof >