From: Jean Delvare <khali@linux-fr.org>
To: felipe.balbi@nokia.com
Cc: linux-omap@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Jonathan Cameron <Jonathan.Cameron@gmail.com>
Subject: Re: [PATCH 6/8] tsl2563: move tsl2563 to drivers/hwmon
Date: Tue, 14 Oct 2008 16:14:26 +0200 [thread overview]
Message-ID: <20081014161426.552115e5@hyperion.delvare> (raw)
In-Reply-To: <20081014135230.GA28019@gandalf.research.nokia.com>
On Tue, 14 Oct 2008 16:52:30 +0300, Felipe Balbi wrote:
> On Tue, Oct 14, 2008 at 03:38:24PM +0200, ext Jean Delvare wrote:
> > Hi Felipe,
> >
> > On Tue, 14 Oct 2008 16:01:38 +0300, Felipe Balbi wrote:
> > > Moving the driver to where it should sit. No functional
> > > changes.
> > >
> > > Cc: Jean Delvare <khali@linux-fr.org>
> > > Signed-off-by: Felipe Balbi <felipe.balbi@nokia.com>
> > > ---
> > > drivers/hwmon/Kconfig | 10 ++++++++++
> > > drivers/hwmon/Makefile | 1 +
> > > drivers/{i2c/chips => hwmon}/tsl2563.c | 2 +-
> > > drivers/i2c/chips/Kconfig | 10 ----------
> > > drivers/i2c/chips/Makefile | 1 -
> > > 5 files changed, 12 insertions(+), 12 deletions(-)
> > > rename drivers/{i2c/chips => hwmon}/tsl2563.c (99%)
> > >
> > > diff --git a/drivers/hwmon/Kconfig b/drivers/hwmon/Kconfig
> > > index 390c6fa..dabc148 100644
> > > --- a/drivers/hwmon/Kconfig
> > > +++ b/drivers/hwmon/Kconfig
> > > @@ -670,6 +670,16 @@ config SENSORS_THMC50
> > > This driver can also be built as a module. If so, the module
> > > will be called thmc50.
> > >
> > > +config SENSORS_TSL2563
> > > + tristate "Taos TSL2563 ambient light sensor"
> > > + depends on I2C && HWMON
> > > + help
> > > + If you say yes here you get support for the Taos TSL2563
> > > + ambient light sensor.
> > > +
> > > + This driver can also be built as a module. If so, the module
> > > + will be called tsl2563.
> > > +
> > > config SENSORS_VIA686A
> > > tristate "VIA686A"
> > > depends on PCI
> >
> > Nack. Light sensors have nothing to do with hardware monitoring.
> >
> > The only light sensor driver in the kernel tree at the moment
> > is drivers/i2c/chips/tsl2550.c. But I'm not very happy with this
> > either, as my ultimate goal is to delete the drivers/i2c/chips
> > directory completely. So we should find a new home for light sensors.
>
> and that's why I'm moving nokia drivers out of drivers/i2c/chips
> directory.
>
> > Maybe they should go into the new "industrial I/O" subsystem. Or if
> > not, their own drivers/sensors/light directory.
>
> Well, could be. We might need someone else, like Andrew, to answer that
> question.
I'd rather ask the question to Jonathan Cameron (Cc'd.)
> Andrew, do you have any comments if we should create a directory for
> light sensors ? In that case, looks like we're gonna need some
> abstraction layer, right ?
I've implied a sysfs interface with my tsl2550 driver, essentially
derived from the hwmon sysfs interface. I hope you followed it in your
driver if possible. When these drivers have a new home, we can document
the sysfs interface. Or, if these drivers end up in the industrial I/O
subsystem, maybe a completely different interface will be used instead
(but then it's in Jonathan's hands.)
--
Jean Delvare
next prev parent reply other threads:[~2008-10-14 14:14 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-14 13:01 [PATCH 0/8] updtes to few nokia drivers Felipe Balbi
2008-10-14 13:01 ` [PATCH 1/8] i2c: lp5521: remove dead code Felipe Balbi
2008-10-14 13:01 ` [PATCH 2/8] i2c: lp5521: cosmetic fixes Felipe Balbi
2008-10-14 13:01 ` [PATCH 3/8] lp5521: move to drivers/leds Felipe Balbi
2008-10-14 13:01 ` [PATCH 4/8] leds: lp5521: simplify mode setting Felipe Balbi
2008-10-14 13:01 ` [PATCH 5/8] leds: lp5521: register separate leds Felipe Balbi
2008-10-14 13:01 ` [PATCH 6/8] tsl2563: move tsl2563 to drivers/hwmon Felipe Balbi
2008-10-14 13:01 ` [PATCH 7/8] input: lm8323: get rid of global pdata pointer Felipe Balbi
2008-10-14 13:01 ` [PATCH 8/8] input: tsc2005: move to gpiolib Felipe Balbi
2008-10-14 13:38 ` [PATCH 6/8] tsl2563: move tsl2563 to drivers/hwmon Jean Delvare
2008-10-14 13:52 ` Felipe Balbi
2008-10-14 14:14 ` Jean Delvare [this message]
2008-10-14 14:38 ` Felipe Balbi
2008-10-14 16:00 ` David Brownell
2008-10-14 21:20 ` Felipe Balbi
2008-10-14 21:44 ` David Brownell
2008-10-14 21:50 ` Felipe Balbi
2008-10-15 8:26 ` Jean Delvare
2008-10-14 15:55 ` [PATCH 5/8] leds: lp5521: register separate leds David Brownell
2008-10-14 17:09 ` Felipe Balbi
2008-10-14 15:53 ` [PATCH 3/8] lp5521: move to drivers/leds David Brownell
2008-10-14 17:11 ` Felipe Balbi
2008-10-14 17:19 ` David Brownell
2008-10-14 17:32 ` Felipe Balbi
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=20081014161426.552115e5@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=Jonathan.Cameron@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=felipe.balbi@nokia.com \
--cc=linux-omap@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox