From: Jonathan Cameron <jic23@kernel.org>
To: Stefan Tatschner <stefan.tatschner@gmail.com>
Cc: Andreas Klinger <ak@it-klinger.de>,
Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
linux-iio@vger.kernel.org
Subject: Re: [PATCH v2] iio/bmp280-core.c: Read calibration data in probe
Date: Sat, 6 Jan 2018 13:19:11 +0000 [thread overview]
Message-ID: <20180106131911.15115c66@archlinux> (raw)
In-Reply-To: <20180103201345.GA22204@kronos>
On Wed, 3 Jan 2018 21:13:45 +0100
Stefan Tatschner <stefan.tatschner@gmail.com> wrote:
> On Fri, Dec 29, 2017 at 06:48:55PM +0000, Jonathan Cameron wrote:
> > On Tue, 12 Dec 2017 21:35:37 +0100
> > Stefan Tatschner <stefan.tatschner@gmail.com> wrote:
> >
> > > This patch affects BME280 and BMP280. The readout of the calibration
> > > data is moved to the probe function. Each sensor data access triggered
> > > reading the full calibration data before this patch. According to the
> > > datasheet, Section 4.4.2., the calibration data is stored in non-volatile
> > > memory.
> > >
> > > Since the calibration data does not change, and cannot be changed by the
> > > user, we can reduce bus traffic by reading the calibration data once.
> > > Additionally, proper organization of the data types enables removing
> > > some odd casts in the compensation formulas.
> > >
> > > Signed-off-by: Stefan Tatschner <stefan.tatschner@gmail.com>
> > One minor inline. Will fix whilst applying as it's just comment syntax.
>
> Sorry for that. I fired off checkpatch.pl and it didn't complain. I
> remember that, for network code or something, it complains about comment
> style...
>
> > This was headache inducing to check. Glad you got to write it ;)
> >
> > I've also dropped the entropy add that was in here. It should be proposed
> > as a separate patch rather than in here. Particularly as it isn't mentioned
> > in the commit message.
>
> If that makes sense for you, I'll send a further patch.
I think it makes reasonable sense so send a patch adding that on it's own
and we'll consider it then.
>
> > Applied to the togreg branch of iio.git and pushed out as testing for
> > the autobuilders to play with it.
>
> Thanks!
>
> Stefan
prev parent reply other threads:[~2018-01-06 13:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-12 14:34 [PATCH] iio/bmp280-core.c: Read calibration data in probe Stefan Tatschner
2017-12-12 18:06 ` Andreas Klinger
2017-12-12 20:35 ` [PATCH v2] " Stefan Tatschner
2017-12-12 20:38 ` Stefan Tatschner
2017-12-28 11:40 ` Stefan Tatschner
2017-12-28 16:50 ` Andreas Klinger
2017-12-29 18:48 ` Jonathan Cameron
2018-01-03 20:13 ` Stefan Tatschner
2018-01-06 13:19 ` Jonathan Cameron [this message]
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=20180106131911.15115c66@archlinux \
--to=jic23@kernel.org \
--cc=ak@it-klinger.de \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
--cc=stefan.tatschner@gmail.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