[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e7873e6ce07cd92f4b5ce8880aa81b12c2a08ed3.camel@gmail.com>
Date: Tue, 21 Oct 2025 21:12:13 +0200
From: Alexander Sverdlin <alexander.sverdlin@...il.com>
To: Mark Brown <broonie@...nel.org>
Cc: Javier Martinez Canillas <javierm@...hat.com>, Wolfram Sang
<wsa@...-dreams.de>, Herve Codina <herve.codina@...tlin.com>, David Rhodes
<david.rhodes@...rus.com>, Richard Fitzgerald <rf@...nsource.cirrus.com>,
Liam Girdwood <lgirdwood@...il.com>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley
<conor+dt@...nel.org>, Jaroslav Kysela <perex@...ex.cz>, Takashi Iwai
<tiwai@...e.com>, Nikita Shubin <nikita.shubin@...uefel.me>, Axel Lin
<axel.lin@...ics.com>, Brian Austin <brian.austin@...rus.com>,
linux-sound@...r.kernel.org, patches@...nsource.cirrus.com,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org, Thomas Petazzoni
<thomas.petazzoni@...tlin.com>
Subject: Re: [PATCH 1/3] ASoC: cs4271: Fix cs4271 I2C and SPI drivers
automatic module loading
Hi Mark!
On Tue, 2025-10-21 at 20:00 +0100, Mark Brown wrote:
> On Fri, Oct 17, 2025 at 08:14:43PM +0200, Alexander Sverdlin wrote:
>
> > "Reparing" them as Herve proposed would result in I2C modules being
> > loaded only via "of:" style modalias and SPI still via "spi:". Which
> > sounds all but consistent.
>
> > If SPI ever adopts the same of_device_uevent_modalias(), both backends
> > would require "of:" prefixed modalias, and it will not be possible to
> > load the proper one for the corresponding bus type.
>
> > What are your thoughs on this?
>
> Or at least you'd get both modules loaded with one being redundant. TBH
I'm quite confident that udev/modprobe will load only the first module
from modules.alias file.
> 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.
Now declaring "of:" to be the new I2C bus prefix for uevents starting from
Linux v4.18 sounds strange.
--
Alexander Sverdlin.
Powered by blists - more mailing lists