From: Jonathan Cameron <jic23@cam.ac.uk>
To: Jonathan Cameron <jic23@cam.ac.uk>,
List Linux Kernel <linux-kernel@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@suse.de>,
linux-omap@vger.kernel.org
Cc: Zhang Rui <rui.zhang@intel.com>
Subject: Re: [PATCH 1/2] staging: iio: tsl2563 ambient light sensor driver
Date: Mon, 09 Nov 2009 18:08:59 +0000 [thread overview]
Message-ID: <4AF85ABB.7060406@cam.ac.uk> (raw)
In-Reply-To: <20091109142430.GZ1773@smtp.gmail.com>
Amit Kucheria wrote:
> On 09 Nov 09, Jonathan Cameron wrote:
>> Hi Amit,
>>
>> Normally I'd welcome this in IIO, except that all ambient light sensors are in the
>> process of moving to the new ALS subsystem. There are still some issues to resolve
>> in that subsystem (mainly to do with naming conventions) but hopefully we will
>> get them sorted out shortly.
>
> Groan! :)
You have my sympathies on this! Typical that the first other developer to put
forward a patch for IIO picks the one type of device we are moving out.
If you do have any comments on IIO as a result of using it please send them
on.
> Who will be the subsystem maintainer and is there already a public git
> tree?
No git tree as far as I know. Maintainer is Zhang Rui (Cc'd)
Zhang, what are your plans wrt to that? I guess I can put one up with the current
patches if it is helpful? We really need to sort out the naming issue as the one
thing that people have come out against.
After that I'm guessing ping Andrew Morton to see if he is willing to handle the push
to Linus? Or does Zhang want to try doing one directly?
>> I'll take a close look at this sometime over the next few days though. On a quick
>> glance at the data sheet, it looks very similar to the tsl2561. Perhaps we can merge
>> the drivers? Yours is certainly more complete than the tsl2561 version in IIO so it
>> would make sense to lift the functional elements in to the code I have for an ALS
>> driver. I hadn't posted that previously as I hadn't quite worked out how to handle
>> the various gain related settings. What you have done seems to make sense (from a very
>> quick look.)
>
> I've got no problem merging the tsl2563 with 2561. I don't have any 2561
> hardware to check a merged driver though.
On a reasonably thorough review of data sheets I think the only difference is the
input voltage range and a few timing parameters. These two chips even use the same
addresses. I'll actually test your driver against the tsl2561 sometime later in the
week to be sure. So the merge looks like adding a few more lines to the i2c_device_id
table. As a quick comment you would ideally have the tsl2563 and tsl2562 in there
already.
>
>
> Do you think the ALS framework will be finalised before the 2.6.33 merge
> window (in a few weeks)? If not, I wonder if Greg would take this driver to
> staging to begin with and I'll modify it to use the ALS subsystem when it
> settles down.
I'm certainly happy with that as an option if Greg is willing. In fact,
adding this with tsl2560-> tsl2563 support and removing the current tsl2561 driver would
be great (post any reviews over the next couple of days).
Thanks,
Jonathan
next prev parent reply other threads:[~2009-11-09 18:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-09 13:14 [PATCH 1/2] staging: iio: tsl2563 ambient light sensor driver Amit Kucheria
2009-11-09 13:14 ` [PATCH 2/2] omap: rx51: Enable RX-51 ambient light sensor Amit Kucheria
2009-11-09 13:57 ` [PATCH 1/2] staging: iio: tsl2563 ambient light sensor driver Jonathan Cameron
2009-11-09 14:03 ` Jonathan Cameron
2009-11-09 14:24 ` Amit Kucheria
2009-11-09 18:08 ` Jonathan Cameron [this message]
2009-11-10 8:58 ` Zhang Rui
2009-11-10 9:52 ` Amit Kucheria
2009-11-09 19:03 ` 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=4AF85ABB.7060406@cam.ac.uk \
--to=jic23@cam.ac.uk \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=rui.zhang@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