From: Conor Dooley <conor@kernel.org>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>,
egyszeregy@freemail.hu, devicetree@vger.kernel.org,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] i2c-dev: Introduce "linux,i2c-dev-name" property for device tree of I2C controller.
Date: Wed, 29 May 2024 17:10:46 +0100 [thread overview]
Message-ID: <20240529-espresso-founding-54a36bb34e8e@spud> (raw)
In-Reply-To: <mnzj5bqbiuwt4dqnenwctejdnqccqzk2x4tkz2ukqssrmdmsxc@7srnfnfjym26>
[-- Attachment #1: Type: text/plain, Size: 1089 bytes --]
On Wed, May 29, 2024 at 12:28:03PM +0200, Wolfram Sang wrote:
>
> > Optionally, an I2C controller may have a "linux,i2c-dev-name" property.
> > This is a string which is defining a custom suffix name for I2C device
> > in /dev/i2c-<name> format. It helps to improve software portability between
> > various SoCs and reduce complexities of hardware related codes in SWs.
>
> (I thought I already replied to this?)
>
> Highly similar to [1] from 2021. I don't have a super clear opinion
> about this, so I'd need help from the DT maintainers. But the discussion
> from back then stalled.
>
> [1] http://patchwork.ozlabs.org/project/linux-i2c/list/?series=237908
This patch (or one very similar) got sent to the SPI and GPIO subsystems
too. The response was effectively "use udev":
https://lore.kernel.org/all/20240519144920.14804-1-egyszeregy@freemail.hu/
https://lore.kernel.org/all/20240519211346.30323-1-egyszeregy@freemail.hu/
This definitely is in "devicetree properties are not for software-policy"
territory to me, maybe Rob's changed his mind since 2021.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2024-05-29 16:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240519165504.19627-1-egyszeregy@freemail.hu>
2024-05-29 10:28 ` [PATCH] i2c-dev: Introduce "linux,i2c-dev-name" property for device tree of I2C controller Wolfram Sang
2024-05-29 16:10 ` Conor Dooley [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=20240529-espresso-founding-54a36bb34e8e@spud \
--to=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=egyszeregy@freemail.hu \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).