All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Jonathan Cameron <jic23@cam.ac.uk>
Cc: mems applications <mems.applications@st.com>,
	rdunlap@xenotime.net, carmine.iascone@st.com,
	matteo.dameno@st.com, rubini@cvml.unipv.it,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Add STMicroelectronics LPS001WP pressure sensor device driver into misc
Date: Mon, 14 Mar 2011 20:46:25 +0100	[thread overview]
Message-ID: <201103142046.25393.arnd@arndb.de> (raw)
In-Reply-To: <4D7E6A38.7010801@cam.ac.uk>

On Monday 14 March 2011 20:19:20 Jonathan Cameron wrote:
> The big issue raised last time around is that this is not a conventional human
> input device.  Hence Dmitry isn't going to take it into input.  That doesn't
> just mean that you have to move it's physical location; it also means you have
> to not use the input interfaces at all.

How about making this a hwmon driver instead?
There are already a number of temperature sensor drivers in
driver/hwmon/, I think it would fit in well there.

This would mean moving it to the other directory,
registering it to the common hwmon api (hwmon_device_register)
and rewriting the user API to blend in with the other
hwmon drivers.

	Arnd

  reply	other threads:[~2011-03-14 19:46 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-14 18:55 [PATCH] Add STMicroelectronics LPS001WP pressure sensor device driver into misc mems applications
2011-03-14 19:19 ` Jonathan Cameron
2011-03-14 19:46   ` Arnd Bergmann [this message]
2011-03-14 20:14     ` Jonathan Cameron
2011-03-14 20:18       ` Jean Delvare
2011-03-14 20:27         ` Guenter Roeck
2011-03-14 20:36         ` Arnd Bergmann
2011-03-14 21:42           ` Jean Delvare
2011-03-14 22:48             ` Guenter Roeck
2011-03-15  9:24               ` Arnd Bergmann
2011-03-15 11:30                 ` Jonathan Cameron
2011-03-15 13:58                   ` Arnd Bergmann
2011-03-14 23:23             ` Jonathan Cameron
2011-03-15  9:38               ` Arnd Bergmann
2011-03-15 11:11                 ` Jonathan Cameron
2011-03-15 11:11                   ` Jonathan Cameron
2011-03-15 12:51                   ` Mark Brown
2011-03-15 12:51                     ` Mark Brown
2011-03-15 13:31                     ` Arnd Bergmann
2011-03-15 13:31                       ` Arnd Bergmann
2011-03-15 14:35                       ` Jonathan Cameron
2011-03-15 14:35                         ` Jonathan Cameron
2011-03-15 14:38                     ` Jonathan Cameron
2011-03-15 14:38                       ` Jonathan Cameron
2011-03-15 13:29                   ` Arnd Bergmann
2011-03-15 13:29                     ` Arnd Bergmann
2011-03-15 14:47                     ` Jonathan Cameron
2011-03-15 14:47                       ` Jonathan Cameron
2011-03-15 16:50                       ` Arnd Bergmann
2011-03-15 16:50                         ` Arnd Bergmann

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=201103142046.25393.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=carmine.iascone@st.com \
    --cc=jic23@cam.ac.uk \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matteo.dameno@st.com \
    --cc=mems.applications@st.com \
    --cc=rdunlap@xenotime.net \
    --cc=rubini@cvml.unipv.it \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.