From: Hans Verkuil <hverkuil+cisco@kernel.org>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: linux-i2c@vger.kernel.org,
Jarkko Nikula <jarkko.nikula@linux.intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Jan Dabros <jsd@semihalf.com>, Andi Shyti <andi.shyti@kernel.org>
Subject: Re: i2c-designware: not possible to write to different i2c addresses in one transfer?
Date: Mon, 20 Oct 2025 09:15:05 +0200 [thread overview]
Message-ID: <9da780fe-fa4e-4534-9d97-0c321103e9cb@kernel.org> (raw)
In-Reply-To: <aPUltv8jbxDJ8DcC@shikoro>
On 19/10/2025 19:53, Wolfram Sang wrote:
>
>> May I ask a dumb question? Why do we need such an awkward transaction
>> to begin with?
>
> Because it is allowed per I2C specs? So people will use it.
>
> Interestingly, a patch has just now been proposed which I haven't looked
> at but I wanted to let you guys already know:
>
> [PATCH 2/3] i2c: designware: Enable transfer with different target addresses
> https://lore.kernel.org/r/20251017-i2c-dw-v1-2-7b85b71c7a87@bootlin.com
>
> Maybe you guys can have a look at it?
>
I'll give it a spin today.
Regards,
Hans
next prev parent reply other threads:[~2025-10-20 7:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-15 11:25 i2c-designware: not possible to write to different i2c addresses in one transfer? Hans Verkuil
2025-10-15 11:51 ` Wolfram Sang
2025-10-15 13:40 ` Andy Shevchenko
2025-10-18 18:17 ` Hans Verkuil
2025-10-18 19:21 ` Andy Shevchenko
2025-10-20 9:41 ` Hans Verkuil
2025-10-19 17:53 ` Wolfram Sang
2025-10-20 7:15 ` Hans Verkuil [this message]
2025-10-20 11:59 ` Mika Westerberg
2025-10-20 12:29 ` Hans Verkuil
2025-10-20 12:45 ` Mika Westerberg
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=9da780fe-fa4e-4534-9d97-0c321103e9cb@kernel.org \
--to=hverkuil+cisco@kernel.org \
--cc=andi.shyti@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=jsd@semihalf.com \
--cc=linux-i2c@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=wsa+renesas@sang-engineering.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