From: Michael Hennerich <michael.hennerich@analog.com>
To: Mark Brown <broonie@kernel.org>
Cc: linus.walleij@linaro.org, wsa@the-dreams.de,
linux-gpio@vger.kernel.org, linux-i2c@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: question about concurrent regmap i2c usage
Date: Wed, 5 Apr 2017 08:31:15 +0200 [thread overview]
Message-ID: <4929e112-9a08-8b9c-f64e-fd2ffaf8b45e@analog.com> (raw)
In-Reply-To: <20170404122654.dfhtvpcnngl3gfco@sirena.org.uk>
On 04.04.2017 14:26, Mark Brown wrote:
> On Tue, Apr 04, 2017 at 10:28:23AM +0200, Michael Hennerich wrote:
>
>> A question came up, regarding whether it's recommended to mix regmap_i2c and
>> plain i2c_smbus or direct adapter transfers.
>
>> In this specific case for the i2c MUX portion we need to avoid double locks,
>> and therefore use un-locked direct adapter transfers.
>
>> The same time we also implement a small gpiochip, where we would like to use
>> regmap to avoid some boilerplate code for the register cache.
>
> That should work fine providing nothing tries to change cached registers
> underneath the regmap. regmap won't be able to tell anything's changed
> otherwise.
Hi Mark,
Thanks for confirmation!
--
Greetings,
Michael
--
Analog Devices GmbH Otl-Aicher Strasse 60-64 80807 München
Sitz der Gesellschaft München, Registergericht München HRB 40368,
Geschäftsführer: Peter Kolberg, Ali Raza Husain, Eileen Wynne
prev parent reply other threads:[~2017-04-05 6:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-04 8:28 question about concurrent regmap i2c usage Michael Hennerich
2017-04-04 12:26 ` Mark Brown
2017-04-05 6:31 ` Michael Hennerich [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=4929e112-9a08-8b9c-f64e-fd2ffaf8b45e@analog.com \
--to=michael.hennerich@analog.com \
--cc=broonie@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wsa@the-dreams.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;
as well as URLs for NNTP newsgroup(s).