All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Jonathan Cameron <jic23@cam.ac.uk>,
	mingo@elte.hu, linux-kernel@vger.kernel.org,
	Jonathan Cameron <jic23@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH RESEND] x86, intel_mid: ADC management
Date: Thu, 12 Apr 2012 18:53:13 +0100	[thread overview]
Message-ID: <20120412175313.GB18049@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20120411133035.25fa00b0@pyramind.ukuu.org.uk>

[-- Attachment #1: Type: text/plain, Size: 695 bytes --]

On Wed, Apr 11, 2012 at 01:30:35PM +0100, Alan Cox wrote:
> > needs to be abstracted as well.  Consumers might not care that the gain 
> > just doubled because someone else requested it, but I suspect many of them will.

> At the bottom layer I'd expect a second consumer of the same data to get
> -EBUSY, but you are then going to tell me there are ADCs with one gain
> control for several channels no doubt 8)

There's also some sensible use cases like the multiple system monitoring
subsystems we've got wanting to monitor the same power rail where it's
useful to have multiple consumers sharing the ADC, though with those
ones changing the gain probably doesn't make much sense.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  parent reply	other threads:[~2012-04-12 17:53 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-10 13:20 [PATCH RESEND] x86, intel_mid: ADC management Alan Cox
2012-04-10 13:12 ` Mark Brown
2012-04-10 13:25   ` Alan Cox
2012-04-10 13:33     ` Mark Brown
2012-04-10 13:42       ` Alan Cox
2012-04-10 14:07         ` Mark Brown
2012-04-10 14:15           ` Alan Cox
2012-04-10 15:19             ` Mark Brown
2012-04-10 16:56               ` Alan Cox
2012-04-10 17:58                 ` Mark Brown
2012-04-10 19:39                   ` Jonathan Cameron
2012-04-10 22:37                     ` Mark Brown
2012-04-11  6:19                       ` Jonathan Cameron
2012-04-11  6:19                         ` Jonathan Cameron
2012-04-11  7:44                         ` Jonathan Cameron
2012-04-11 15:38                         ` Greg Kroah-Hartman
2012-04-11 16:30                           ` Jonathan Cameron
2012-04-11 23:46                             ` Greg Kroah-Hartman
2012-04-12  6:25                               ` Jonathan Cameron
2012-04-11 10:24                   ` Alan Cox
2012-04-11 10:38                     ` Mark Brown
2012-04-11 10:48                       ` Jonathan Cameron
2012-04-11 11:13                         ` Alan Cox
2012-04-11 11:19                           ` Jonathan Cameron
2012-04-11 12:30                             ` Alan Cox
2012-04-11 12:55                               ` Jonathan Cameron
2012-04-12 17:53                               ` Mark Brown [this message]
2012-04-12 18:04                             ` Mark Brown
2012-04-11 11:38                     ` Jonathan Cameron

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=20120412175313.GB18049@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=gregkh@linuxfoundation.org \
    --cc=jic23@cam.ac.uk \
    --cc=jic23@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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.