linux-kernel - Re: [PATCH 3/3] ASoC: ak5558: Fix the supply names

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <aYxpPX3LQ8RGgIBz@smile.fi.intel.com>
Date: Wed, 11 Feb 2026 13:34:21 +0200
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Shengjiu Wang <shengjiu.wang@...il.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, ckeepax@...nsource.cirrus.com,
	nichen@...as.ac.cn, kuninori.morimoto.gx@...esas.com
Subject: Re: [PATCH 3/3] ASoC: ak5558: Fix the supply names

On Wed, Feb 11, 2026 at 07:29:42PM +0800, Shengjiu Wang wrote:
> On Wed, Feb 11, 2026 at 7:21 PM Andy Shevchenko
> <andriy.shevchenko@...ux.intel.com> wrote:
> > On Wed, Feb 11, 2026 at 05:35:27PM +0800, Shengjiu Wang wrote:
> > > According to the binding document, the supply name characters are
> > > lowercase.
> >
> > Same question. If it's okay to convert, please elaborate that it doesn't have
> > any side-effects for in-kernel users. Also, check if these names may come from
> > DTS (some old DTS might have it, in such case it's a documentation issue, or
> > driver needs to support both).
> 
> Thanks.
> 
> I go through all the DTS,  no DTS uses DVDD/AVDD or dvdd/avdd for ak4458 and
> ak5558 codecs.  so there is no side-effect.

You mean no "in-kernel" DTS. But my question was if any DTS in the world may
supply this as AVDD? If answer is yes, the binding must be changed. But then
the same issue may come due to somebody using a new binding somewhere. however
I don't understand how in that case it will work in Linux (only other projects
that use the same bindings as Linux kernel may be affected).

> I just am thinking it is better to fix it in document, it is caused
> by converting txt to dtschema.

I think this sounds at least like a safer change.

-- 
With Best Regards,
Andy Shevchenko