From: Wolfram Sang <wsa@kernel.org>
To: Stefan Lengfeld <stefan@lengfeld.xyz>
Cc: "Krzysztof Hałasa" <khalasa@piap.pl>,
linux-media <linux-media@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>,
"Dave Stevenson" <dave.stevenson@raspberrypi.com>,
"Oleksij Rempel" <linux@rempel-privat.de>,
"Pengutronix Kernel Team" <kernel@pengutronix.de>,
"Shawn Guo" <shawnguo@kernel.org>,
"Sascha Hauer" <s.hauer@pengutronix.de>,
"Fabio Estevam" <festevam@gmail.com>,
"NXP Linux Team" <linux-imx@nxp.com>,
linux-i2c@vger.kernel.org
Subject: Re: Sony IMX290/462 image sensors I2C xfer peculiarity
Date: Fri, 13 Oct 2023 09:17:23 +0200 [thread overview]
Message-ID: <ZSjvA3QpY1T9McjN@ninjato> (raw)
In-Reply-To: <20231012220127.GB27838@stcim.de>
[-- Attachment #1: Type: text/plain, Size: 506 bytes --]
> Do you know the I2C repeated start feature [1]? This allows to batch together
> multiple I2C read/writes in a single transfer. And in the best case, this
> transfer is executed in one go without a delay in between. At least in the
> kernel it's guaranteed that no other driver can go in between with another
> transfer.
If the HW does rep_start properly, it is even guaranteed on the bus
because the bus is never seen as free by other participants. Check
"START and STOP" conditions in the I2C specs.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-10-13 7:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m3y1gpw8ri.fsf@t19.piap.pl>
[not found] ` <CAPY8ntASwh3AcRqE+2zF4Df=u+=wJ5K9icAeOrXTMJGDd1+caw@mail.gmail.com>
[not found] ` <m3o7hfx3ob.fsf@t19.piap.pl>
[not found] ` <m37cnuvmhn.fsf@t19.piap.pl>
[not found] ` <m3o7h5tthf.fsf@t19.piap.pl>
2023-10-11 9:50 ` Sony IMX290/462 image sensors I2C xfer peculiarity Krzysztof Hałasa
2023-10-11 10:15 ` Stefan Lengfeld
2023-10-11 11:25 ` Krzysztof Hałasa
2023-10-11 11:59 ` Alexander Stein
2023-10-11 12:18 ` Krzysztof Hałasa
2023-10-12 22:01 ` Stefan Lengfeld
2023-10-13 7:17 ` Wolfram Sang [this message]
2023-10-13 10:39 ` Krzysztof Hałasa
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=ZSjvA3QpY1T9McjN@ninjato \
--to=wsa@kernel.org \
--cc=dave.stevenson@raspberrypi.com \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=khalasa@piap.pl \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux@rempel-privat.de \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=stefan@lengfeld.xyz \
/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