From: Laxman Dewangan <ldewangan@nvidia.com>
To: Jonathan Cameron <jic23@cam.ac.uk>
Cc: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"max@stro.at" <max@stro.at>,
"jbrenner@taosinc.com" <jbrenner@taosinc.com>,
"bfreed@chromium.org" <bfreed@chromium.org>,
"lars@metafoo.de" <lars@metafoo.de>,
"grundler@chromium.org" <grundler@chromium.org>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] staging: iio: light: isl29018: use regmap for register access
Date: Tue, 17 Apr 2012 17:29:05 +0530 [thread overview]
Message-ID: <4F8D5B09.8080309@nvidia.com> (raw)
In-Reply-To: <4F8D5506.6070105@cam.ac.uk>
HI Jonathan,
Thanks for fast review.
On Tuesday 17 April 2012 05:03 PM, Jonathan Cameron wrote:
> On 4/17/2012 9:50 AM, Laxman Dewangan wrote:
>> Using regmap for accessing register through i2c bus. This will
>> remove the code for caching registers, read-modify-write logics.
>> Also it will provide the debugfs feature to dump register
>> through regmap debugfs.
> I'd prefer the intial tab fixup for the kconfig file as a separate
> patch, but other than that
> all looks good.
>
Yes, this make sense. I will create fist patch for fixing this and then
next patch for actual my change.
> This will probably cause issues alongside the series I sent to Greg the
> other day though
> so you may want to sit on it for a day or two and rebase.
I will wait for your change to be in linux-next and then I will create
next patches.
>> Signed-off-by: Laxman Dewangan<ldewangan@nvidia.com>
> Acked-by: Jonathan Cameron<jic23@kernel.org>
>> ---
>> drivers/staging/iio/light/Kconfig | 19 ++--
>> drivers/staging/iio/light/isl29018.c | 176 +++++++++++++++++-----------------
>> 2 files changed, 99 insertions(+), 96 deletions(-)
>>
>> diff --git a/drivers/staging/iio/light/Kconfig b/drivers/staging/iio/light/Kconfig
>> index 53b49f7..fd39f72 100644
>> --- a/drivers/staging/iio/light/Kconfig
>> +++ b/drivers/staging/iio/light/Kconfig
>> @@ -4,15 +4,16 @@
>> menu "Light sensors"
>>
>> config SENSORS_ISL29018
>> - tristate "ISL 29018 light and proximity sensor"
>> - depends on I2C
>> - default n
>> - help
>> - If you say yes here you get support for ambient light sensing and
>> - proximity infrared sensing from Intersil ISL29018.
>> - This driver will provide the measurements of ambient light intensity
>> - in lux, proximity infrared sensing and normal infrared sensing.
>> - Data from sensor is accessible via sysfs.
>> + tristate "ISL 29018 light and proximity sensor"
>> + depends on I2C
>> + select REGMAP_I2C
>> + default n
>> + help
>> + If you say yes here you get support for ambient light sensing and
>> + proximity infrared sensing from Intersil ISL29018.
>> + This driver will provide the measurements of ambient light intensity
>> + in lux, proximity infrared sensing and normal infrared sensing.
>> + Data from sensor is accessible via sysfs.
> Down to here is a valid but unconnected change. Can you break this out
> to a separate patch?
Sure, I will do.
next prev parent reply other threads:[~2012-04-17 11:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-17 8:50 [PATCH] staging: iio: light: isl29018: use regmap for register access Laxman Dewangan
2012-04-17 11:33 ` Jonathan Cameron
2012-04-17 11:59 ` Laxman Dewangan [this message]
2012-04-17 17:56 ` Bryan Freed
2012-04-18 6:19 ` Laxman Dewangan
2012-04-18 8:16 ` Mark Brown
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=4F8D5B09.8080309@nvidia.com \
--to=ldewangan@nvidia.com \
--cc=bfreed@chromium.org \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=grundler@chromium.org \
--cc=jbrenner@taosinc.com \
--cc=jic23@cam.ac.uk \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=max@stro.at \
/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).