[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aYxtE9itdo/aYvVc@opensource.cirrus.com>
Date: Wed, 11 Feb 2026 11:50:43 +0000
From: Charles Keepax <ckeepax@...nsource.cirrus.com>
To: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Cc: Shengjiu Wang <shengjiu.wang@....com>, lgirdwood@...il.com,
broonie@...nel.org, robh@...nel.org, krzk+dt@...nel.org,
conor+dt@...nel.org, linux-sound@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
perex@...ex.cz, tiwai@...e.com, nichen@...as.ac.cn,
kuninori.morimoto.gx@...esas.com
Subject: Re: [PATCH 2/3] ASoC: ak4458: Fix the supply names
On Wed, Feb 11, 2026 at 01:18:31PM +0200, Andy Shevchenko wrote:
> On Wed, Feb 11, 2026 at 05:35:26PM +0800, Shengjiu Wang wrote:
> > According to the binding document, the supply name characters are
> > lowercase.
>
> ...
>
> > static const char *ak4458_supply_names[AK4458_NUM_SUPPLIES] = {
> > - "DVDD",
> > - "AVDD",
> > + "dvdd",
> > + "avdd",
> > };
>
> In kernel we also have
>
> arch/arm/boot/dts/actions/owl-s500-roseapplepi.dts:123: regulator-name = "AVDD";
> arch/arm/mach-s3c/mach-crag6410.c:631: REGULATOR_SUPPLY("AVDD", "spi0.0"),
> arch/arm/mach-s3c/mach-crag6410.c:632: REGULATOR_SUPPLY("AVDD", "spi0.1"),
> arch/arm/mach-s3c/mach-crag6410.c:655: REGULATOR_SUPPLY("AVDD", "1-001a"),
> arch/arm/mach-s3c/mach-crag6410.c:661: REGULATOR_SUPPLY("AVDD", "1-003a"),
>
> Are those related? Can they affect this one?
No idea about the roseapplepi one but all the crag6410 ones
are totally different devices from this series.
Thanks,
Charles
Powered by blists - more mailing lists