From: tip-bot for Linus Walleij <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: jic23@kernel.org, hpa@zytor.com, peterz@infradead.org,
linus.walleij@linaro.org, dmitry.torokhov@gmail.com,
mingo@kernel.org, linux-kernel@vger.kernel.org,
tglx@linutronix.de, torvalds@linux-foundation.org,
andriy.shevchenko@linux.intel.com
Subject: [tip:x86/urgent] x86/platform/intel-mid: Switch MPU3050 driver to IIO
Date: Mon, 19 Dec 2016 23:59:06 -0800 [thread overview]
Message-ID: <tip-a7dcc6e076fb1e4ce1a56c7f3a49a83b41b01f44@git.kernel.org> (raw)
In-Reply-To: <1481722794-4348-1-git-send-email-linus.walleij@linaro.org>
Commit-ID: a7dcc6e076fb1e4ce1a56c7f3a49a83b41b01f44
Gitweb: http://git.kernel.org/tip/a7dcc6e076fb1e4ce1a56c7f3a49a83b41b01f44
Author: Linus Walleij <linus.walleij@linaro.org>
AuthorDate: Wed, 14 Dec 2016 14:39:54 +0100
Committer: Ingo Molnar <mingo@kernel.org>
CommitDate: Tue, 20 Dec 2016 08:52:40 +0100
x86/platform/intel-mid: Switch MPU3050 driver to IIO
The Intel Mid goes in and creates a I2C device for the
MPU3050 if the input driver for MPU-3050 is activated.
As of commit:
3904b28efb2c ("iio: gyro: Add driver for the MPU-3050 gyroscope")
.. there is a proper and fully featured IIO driver for this
device, so deprecate the use of the incomplete input driver
by augmenting the device population code to react to the
presence of the IIO driver's Kconfig symbol instead.
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
Acked-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Jonathan Cameron <jic23@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Link: http://lkml.kernel.org/r/1481722794-4348-1-git-send-email-linus.walleij@linaro.org
Signed-off-by: Ingo Molnar <mingo@kernel.org>
---
arch/x86/platform/intel-mid/device_libs/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/platform/intel-mid/device_libs/Makefile b/arch/x86/platform/intel-mid/device_libs/Makefile
index dd6cfa4..61b5ed2 100644
--- a/arch/x86/platform/intel-mid/device_libs/Makefile
+++ b/arch/x86/platform/intel-mid/device_libs/Makefile
@@ -19,7 +19,7 @@ obj-$(subst m,y,$(CONFIG_SPI_SPIDEV)) += platform_spidev.o
# I2C Devices
obj-$(subst m,y,$(CONFIG_SENSORS_EMC1403)) += platform_emc1403.o
obj-$(subst m,y,$(CONFIG_SENSORS_LIS3LV02D)) += platform_lis331.o
-obj-$(subst m,y,$(CONFIG_INPUT_MPU3050)) += platform_mpu3050.o
+obj-$(subst m,y,$(CONFIG_MPU3050_I2C)) += platform_mpu3050.o
obj-$(subst m,y,$(CONFIG_INPUT_BMA150)) += platform_bma023.o
obj-$(subst m,y,$(CONFIG_DRM_MEDFIELD)) += platform_tc35876x.o
# I2C GPIO Expanders
next prev parent reply other threads:[~2016-12-20 8:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-14 13:39 [PATCH] x86/platform/intel-mid: switch " Linus Walleij
2016-12-14 15:12 ` Andy Shevchenko
2016-12-20 7:59 ` tip-bot for Linus Walleij [this message]
2016-12-20 9:35 ` [tip:x86/urgent] x86/platform/intel-mid: Switch " tip-bot for Linus Walleij
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=tip-a7dcc6e076fb1e4ce1a56c7f3a49a83b41b01f44@git.kernel.org \
--to=tipbot@zytor.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=dmitry.torokhov@gmail.com \
--cc=hpa@zytor.com \
--cc=jic23@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome