[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <59e004d7-7e46-4141-bf61-f01a6e5296e2@sirena.org.uk>
Date: Tue, 17 Dec 2024 21:19:17 +0000
From: Mark Brown <broonie@...nel.org>
To: Andrew Davis <afd@...com>
Cc: Shree Ramamoorthy <s-ramamoorthy@...com>, aaro.koskinen@....fi,
andreas@...nade.info, khilman@...libre.com, rogerq@...nel.org,
tony@...mide.com, lgirdwood@...il.com, linux-omap@...r.kernel.org,
linux-kernel@...r.kernel.org, m-leonard@...com, praneeth@...com
Subject: Re: [PATCH v1 2/4] regulator: tps65219: Update driver name
On Tue, Dec 17, 2024 at 03:16:44PM -0600, Andrew Davis wrote:
> On 12/17/24 3:01 PM, Mark Brown wrote:
> > This isn't just a naming convention thing AFACIT, the MFD registers the
> > new name so the driver wouldn't previously have loaded. How did this
> > ever work?
> It matches based on the platform device .id_table[0] which does have
> "tps65219-regulator" listed, the driver .name itself is only used
> as a last fallback when there is no .id_table.
Ah, there's not enough context in the diff to show the ID table.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists