From: Hans Verkuil <hverkuil+cisco@kernel.org>
To: linux-i2c@vger.kernel.org
Cc: Jarkko Nikula <jarkko.nikula@linux.intel.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Jan Dabros <jsd@semihalf.com>, Andi Shyti <andi.shyti@kernel.org>
Subject: i2c-designware: not possible to write to different i2c addresses in one transfer?
Date: Wed, 15 Oct 2025 13:25:02 +0200 [thread overview]
Message-ID: <ee6afdd7-3117-43cd-831f-e0ec5ee46f46@kernel.org> (raw)
Hi,
I have this code in a driver (writing display EDID data into an EDID EEPROM):
struct i2c_msg msg[] = {
{
.addr = state->seg_client->addr, // 0x30
.buf = &seg,
.len = 1,
.flags = 0,
},
{
.addr = state->data_client->addr, // 0x50
.buf = data,
.len = len,
.flags = 0,
},
};
err = i2c_transfer(state->dev_client->adapter, msg, ARRAY_SIZE(msg));
This worked fine for the Raspberry Pi 4B using the broadcom i2c driver, but for
the Raspberry Pi 5 using the designware driver it fails with -EINVAL and these
kernel messages:
[ 272.284689] i2c_designware 1f00074000.i2c: i2c_dw_xfer_msg: invalid target address
[ 272.305788] i2c_designware 1f00074000.i2c: controller active
Looking in i2c-designware-master.c it seems it cannot handle consecutive messages for
different addresses.
The i2c device I'm using is this one:
https://www.onsemi.com/pdf/datasheet/cat24c208-d.pdf
Is this a hardware limitation? Or is this a corner case that was never implemented?
Or just simply a bug?
Regards,
Hans
next reply other threads:[~2025-10-15 11:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-15 11:25 Hans Verkuil [this message]
2025-10-15 11:51 ` i2c-designware: not possible to write to different i2c addresses in one transfer? 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
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=ee6afdd7-3117-43cd-831f-e0ec5ee46f46@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 \
/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