On 13/12/2022 18:15, Han Xu wrote: > Add new compatible string for the NXP FXLS8967AF accelerometer sensor. > > Signed-off-by: Han Xu <han.xu@xxxxxxx> > > --- > 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. That's not what I meant. Compatibility is expressed (check DT spec) by following specific compatible with a more generic one (fallback), so in DTS: compatible = "nxp,fxls8967af", "nxp,fxls8964af"; Your driver changes partially suggested that (and driver changes should be probably skipped in such case), but now I wonder how it is in reality.... Best regards, Krzysztof
