On 10/03/2022 14:39, michael.srba@xxxxxxxxx wrote: > From: Michael Srba <Michael.Srba@xxxxxxxxx> > > ICM-20608-D differs from the other ICM-20608 variants by having > a DMP (Digital Motion Processor) core tacked on. > Despite having a different WHOAMI register, this variant is > completely interchangeable with the other ICM-20608 variants > by simply pretending the DMP core doesn't exist. I wonder now why not using generic invensense,icm20608 compatible as fallback? Why only having one specific compatible? > > Signed-off-by: Michael Srba <Michael.Srba@xxxxxxxxx> > --- > .../devicetree/bindings/iio/imu/invensense,mpu6050.yaml | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/Documentation/devicetree/bindings/iio/imu/invensense,mpu6050.yaml b/Documentation/devicetree/bindings/iio/imu/invensense,mpu6050.yaml > index d69595a524c1..6784cc140323 100644 > --- a/Documentation/devicetree/bindings/iio/imu/invensense,mpu6050.yaml > +++ b/Documentation/devicetree/bindings/iio/imu/invensense,mpu6050.yaml > @@ -17,6 +17,7 @@ properties: > enum: > - invensense,iam20680 > - invensense,icm20608 > + - invensense,icm20608d > - invensense,icm20609 > - invensense,icm20689 > - invensense,icm20602 Best regards, Krzysztof
