All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: platform-driver-x86@vger.kernel.org,
	Guenter Roeck <guenter.roeck@ericsson.com>
Subject: Re: [PATCH RESEND] x86,mrst: Intel Medfield over-current detection patch
Date: Tue, 8 Feb 2011 13:52:28 +0000	[thread overview]
Message-ID: <20110208135228.GA11302@srcf.ucam.org> (raw)
In-Reply-To: <20110208104535.71a4bb12@lxorguk.ukuu.org.uk>

On Tue, Feb 08, 2011 at 10:45:35AM +0000, Alan Cox wrote:
> On Mon, 7 Feb 2011 19:58:43 +0000
> Matthew Garrett <mjg59@srcf.ucam.org> wrote:
> 
> > hwmon includes support for exposing the instantaneous current draw. 
> > hwmon includes support for triggering events if a parameter crosses a 
> > threshold. I still don't see why this isn't an hwmon driver, perhaps 
> > with a small platform driver for the more estoric bits of the setup.
> 
> The hwmon maintainer says its not. Explicitly so. Been there, had that
> discussion a while ago (in fact we had it as well in December if you
> remember and I pointed you at the hwmon list discussion

The hwmon maintainer says that it's not an hwmon driver, not that it 
shouldn't be an hwmon driver.

-- 
Matthew Garrett | mjg59@srcf.ucam.org

  reply	other threads:[~2011-02-08 13:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-25 14:35 [PATCH RESEND] x86,mrst: Intel Medfield over-current detection patch Alan Cox
2011-02-07 19:58 ` Matthew Garrett
2011-02-08 10:45   ` Alan Cox
2011-02-08 13:52     ` Matthew Garrett [this message]
2011-02-08 14:08       ` Alan Cox
2011-02-08 15:49         ` Guenter Roeck
2011-02-08 15:56           ` Matthew Garrett
2011-02-08 16:09             ` Alan Cox
2011-02-08 16:19               ` Matthew Garrett
2011-02-08 16:21             ` Guenter Roeck

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=20110208135228.GA11302@srcf.ucam.org \
    --to=mjg59@srcf.ucam.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=guenter.roeck@ericsson.com \
    --cc=platform-driver-x86@vger.kernel.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 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.