linux-kernel - Re: [PATCH RFC 03/16] pinctrl: aspeed: g5: Allow use of LPC node instead of LPC host controller

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: <0b94a728bdee2483d0e963bdae69178539ed7721.camel@codeconstruct.com.au>
Date: Fri, 09 Jan 2026 11:47:36 +1030
From: Andrew Jeffery <andrew@...econstruct.com.au>
To: Linus Walleij <linusw@...nel.org>
Cc: Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
  Conor Dooley <conor+dt@...nel.org>, Joel Stanley <joel@....id.au>,
 linux-hwmon@...r.kernel.org, 	devicetree@...r.kernel.org,
 linux-arm-kernel@...ts.infradead.org, 	linux-aspeed@...ts.ozlabs.org,
 linux-kernel@...r.kernel.org, 	openbmc@...ts.ozlabs.org,
 linux-gpio@...r.kernel.org, linux-mmc@...r.kernel.org, 
	linux-crypto@...r.kernel.org, linux-iio@...r.kernel.org
Subject: Re: [PATCH RFC 03/16] pinctrl: aspeed: g5: Allow use of LPC node
 instead of LPC host controller

On Wed, 2025-12-31 at 22:38 +0100, Linus Walleij wrote:
> On Thu, Dec 11, 2025 at 9:46 AM Andrew Jeffery
> <andrew@...econstruct.com.au> wrote:
> 
> > There's currently a wart where the Aspeed LPC host controller has no
> > binding specified, but the pinctrl binding depends on referencing its
> > node.
> > 
> > Allow specification of a phandle to the parent LPC controller instead.
> > Fall back to testing for a compatible parent node if the provided
> > phandle doesn't directly resolve to the LPC controller node.
> > 
> > Signed-off-by: Andrew Jeffery <andrew@...econstruct.com.au>
> 
> Reviewed-by: Linus Walleij <linusw@...nel.org>
> 
> I guess when this is non-RFC I will just apply these two patches.

Yeah, no dramas. I intend to split what remains to be applied into
separate (non-RFC) follow-up series now that many of the changes have
been applied.

Andrew