From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: Wolfram Sang <wsa@kernel.org>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
Krzysztof Piotr Oledzki <ole@ans.pl>
Subject: Re: [PATCH] i2c: core: Lock address during client device instantiation
Date: Fri, 16 Aug 2024 11:23:59 +0200 [thread overview]
Message-ID: <Zr8ar4SCtYAiq-U0@shikoro> (raw)
In-Reply-To: <dfbe5afa-daf6-4366-8f53-c8f7434b0748@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 849 bytes --]
Hi Heiner,
> I didn't find a single dts(i) with a 10bit i2c device. Because you said
In all those years, I didn't even find a device supporting 10 bit
addresses. And I really looked especially for them. Some controllers
offer 10-bit support in target mode, but that's all I found.
Also, there is only one user of I2C_CLIENT_TEN, and this is only a hack
to allow instantiating the device at address 0x00. No actual 10-bit
usage involved. I will remove this as a first step, because this hack is
terrible anyhow.
> that you're tempted to remove 10 bit support: Could the device tree part
> be a starting point?
I don't really have a roadmap how to deprecate 10 bit support. Because
it is exported to userspace, the first question is if we can deprecate
it, after all. But not much bandwidth even for that, currently.
Happy hacking,
Wolfram
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-08-16 9:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-13 21:39 [PATCH] i2c: core: Lock address during client device instantiation Heiner Kallweit
2024-08-14 11:14 ` Wolfram Sang
2024-08-14 20:07 ` Heiner Kallweit
2024-08-14 20:25 ` Wolfram Sang
2024-08-16 6:17 ` Heiner Kallweit
2024-08-16 9:23 ` Wolfram Sang [this message]
2024-08-16 11:33 ` Heiner Kallweit
2024-08-16 14:49 ` Wolfram Sang
2024-08-15 11:29 ` kernel test robot
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=Zr8ar4SCtYAiq-U0@shikoro \
--to=wsa+renesas@sang-engineering.com \
--cc=hkallweit1@gmail.com \
--cc=linux-i2c@vger.kernel.org \
--cc=ole@ans.pl \
--cc=wsa@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