From: Wolfram Sang <wsa@the-dreams.de>
To: "Adamski, Krzysztof (Nokia - PL/Wrocław)" <krzysztof.adamski@nokia.com>
Cc: Peter Rosin <peda@axentia.se>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>
Subject: Re: Two separate i2c transfers
Date: Fri, 15 May 2020 11:20:42 +0200 [thread overview]
Message-ID: <20200515092042.GA2077@ninjato> (raw)
In-Reply-To: <820e15e2-9267-1bbb-0809-4e9dc19d566d@nokia.com>
[-- Attachment #1: Type: text/plain, Size: 544 bytes --]
> So this does not really solve my problem - even if we do get the lock
> by calling select(), we will simply release it as soon as our
> i2c_transfer() is finished (and will let the other master take it,
> breaking atomicity of the two operations I need to perform on target
> device) and this is exactly what I need to avoid.
I was assuming that once you have the lock from the arbitrator you can
be sure that the other master is not active and, thus, you maybe don't
need to read the status register at all? But I am probably wrong here.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-05-15 9:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-14 12:41 Two separate i2c transfers Adamski, Krzysztof (Nokia - PL/Wrocław)
2020-05-14 14:50 ` Wolfram Sang
2020-05-15 7:04 ` Adamski, Krzysztof (Nokia - PL/Wrocław)
2020-05-15 7:53 ` Wolfram Sang
2020-05-15 8:51 ` Adamski, Krzysztof (Nokia - PL/Wrocław)
2020-05-15 9:20 ` Wolfram Sang [this message]
2020-05-15 9:24 ` Peter Rosin
2020-05-15 9:31 ` Wolfram Sang
2020-05-15 9:46 ` Adamski, Krzysztof (Nokia - PL/Wrocław)
2020-05-15 8:02 ` Peter Rosin
2020-05-15 8:36 ` Adamski, Krzysztof (Nokia - PL/Wrocław)
2020-05-15 21:19 ` Peter Rosin
2020-05-17 21:32 ` Peter Rosin
2020-05-19 12:59 ` Adamski, Krzysztof (Nokia - PL/Wrocław)
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=20200515092042.GA2077@ninjato \
--to=wsa@the-dreams.de \
--cc=krzysztof.adamski@nokia.com \
--cc=linux-i2c@vger.kernel.org \
--cc=peda@axentia.se \
/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).