On ma, 2016-01-25 at 23:24 +0100, Richard Weinberger wrote:
> --- a/drivers/iio/imu/inv_mpu6050/Kconfig
> +++ b/drivers/iio/imu/inv_mpu6050/Kconfig
> config INV_MPU6050_IIO
> tristate "Invensense MPU6050 devices"
> depends on I2C && SYSFS
> + depends on I2C_MUX
Nit: if I parsed the v4.5-rc1 tree correctly I2C_MUX depends I2C. So
just
depends on I2C_MUX && SYSFS
should also do the trick. Is it clearer to mention both I2C and I2C_MUX
explicitly?
(Likewise for 17/22.)
> select IIO_BUFFER
> select IIO_TRIGGERED_BUFFER
> - select I2C_MUX
> help
> This driver supports the Invensense MPU6050 devices.
(evolution 3.16.5 hates replying to plain text messages, so I've lost a
line of context after fiddling with your message here.)
Paul Bolle
------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
