From: Vlad Dogaru <vlad.dogaru@intel.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Jonathan Cameron <jic23@kernel.org>,
"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>,
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: Tue, 28 Jun 2016 13:21:11 +0300 [thread overview]
Message-ID: <20160628102111.GB27798@vdogaru> (raw)
In-Reply-To: <CACRpkdb89mMFHQFPs4a00ZcdWmvwHRVhhjc8TBLM25ZjGrzCvg@mail.gmail.com>
On Tue, Jun 28, 2016 at 09:34:34AM +0200, Linus Walleij wrote:
> On Mon, Jun 27, 2016 at 8:57 PM, Jonathan Cameron <jic23@kernel.org> wrote:
> > On 27/06/16 08:42, Vlad Dogaru wrote:
> >> On Wed, Jun 22, 2016 at 10:53:39PM +0200, 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.
> >>
> >> I think my initial thought when writing this was that regmap will take
> >> care of the caching and not hit the i2c bus each time. But I don't have
> >> an issue with this change. Other than that, series looks good to me.
> >
> > Good point. I must be half asleep.
> >
> > Linus, are we missing something? If not, I'd go without this one.
>
> It's true that regmap does cache the contents of the registers,
> cutting the I2C bus traffic bottleneck. But reading it out every time
> still incurs a bulk read of 22 bytes from regmap, meaning 22 iterations
> in regmap where each need to be checked individually for volatileness
> etc in the regmap core, then this happens at every conversion.
>
> Compared to just doing this once and keeping a copy around
> it is wasteful, so still an optimization worth it IMO.
>
> Don't get me wrong, regmap is optimized
> (just check drivers/base/regmap/*) but it can never be as optimized
> as reading just once.
>
> Also Vlad seems to OK it?
Yep, it's not a problem for me. You're right about reading once being
more efficient and.
Thanks,
Vlad
next prev parent reply other threads:[~2016-06-28 10:21 UTC|newest]
Thread overview: 31+ 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 ` [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
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 [this message]
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=20160628102111.GB27798@vdogaru \
--to=vlad.dogaru@intel.com \
--cc=akinobu.mita@gmail.com \
--cc=christoph.mair@gmail.com \
--cc=eric.andersson@unixphere.com \
--cc=hns@goldelico.com \
--cc=jic23@kernel.org \
--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 \
/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