From: Guenter Roeck <guenter.roeck@ericsson.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Randy Dunlap <rdunlap@xenotime.net>,
Jean Delvare <khali@linux-fr.org>,
Andrew Morton <akpm@linux-foundation.org>,
"Ira W. Snyder" <iws@ovro.caltech.edu>,
Hans de Goede <hdegoede@redhat.com>,
Samuel Ortiz <sameo@linux.intel.com>,
Jonathan Cameron <kernel@jic23.retrosnub.co.uk>,
"lm-sensors@lm-sensors.org" <lm-sensors@lm-sensors.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>
Subject: Re: [PATCH v3 1/4] hwmon: Driver for SMM665 Six-Channel Active DC Output Controller/Monitor
Date: Sun, 27 Jun 2010 08:10:47 -0700 [thread overview]
Message-ID: <20100627151047.GA5731@ericsson.com> (raw)
In-Reply-To: <20100627102058.GB2845@sirena.org.uk>
On Sun, Jun 27, 2010 at 06:20:59AM -0400, Mark Brown wrote:
> On Thu, Jun 24, 2010 at 03:00:58PM -0700, Guenter Roeck wrote:
> > This driver adds support for the monitoring features of the Summit
> > Microelectronics SMM665 Six-Channel Active DC Output Controller/Monitor.
>
> A bit late to the game here but this looks like the chip has some
> regulator control functionality as well as monitoring functionality (and
> the product page on the Summit web site suggests so also). This means
> that when fully supported in software the driver would cross multiple
> subsystems so it might make sense to start off with a MFD rather than
> direct I2C control?
>
> If the non-monitoring functionality can't be controlled from software
> this isn't an issue.
I thought about that when I started working on the driver, but concluded that
it does not really make sense.
The chip is commonly used to control all supply voltages on a board.
Changing those voltages is not a good idea. For that reason, the chip can be
set into read-only mode, where changing the voltages is no longer possible
after initial programming.
While it is theoretically possible that someone might use the device to control
not only fixed but also dynamic voltages, I think that is highly unlikely, given
the risk involved in blowing up the board. Thus, moving the driver to mfd would
effectively serve no real purpose other than to cause confusion and add unnecessary
complexity.
Guenter
next prev parent reply other threads:[~2010-06-27 15:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-24 22:00 [PATCH v3 0/4] " Guenter Roeck
2010-06-24 22:00 ` [PATCH v3 1/4] " Guenter Roeck
2010-06-24 23:05 ` Guenter Roeck
2010-06-27 10:20 ` Mark Brown
2010-06-27 15:10 ` Guenter Roeck [this message]
2010-06-27 19:54 ` Mark Brown
2010-06-27 22:07 ` Guenter Roeck
2010-06-24 22:00 ` [PATCH v3 2/4] hwmon: SMM665 driver documentation Guenter Roeck
2010-06-24 22:01 ` [PATCH v3 3/4] hwmon: Update sysfs-interface to include new attributes Guenter Roeck
2010-06-24 23:32 ` Ira W. Snyder
2010-06-24 23:40 ` Guenter Roeck
2010-06-25 8:05 ` Jean Delvare
2010-06-24 22:01 ` [PATCH v3 4/4] hwmon: Update MAINTAINERS for smm665 driver Guenter Roeck
2010-06-25 8:09 ` Jean Delvare
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=20100627151047.GA5731@ericsson.com \
--to=guenter.roeck@ericsson.com \
--cc=akpm@linux-foundation.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=hdegoede@redhat.com \
--cc=iws@ovro.caltech.edu \
--cc=kernel@jic23.retrosnub.co.uk \
--cc=khali@linux-fr.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lm-sensors@lm-sensors.org \
--cc=rdunlap@xenotime.net \
--cc=sameo@linux.intel.com \
/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
Powered by JetHome