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 1/5] misc: Driver for bh1770glc / sfh7770 ALS and proximity sensor
Date: Mon, 11 Oct 2010 09:16:03 +0300 [thread overview]
Message-ID: <1286777763.28027.3.camel@4fid08082> (raw)
In-Reply-To: <4CAF2C1D.9040304@cam.ac.uk>
I have a question about one of your comment
On Fri, 2010-10-08 at 16:35 +0200, ext Jonathan Cameron wrote:
> On 10/08/10 14:42, Samu Onkalo wrote:
> > This is a driver for ROHM BH1770GLC and OSRAM SFH7770 combined
> > ALS and proximity sensor.
> >
> > Interface is sysfs based. The driver uses interrupts to provide new data.
> > The driver supports pm_runtime and regulator frameworks.
> >
> > See Documentation/misc-devices/bhsfh.txt for details
>
> Couple of nitpicks / formatting suggestions inline.
>
> >
> > +/* chip->mutex is kept when this is called */
> > +static int bhsfh_lux_update_thresholds(struct bhsfh_chip *chip,
> > + u16 threshold_hi, u16 threshold_lo)
> > +{
> > + u8 data[4];
>
> u8 data[4] = { threshold_hi,
> threshold_hi >> 8,
> threshold_lo,
> threshold_low >> 8};
> and loose the below will give same result.
What do you mean by that? Threshold_lo / threshold_hi parameters can be
modified before they are stored to HW.
> > + int ret;
> > +
> > + /* sysfs may call this when the chip is powered off */
> > + if (pm_runtime_suspended(&chip->client->dev))
> > + return 0;
> > +
> > + /*
> > + * Compensate threshold values with the correction factors if not
> > + * set to minimum or maximum.
> > + * Min & max values disables interrupts.
> > + */
> > + if (threshold_hi != BHSFH_LUX_RANGE && threshold_hi != 0)
> > + threshold_hi = bhsfh_lux_adjusted_to_raw(chip, threshold_hi);
> > +
> > + if (threshold_lo != BHSFH_LUX_RANGE && threshold_lo != 0)
> > + threshold_lo = bhsfh_lux_adjusted_to_raw(chip, threshold_lo);
Code above can modify values.
> > +
> > + if (chip->lux_thres_hi_onchip == threshold_hi &&
> > + chip->lux_thres_lo_onchip == threshold_lo)
> > + return 0;
> > +
> > + chip->lux_thres_hi_onchip = threshold_hi;
> > + chip->lux_thres_lo_onchip = threshold_lo;
> > +
> > + data[0] = threshold_hi;
> > + data[1] = threshold_hi >> 8;
> > + data[2] = threshold_lo;
> > + data[3] = threshold_lo >> 8;
> > +
> > + ret = i2c_smbus_write_i2c_block_data(chip->client,
> > + BHSFH_ALS_TH_UP_0,
> > + ARRAY_SIZE(data),
> > + data);
> > + return ret;
> > +}
> > +
next prev parent reply other threads:[~2010-10-11 6:16 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 [this message]
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
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=1286777763.28027.3.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