From: Onkalo Samu <samu.p.onkalo@nokia.com>
To: ext Jonathan Cameron <jic23@cam.ac.uk>
Cc: "linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"alan@lxorguk.ukuu.org.uk" <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCHv2 2/5] misc: update bhsfh driver to Kconfig and Makefile
Date: Mon, 11 Oct 2010 09:17:40 +0300 [thread overview]
Message-ID: <1286777860.28027.5.camel@4fid08082> (raw)
In-Reply-To: <4CAF29F4.9010709@cam.ac.uk>
On Fri, 2010-10-08 at 16:25 +0200, ext Jonathan Cameron wrote:
> On 10/08/10 14:42, Samu Onkalo wrote:
> > Compilation support for bhsfh driver
> >
> > Signed-off-by: Samu Onkalo <samu.p.onkalo@nokia.com>
> > ---
> > drivers/misc/Kconfig | 10 ++++++++++
> > drivers/misc/Makefile | 1 +
> > 2 files changed, 11 insertions(+), 0 deletions(-)
> >
> > diff --git a/drivers/misc/Kconfig b/drivers/misc/Kconfig
> > index b743312..f2e8065 100644
> > --- a/drivers/misc/Kconfig
> > +++ b/drivers/misc/Kconfig
> > @@ -314,6 +314,16 @@ config SENSORS_BH1780
> > This driver can also be built as a module. If so, the module
> > will be called bh1780gli.
> >
> > +config SENSORS_BHSFH
> > + tristate "BH1770GLC / SFH7770 combined ALS / Proximity sensor";
> > + depends on I2C
> > + ---help---
> > + Say Y here if you want to build a driver for BH1770GLC / SFH7770
> > + combined ambient light and proximity sensor chip
> > +
> > + To compile this driver as a module, choose M here: the
> > + module will be called bhsfh. If unsure, say N here.
> > +
> Really not keen on the naming. The above comment made me think this was
> a single chip integrating both of the parts. Reading the code makes it clear
> that they just share an interface. So please name it after one of them.
> Lots of reasons not to invent combined names like this.
> * non obvious thing to grep for.
> * 3rd part comes along with a different name. Do you change the driver name?
>
> So best bet is always just to pick a supported part and name the driver after
> that. The device table stuff and clear descriptions in kconfig will make
> it obvious what the part supports.
ok, bhsfh.* > bh1770glc.*
What do you think, is it ok to still keep BHSFH in definitions and in
function names?
> > config HMC6352
> > tristate "Honeywell HMC6352 compass"
> > depends on I2C
> > diff --git a/drivers/misc/Makefile b/drivers/misc/Makefile
> > index 42eab95..fd5a4b7 100644
> > --- a/drivers/misc/Makefile
> > +++ b/drivers/misc/Makefile
> > @@ -16,6 +16,7 @@ obj-$(CONFIG_TIFM_CORE) += tifm_core.o
> > obj-$(CONFIG_TIFM_7XX1) += tifm_7xx1.o
> > obj-$(CONFIG_PHANTOM) += phantom.o
> > obj-$(CONFIG_SENSORS_BH1780) += bh1780gli.o
> > +obj-$(CONFIG_SENSORS_BHSFH) += bhsfh.o
> > obj-$(CONFIG_SGI_IOC4) += ioc4.o
> > obj-$(CONFIG_ENCLOSURE_SERVICES) += enclosure.o
> > obj-$(CONFIG_KGDB_TESTS) += kgdbts.o
>
next prev parent reply other threads:[~2010-10-11 6:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-08 13:41 [PATCHv2 0/5] BH1770GLC, SFH7770 and APDS990x als / proximity sensor drivers Samu Onkalo
2010-10-08 13:42 ` [PATCHv2 1/5] misc: Driver for bh1770glc / sfh7770 ALS and proximity sensor Samu Onkalo
2010-10-08 14:35 ` Jonathan Cameron
2010-10-11 6:16 ` Onkalo Samu
2010-10-11 13:35 ` Jonathan Cameron
2010-10-08 13:42 ` [PATCHv2 2/5] misc: update bhsfh driver to Kconfig and Makefile Samu Onkalo
2010-10-08 14:25 ` Jonathan Cameron
2010-10-11 6:17 ` Onkalo Samu [this message]
2010-10-11 13:36 ` Jonathan Cameron
2010-10-09 23:43 ` Randy Dunlap
2010-10-08 13:42 ` [PATCHv2 3/5] misc: Driver for APDS990X ALS and proximity sensors Samu Onkalo
2010-10-08 14:46 ` Jonathan Cameron
2010-10-08 13:42 ` [PATCHv2 4/5] misc: update apds990x driver to Kconfig and Makefile Samu Onkalo
2010-10-09 23:43 ` Randy Dunlap
2010-10-08 13:42 ` [PATCHv2 5/5] Documentation: Short descriptions for bhsfh and apds990x drivers Samu Onkalo
2010-10-08 14:07 ` 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=1286777860.28027.5.camel@4fid08082 \
--to=samu.p.onkalo@nokia.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jic23@cam.ac.uk \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@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