From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Vladimir Kondratiev <Vladimir.Kondratiev@mobileye.com>
Cc: "linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>
Subject: Re: [RFC] Handle targets with different speed by the same I2C master
Date: Thu, 10 Apr 2025 12:15:58 +0200 [thread overview]
Message-ID: <Z_eaXhYqYaB7RSeI@shikoro> (raw)
In-Reply-To: <AS2PR09MB62965C94F5AD1F72FCAD281894B42@AS2PR09MB6296.eurprd09.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 913 bytes --]
> In my case it is bus powered by 1.8V VCC with lots of FM+ targets and this EEPROM:
> https://www.onsemi.com/download/data-sheet/pdf/nv24m01muw-d.pdf
> This EEPROM supports 1MHz at VCC >= 2.5v and 400 KHz at VCC >= 1.8v.
> Our experiments confirm it can stay silent when bus is clocked at 1MHz
Okay, I get the picture, thanks. Still, this is a corner case which is
furthermore based only on experiments, not on specifications. This is
way too vague to have this added to a generic OS. For most people, it
won't work. And this will add some complexity to the code base which I
don't want to maintain. Because the underlying principle is unreliable
itself.
Sorry that the HW design is flawed on your device. If you can still
influence the process, you could get the EERPOM replaced. If you still
want your software solution in your device (I don't recommend it), you
have to carry it out-of-tree, I am afraid.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2025-04-10 10:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-08 10:11 [RFC] Handle targets with different speed by the same I2C master Vladimir Kondratiev
2025-04-08 11:53 ` Wolfram Sang
2025-04-09 13:52 ` Vladimir Kondratiev
2025-04-10 10:15 ` Wolfram Sang [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=Z_eaXhYqYaB7RSeI@shikoro \
--to=wsa+renesas@sang-engineering.com \
--cc=Vladimir.Kondratiev@mobileye.com \
--cc=linux-i2c@vger.kernel.org \
/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