On Mon, 5 Aug 2019 12:26:50 +0000 Jean-Baptiste Maneyrol <JManeyrol@xxxxxxxxxxxxxx> wrote: > Since every chip has a different whoami, we are not supporting all > existing variant of all chips. Add an explicit supported chips > list in Kconfig description. > > Signed-off-by: Jean-Baptiste Maneyrol <jmaneyrol@xxxxxxxxxxxxxx> Applied, Thanks, Jonathan > --- > drivers/iio/imu/inv_mpu6050/Kconfig | 10 ++++++---- > 1 file changed, 6 insertions(+), 4 deletions(-) > > diff --git a/drivers/iio/imu/inv_mpu6050/Kconfig b/drivers/iio/imu/inv_mpu6050/Kconfig > index 395f3bd7de0a..e4c4c12236a7 100644 > --- a/drivers/iio/imu/inv_mpu6050/Kconfig > +++ b/drivers/iio/imu/inv_mpu6050/Kconfig > @@ -14,8 +14,9 @@ config INV_MPU6050_I2C > select INV_MPU6050_IIO > select REGMAP_I2C > help > - This driver supports the Invensense MPU6050/6500/9150 and > - ICM20608/20602 motion tracking devices over I2C. > + This driver supports the Invensense MPU6000/6050/6500/6515, > + MPU9150/9250/9255 and ICM20608/20602 motion tracking devices > + over I2C. > This driver can be built as a module. The module will be called > inv-mpu6050-i2c. > > @@ -25,7 +26,8 @@ config INV_MPU6050_SPI > select INV_MPU6050_IIO > select REGMAP_SPI > help > - This driver supports the Invensense MPU6050/6500/9150 and > - ICM20608/20602 motion tracking devices over SPI. > + This driver supports the Invensense MPU6000/6050/6500/6515, > + MPU9150/9250/9255 and ICM20608/20602 motion tracking devices > + over SPI. > This driver can be built as a module. The module will be called > inv-mpu6050-spi.
