From: Alexander Sverdlin <alexander.sverdlin@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: Javier Martinez Canillas <javierm@redhat.com>,
Wolfram Sang <wsa@the-dreams.de>,
Herve Codina <herve.codina@bootlin.com>,
David Rhodes <david.rhodes@cirrus.com>,
Richard Fitzgerald <rf@opensource.cirrus.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Nikita Shubin <nikita.shubin@maquefel.me>,
Axel Lin <axel.lin@ingics.com>,
Brian Austin <brian.austin@cirrus.com>,
linux-sound@vger.kernel.org, patches@opensource.cirrus.com,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [PATCH 1/3] ASoC: cs4271: Fix cs4271 I2C and SPI drivers automatic module loading
Date: Wed, 22 Oct 2025 19:46:26 +0200 [thread overview]
Message-ID: <d42ab1a0665f55731aabd1e9fcb31b8401b7913f.camel@gmail.com> (raw)
In-Reply-To: <d38779a7-a1af-49e4-b429-5ebd791e2168@sirena.org.uk>
Hi Mark,
On Wed, 2025-10-22 at 15:56 +0100, Mark Brown wrote:
> > > I'm very reluctant to touch this stuff for SPI without some very careful
> > > analysis that it's not going to cause things to explode on people, right
> > > now things seem to be working well enough so I'm not clear we'd be
> > > solving an actual problem.
>
> > The actual problem is that i2c-core is producing "of:" prefixed uevents
> > instead of "i2c:" prefixed uevents starting from v4.18.
>
> > Most of the dual-bus ASoC CODECs are affected.
>
> That's a description of what change but not of a concrete problem that
> users are experiencing.
the concrete problem Herve has experienced is that cs4271-i2c will not be
loaded automatically starting with Linux v4.18 (commit af503716ac14
"i2c: core: report OF style module alias for devices registered via OF").
> > Now declaring "of:" to be the new I2C bus prefix for uevents starting from
> > Linux v4.18 sounds strange.
>
> I think a robust solution would involve having the OF aliases namespaced
> by bus, or just not using the OF aliases but potentially having
> collisions if two vendors pick the same device name.
But this sounds like the situation before the above mentioned commit
af503716ac14, when both i2c and spi were symmetrically namespaced with
i2c: and spi: respectively and contained the "compatible" stripped of the
vendor prefix.
And I must admit that I had more understanding for the prior state of things.
--
Alexander Sverdlin.
next prev parent reply other threads:[~2025-10-22 17:46 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-16 13:03 [PATCH 0/3] Add support for an external Master Clock in the Cirrus CS4271 codec Herve Codina
2025-10-16 13:03 ` [PATCH 1/3] ASoC: cs4271: Fix cs4271 I2C and SPI drivers automatic module loading Herve Codina
2025-10-16 18:40 ` Alexander Sverdlin
2025-10-17 6:32 ` Herve Codina
2025-10-17 13:25 ` Alexander Sverdlin
2025-10-17 14:41 ` Alexander Sverdlin
2025-10-17 15:01 ` Mark Brown
2025-10-17 18:14 ` Alexander Sverdlin
2025-10-21 19:00 ` Mark Brown
2025-10-21 19:12 ` Alexander Sverdlin
2025-10-22 14:56 ` Mark Brown
2025-10-22 17:46 ` Alexander Sverdlin [this message]
2025-10-22 18:01 ` Mark Brown
2025-10-23 11:40 ` Javier Martinez Canillas
2025-10-23 12:32 ` Alexander Sverdlin
2025-10-17 15:10 ` Herve Codina
2025-10-17 15:35 ` Alexander Sverdlin
2025-10-17 16:03 ` Herve Codina
2025-10-21 17:25 ` Herve Codina
2025-10-16 13:03 ` [PATCH 2/3] ASoC: dt-bindings: cirrus,cs4271: Document mclk clock Herve Codina
2025-10-22 7:57 ` Krzysztof Kozlowski
2025-10-16 13:03 ` [PATCH 3/3] ASoC: cs4271: Add support for the external mclk Herve Codina
2025-10-16 19:14 ` Alexander Sverdlin
2025-10-16 19:17 ` Mark Brown
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=d42ab1a0665f55731aabd1e9fcb31b8401b7913f.camel@gmail.com \
--to=alexander.sverdlin@gmail.com \
--cc=axel.lin@ingics.com \
--cc=brian.austin@cirrus.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=david.rhodes@cirrus.com \
--cc=devicetree@vger.kernel.org \
--cc=herve.codina@bootlin.com \
--cc=javierm@redhat.com \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=nikita.shubin@maquefel.me \
--cc=patches@opensource.cirrus.com \
--cc=perex@perex.cz \
--cc=rf@opensource.cirrus.com \
--cc=robh@kernel.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=tiwai@suse.com \
--cc=wsa@the-dreams.de \
/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).