From: jic23@cam.ac.uk (Jonathan Cameron)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC] What is the preferred way to share ADC unit between hwmon and input(ts) drivers?
Date: Fri, 06 May 2011 14:43:49 +0100 [thread overview]
Message-ID: <4DC3FB15.5090307@cam.ac.uk> (raw)
In-Reply-To: <20110425110230.GD4768@sirena.org.uk>
On 04/25/11 12:02, Mark Brown wrote:
> On Mon, Apr 25, 2011 at 04:37:38AM +0400, Ilya Yanok wrote:
>
>> So, to add both input and hwmon drivers we need to serialize the
>> register accesses. I was thinking about adding some middle-layer to
>> perform the actual conversion. The question is what is the preferred way
>> to add such a middle layer? Should we use a multi-function device driver
>> for this or just some platform-specific code (as S3C does)? Or maybe
>> there is another way?
>
> IIO would probably be the standard API to use but that's still stuck in
> staging. I'd suggest doing a custom API and then transitioning to IIO
> when that moves out of staging.
IIO is fine for the adc side if it is general purpose (and typically
used as such). If it's typically used for power supply monitoring then
hwmon is the right place.
The touch screen element should definitely be in input though so
you will need a solution to the problem of shared registers.
next prev parent reply other threads:[~2011-05-06 13:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-25 0:37 [RFC] What is the preferred way to share ADC unit between hwmon and input(ts) drivers? Ilya Yanok
2011-04-25 5:25 ` Kurt Van Dijck
2011-05-05 23:41 ` Ilya Yanok
2011-04-25 11:02 ` Mark Brown
2011-05-05 23:43 ` Ilya Yanok
2011-05-06 13:43 ` Jonathan Cameron [this message]
2011-05-06 14:13 ` Ithamar R. Adema
2011-05-06 14:23 ` Mark Brown
2011-05-06 15:15 ` Jonathan Cameron
2011-05-06 15:56 ` Mark Brown
2011-05-06 16:29 ` Jonathan Cameron
2011-05-06 17:20 ` Mark Brown
2011-05-09 13:25 ` Jonathan Cameron
2011-05-09 14:39 ` Mark Brown
2011-05-09 16:35 ` Jonathan Cameron
2011-05-09 19:54 ` Mark Brown
2011-05-10 9:51 ` Jonathan Cameron
2011-05-06 15:21 ` Ithamar R. Adema
2011-05-07 18:11 ` 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=4DC3FB15.5090307@cam.ac.uk \
--to=jic23@cam.ac.uk \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).