public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Charles Keepax <ckeepax@opensource.cirrus.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Shengjiu Wang <shengjiu.wang@nxp.com>,
	lgirdwood@gmail.com, broonie@kernel.org, robh@kernel.org,
	krzk+dt@kernel.org, conor+dt@kernel.org,
	linux-sound@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, perex@perex.cz, tiwai@suse.com,
	nichen@iscas.ac.cn, kuninori.morimoto.gx@renesas.com
Subject: Re: [PATCH 2/3] ASoC: ak4458: Fix the supply names
Date: Wed, 11 Feb 2026 11:50:43 +0000	[thread overview]
Message-ID: <aYxtE9itdo/aYvVc@opensource.cirrus.com> (raw)
In-Reply-To: <aYxlh2YDmBrvCOCs@smile.fi.intel.com>

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

  reply	other threads:[~2026-02-11 11:51 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-11  9:35 [PATCH 0/3] ASoC: codec: fixes for ak4458 and ak5558 codecs Shengjiu Wang
2026-02-11  9:35 ` [PATCH 1/3] ASoC: dt-bindings: asahi-kasei,ak4458: set unevaluatedProperties:false Shengjiu Wang
2026-02-11 21:53   ` Rob Herring
2026-02-12  1:43     ` Shengjiu Wang
2026-02-12  2:38       ` Rob Herring
2026-02-12  2:59         ` Shengjiu Wang
2026-02-11  9:35 ` [PATCH 2/3] ASoC: ak4458: Fix the supply names Shengjiu Wang
2026-02-11 11:16   ` Shengjiu Wang
2026-02-11 11:18   ` Andy Shevchenko
2026-02-11 11:50     ` Charles Keepax [this message]
2026-02-11  9:35 ` [PATCH 3/3] ASoC: ak5558: " Shengjiu Wang
2026-02-11 11:18   ` Shengjiu Wang
2026-02-11 11:21     ` Andy Shevchenko
2026-02-11 11:20   ` Andy Shevchenko
2026-02-11 11:29     ` Shengjiu Wang
2026-02-11 11:34       ` Andy Shevchenko
2026-02-11 12:55 ` [PATCH 0/3] ASoC: codec: fixes for ak4458 and ak5558 codecs Shengjiu Wang

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=aYxtE9itdo/aYvVc@opensource.cirrus.com \
    --to=ckeepax@opensource.cirrus.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=broonie@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=nichen@iscas.ac.cn \
    --cc=perex@perex.cz \
    --cc=robh@kernel.org \
    --cc=shengjiu.wang@nxp.com \
    --cc=tiwai@suse.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