mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Onkalo Samu <samu.p.onkalo@nokia.com>
To: ext Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/5] misc: Driver for bh1770glc / sfh7770 ALS and proximity sensor
Date: Tue, 05 Oct 2010 15:37:06 +0300	[thread overview]
Message-ID: <1286282226.21781.60.camel@4fid08082> (raw)
In-Reply-To: <20101005130102.7690c484@lxorguk.ukuu.org.uk>

On Tue, 2010-10-05 at 14:01 +0200, ext Alan Cox wrote:
> On Tue, 05 Oct 2010 14:29:50 +0300

> > > > +	for (i = 0; i < ARRAY_SIZE(prox_rates); i++)
> > > > +		if (prox_rates[i] == rate_threshold) {
> > > > +			chip->prox_rate_threshold = i;
> > > > +			return 0;
> > > > +		}
> > > > +
> > > > +	return -EINVAL;
> > > 
> > > This makes it hard for generic code. Wouldn't picking the best (first at
> > > least as good as required) be a bit more polite to user space ?
> > 
> > Well, perhaps it is better to have hardcoded (or platform specific)
> > rates instead of control interface. I'll change that.
> 
> I don't see a problem with a rate setting where you ask for 'at least X'
> and get the nearest ? Ie swap the == for a >= ?

ok.

> 
> > > This makes no sense because you can't poll() a sysfs file
> > 
> > ok, what should be returned when there is no valid results available?
> 
> I have the same problem with the isl29020 - I think you have to block,
> there isn't any other sane response. A user given -EAGAIN simply doesn't
> know what to do
> 

-EIO then the chip is not running and otherwise block until data is
available.

> 
> > > > +static ssize_t bhsfh_lux_calib_show(struct device *dev,
> > > > +				 struct device_attribute *attr, char *buf)
> > > > +{
> > > > +	struct bhsfh_chip *chip = dev_get_drvdata(dev);
> > > > +	return snprintf(buf, PAGE_SIZE, "%u\n", chip->lux_calib);
> > > > +}
> > > 
> > > This is short chip->mutex locks as you sometimes temporarily change the
> > > value (error path below)
> > > 
> > 
> > ?

of course...

> If I am doing a calib store and a calib show in parallel then the show
> can give a bogus answer because of this bit of code
> 
> > > > +	mutex_lock(&chip->mutex);
> > > > +	old_calib = chip->lux_calib;
> > > > +	chip->lux_calib = value;
> > > > +	new_corr = bhsfh_get_corr_value(chip);
> > > > +	if (new_corr == 0) {
> 
> [Show can occur here]
> 
> > > > +		chip->lux_calib = old_calib;
> > > > +		mutex_unlock(&chip->mutex);
> > > > +		return -EINVAL;
> > > > +	}
> > > > +	chip->lux_corr = new_corr;
> > > > +	mutex_unlock(&chip->mutex);
> > > > +
> > > > +	return len;
> 
> 


  reply	other threads:[~2010-10-05 12:37 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-05  9:42 [PATCH 0/5] BH1770GLC, SFH7770 and APDS990x als / proximity sensor drivers Samu Onkalo
2010-10-05  9:42 ` [PATCH 1/5] misc: Driver for bh1770glc / sfh7770 ALS and proximity sensor Samu Onkalo
2010-10-05 11:21   ` Alan Cox
2010-10-05 11:29     ` Onkalo Samu
2010-10-05 12:01       ` Alan Cox
2010-10-05 12:37         ` Onkalo Samu [this message]
2010-10-05  9:42 ` [PATCH 2/5] misc: update bhsfh driver to Kconfig and Makefile Samu Onkalo
2010-10-05  9:42 ` [PATCH 3/5] misc: Driver for APDS990X ALS and proximity sensors Samu Onkalo
2010-10-05 11:23   ` Alan Cox
2010-10-05 11:48     ` Onkalo Samu
2010-10-05 13:00       ` Alan Cox
2010-10-05 12:39         ` Onkalo Samu
2010-10-05 21:42     ` Mark Brown
2010-10-05  9:42 ` [PATCH 4/5] misc: update apds990x driver to Kconfig and Makefile Samu Onkalo
2010-10-05  9:42 ` [PATCH 5/5] Documentation: Short descriptions for bhsfh and apds990x drivers Samu Onkalo
2010-10-05 11:53   ` Jonathan Cameron
2010-10-05 12:22     ` Onkalo Samu
2010-10-05 14:13       ` 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=1286282226.21781.60.camel@4fid08082 \
    --to=samu.p.onkalo@nokia.com \
    --cc=alan@lxorguk.ukuu.org.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

Powered by JetHome