From: Guenter Roeck <guenter.roeck@ericsson.com>
To: "J, KEERTHY" <j-keerthy@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"Krishnamoorthy, Balaji T" <balajitk@ti.com>,
"lm-sensors@lm-sensors.org" <lm-sensors@lm-sensors.org>
Subject: Re: [lm-sensors] [PATCH 1/2] hwmon: twl4030: Driver for twl4030 madc module
Date: Mon, 20 Sep 2010 07:38:34 -0700 [thread overview]
Message-ID: <20100920143834.GA1500@ericsson.com> (raw)
In-Reply-To: <20100920140905.GB1306@ericsson.com>
On Mon, Sep 20, 2010 at 10:09:05AM -0400, Guenter Roeck wrote:
> Hi,
> On Mon, Sep 20, 2010 at 06:34:24AM -0400, J, KEERTHY wrote:
> >
> >
> > > -----Original Message-----
> > > From: Guenter Roeck [mailto:guenter.roeck@ericsson.com]
> > > Sent: Thursday, September 16, 2010 8:48 PM
> > > To: J, KEERTHY
> > > Cc: linux-omap@vger.kernel.org; lm-sensors@lm-sensors.org; Krishnamoorthy,
> > > Balaji T
> > > Subject: Re: [lm-sensors] [PATCH 1/2] hwmon: twl4030: Driver for twl4030
> > > madc module
> > >
> [...]
> > > > +EXPORT_SYMBOL(twl4030_madc_conversion);
> > > > +
> > > If this function is going to be called from external code, it should not
> > > really be defined here. I would suggest to move it to a global location
> > > such as
> > > mfd instead, including all related functions.
> > >
> > > The existence of this function export indicates that another non-hwmon
> > > driver depends on this one, which should not really be the case. Another
> > > reason to have a separate common driver instead, and mfd might just be the
> > > place for it.
> > Few kernel modules need to perform ADC conversion to measure battery
> > voltage, battery temperature, VBUS voltage via twl4030_madc_conversion.
> > the_madc is needed as those drivers will not have this device pointer.
> >
> The point I was trying to make is that this function (as well as the ioctl)
> should not be in this driver in the first place. hwmon is about providing
> hwmon information, not about providing adc readings to another driver.
>
> Or, in other words, hwmon should be a consumer of information from other drivers,
> not a producer of information to other drivers.
>
> There should be a higher level driver (presumably a mfd driver) to provide
> adc readings to all consumers, ie to all callers of twl4030_madc_conversion().
> This driver can provide all data and information needed by more than one driver,
> and would also be the logical place for the ioctl providing raw adc readings
> to the user.
>
I just noticed that there already is a mfd core driver for tw4030. You might want
to consider moving the functionality to read adc values into that driver.
Guenter
next prev parent reply other threads:[~2010-09-20 14:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-16 10:23 [PATCH 1/2] hwmon: twl4030: Driver for twl4030 madc module Keerthy
2010-09-16 15:17 ` [lm-sensors] " Guenter Roeck
2010-09-20 10:34 ` J, KEERTHY
2010-09-20 14:09 ` Guenter Roeck
2010-09-20 14:38 ` Guenter Roeck [this message]
2010-09-27 9:19 ` Keerthy
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=20100920143834.GA1500@ericsson.com \
--to=guenter.roeck@ericsson.com \
--cc=balajitk@ti.com \
--cc=j-keerthy@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=lm-sensors@lm-sensors.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).