All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
	Akinobu Mita <akinobu.mita@gmail.com>,
	"H. Nikolaus Schaller" <hns@goldelico.com>,
	Matt Ranostay <mranostay@gmail.com>,
	Christoph Mair <christoph.mair@gmail.com>,
	Vlad Dogaru <vlad.dogaru@intel.com>,
	Hartmut Knaack <knaack.h@gmx.de>,
	Marek Belisko <marek@goldelico.com>,
	Eric Andersson <eric.andersson@unixphere.com>,
	Neil Brown <neilb@suse.de>
Subject: Re: [PATCH 9/9 v2] iio: pressure: bmp280: read calibration data once
Date: Mon, 27 Jun 2016 19:59:15 +0100	[thread overview]
Message-ID: <2efdabca-f229-89d4-cbc1-4b4e05856296@kernel.org> (raw)
In-Reply-To: <CACRpkdb_fxLSRJq_8ki7u1i9BwxmTS35XD14HDCe9WXfO+L05g@mail.gmail.com>

On 27/06/16 13:11, Linus Walleij wrote:
> On Sun, Jun 26, 2016 at 12:21 PM, Jonathan Cameron <jic23@kernel.org> wrote:
>> On 22/06/16 21:53, Linus Walleij wrote:
>>> The calibration data is described as coming from an E2PROM and that
>>> means it does not change. Just read it once at probe time and store
>>> it in the device state container. Also toss the calibration data
>>> into the entropy pool since it is device unique.
>>>
>>> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
>>
>> One nitpick inline, but it's minor enough I'm just being grumpy
>> about it so don't bother fixing it unless you want to.
>>
>> On the adding entropy bit, any idea who to sanity check that with?
>> It's not something we've done before, so I just want a bit of
>> reassurance ideally;)
> 
> I've done it in a few places whenever I ran into device-unique numbers,
> actually sensors often have device-unique calibration and are thus well
> suited to toss into the entropy pool.
> 
> The data from devices isn't really trusted to increase entropy: it may,
> but it's not relied on by the algorithm, just mixed in, see:
> http://lwn.net/Articles/507115/
Fair enough then.

J
> 
>>>       ret = regmap_bulk_read(data->regmap, BMP180_REG_CALIB_START, buf,
>>>                              sizeof(buf));
>>> -
>> Good but unrelated change.  Should have been in a different patch...
> 
> Dropped unrelated whitespace fix.
> 
> Yours,
> Linus Walleij
> 


  reply	other threads:[~2016-06-27 18:59 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-22 20:53 [PATCH 0/9] Improve BMP280 driver v2 Linus Walleij
2016-06-22 20:53 ` [PATCH 1/9 v2] iio: pressure: bmp280: augment DT bindings Linus Walleij
2016-06-22 20:53   ` Linus Walleij
2016-06-22 20:53 ` [PATCH 2/9 v2] iio: pressure: bmp280: support device tree initialization Linus Walleij
2016-06-23  8:18   ` H. Nikolaus Schaller
2016-06-24 10:26     ` Linus Walleij
2016-06-26  9:52   ` Jonathan Cameron
2016-06-26 10:27     ` H. Nikolaus Schaller
2016-06-26 10:39       ` Jonathan Cameron
2016-06-22 20:53 ` [PATCH 3/9 v2] iio: pressure: bmp280: add reset GPIO line handling Linus Walleij
2016-06-22 20:53 ` [PATCH 4/9 v2] iio: pressure: bmp280: support supply regulators Linus Walleij
2016-06-23 10:02   ` Mark Brown
2016-06-22 20:53 ` [PATCH 5/9 v2] iio: pressure: bmp280: split driver in logical parts Linus Walleij
2016-06-23  8:18   ` H. Nikolaus Schaller
2016-06-24 10:28     ` Linus Walleij
2016-06-26 10:04   ` Jonathan Cameron
2016-06-27 11:29     ` Linus Walleij
2016-06-27 18:58       ` Jonathan Cameron
2016-06-22 20:53 ` [PATCH 6/9 v2] iio: pressure: bmp280: split off an I2C Kconfig entry Linus Walleij
2016-06-22 20:53 ` [PATCH 7/9 v2] iio: pressure: bmp280: add SPI interface driver Linus Walleij
2016-06-26 10:15   ` Jonathan Cameron
2016-06-22 20:53 ` [PATCH 8/9 v2] iio: pressure: bmp280: add support for BMP085 EOC interrupt Linus Walleij
2016-06-26 10:18   ` Jonathan Cameron
2016-06-22 20:53 ` [PATCH 9/9 v2] iio: pressure: bmp280: read calibration data once Linus Walleij
2016-06-26 10:21   ` Jonathan Cameron
2016-06-27 12:11     ` Linus Walleij
2016-06-27 18:59       ` Jonathan Cameron [this message]
2016-06-27  7:42   ` Vlad Dogaru
2016-06-27 18:57     ` Jonathan Cameron
2016-06-28  7:34       ` Linus Walleij
2016-06-28 10:21         ` Vlad Dogaru
2016-06-23  8:17 ` [PATCH 0/9] Improve BMP280 driver v2 H. Nikolaus Schaller

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=2efdabca-f229-89d4-cbc1-4b4e05856296@kernel.org \
    --to=jic23@kernel.org \
    --cc=akinobu.mita@gmail.com \
    --cc=christoph.mair@gmail.com \
    --cc=eric.andersson@unixphere.com \
    --cc=hns@goldelico.com \
    --cc=knaack.h@gmx.de \
    --cc=linus.walleij@linaro.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=marek@goldelico.com \
    --cc=mranostay@gmail.com \
    --cc=neilb@suse.de \
    --cc=vlad.dogaru@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.