From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Peter Meerwald <pmeerw@pmeerw.net>,
Bastien Nocera <hadess@hadess.net>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Linux Input <linux-input@vger.kernel.org>,
Joseph Lai <joseph_lai@wistron.com>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Subject: Re: [PATCH] input: misc: delete MPU3050 driver
Date: Wed, 1 Feb 2017 15:48:54 -0800 [thread overview]
Message-ID: <20170201234854.GH40720@dtor-ws> (raw)
In-Reply-To: <CACRpkda_VP=PKDxHyq_v7q2k3Q4XhGV34bgD1ez5Rdg2O1f5cQ@mail.gmail.com>
On Tue, Jan 31, 2017 at 10:30:01AM +0100, Linus Walleij wrote:
> On Tue, Jan 31, 2017 at 9:14 AM, Dmitry Torokhov
> <dmitry.torokhov@gmail.com> wrote:
>
> > OK, since nobody yelled that they need it I applied the patch.
>
> Thanks!
>
> We need to think about the future of these misc input drivers:
>
> misc/bma150.c
> misc/cma3000*
> misc/mma8450.c
>
> The first has a partial (or maybe complete) support in
> iio/accel/bma180.c and the last seems to be possible to be
> supported by iio/accel/mma8452.c with some slight adjustments.
>
> It's not only because I have OCD and want to sort every driver
> in the right pigeon-hole... the iio-sensor-proxy GNOME daemon
> bugzilla/github has been spamming me with complaints about
> problems caused by the accelerometer-as-input drivers.
> It would be nice to at least compartmentalize the problems
> into one subsystem. Terminating misc/bma150.c has been
> mentioned.
I we have replacements in drivers/iio I'd be happy to cut these out of
drivers/input.
Thanks.
--
Dmitry
next prev parent reply other threads:[~2017-02-01 23:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-10 8:31 [PATCH] input: misc: delete MPU3050 driver Linus Walleij
2017-01-10 10:43 ` Heikki Krogerus
2017-01-31 8:14 ` Dmitry Torokhov
2017-01-31 9:30 ` Linus Walleij
2017-02-01 23:48 ` Dmitry Torokhov [this message]
2017-01-23 13:40 ` 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=20170201234854.GH40720@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=hadess@hadess.net \
--cc=heikki.krogerus@linux.intel.com \
--cc=joseph_lai@wistron.com \
--cc=linus.walleij@linaro.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
/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;
as well as URLs for NNTP newsgroup(s).