mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dragan Simic <dsimic@manjaro.org>
To: Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>
Cc: Naresh Kamboju <naresh.kamboju@linaro.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	stable@vger.kernel.org, patches@lists.linux.dev,
	linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
	akpm@linux-foundation.org, linux@roeck-us.net, shuah@kernel.org,
	patches@kernelci.org, lkft-triage@lists.linaro.org,
	pavel@denx.de, jonathanh@nvidia.com, f.fainelli@gmail.com,
	sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de,
	conor@kernel.org, hargar@microsoft.com, broonie@kernel.org,
	Heiko Stuebner <heiko@sntech.de>,
	Vegard Nossum <vegard.nossum@oracle.com>,
	Darren Kenny <darren.kenny@oracle.com>,
	Diederik de Haas <didi.debian@cknow.org>
Subject: Re: [PATCH 6.6 00/77] 6.6.85-rc1 review
Date: Wed, 26 Mar 2025 04:56:18 +0100	[thread overview]
Message-ID: <0001e7e020145983055d154488f5c460@manjaro.org> (raw)
In-Reply-To: <751cf2c6-c692-4595-98e9-fa3ae4dfd10a@oracle.com>

Hello Harshit and Greg,

On 2025-03-26 03:33, Harshit Mogalapalli wrote:
> On 25/03/25 21:37, Dragan Simic wrote:
>> On 2025-03-25 16:07, Naresh Kamboju wrote:
> ...
>>> Build regression: arm64 dtb rockchip non-existent node or label 
>>> "vcca_0v9"
>>> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
>>> 
>>> ## Build log
>>> arch/arm64/boot/dts/rockchip/rk3399.dtsi:221.23-266.4: ERROR
>>> (phandle_references):
>>> /pcie@f8000000: Reference to non-existent node or label "vcca_0v9"
>>> 
>>>   also defined at arch/arm64/boot/dts/rockchip/rk3399- 
>>> rockpro64.dtsi:659.8-669.3
> ...
>> 
>> This is caused by another patch from the original series failing
>> to apply due to some bulk regulator renaming.  I'll send backported
>> version of that patch soon, which should make everything fine.
> 
> On ARM configs, we do see the same issue that Naresh reported.
> 
> arch/arm64/boot/dts/rockchip/rk3399.dtsi:221.23-266.4: ERROR
> (phandle_references): /pcie@f8000000: Reference to non-existent node
> or label "vcca_0v9"
>  also defined at 
> arch/arm64/boot/dts/rockchip/rk3399-rockpro64.dtsi:659.8-669.3
> ERROR: Input tree has errors, aborting (use -f to force output)
> make[3]: *** [scripts/Makefile.lib:423:
> arch/arm64/boot/dts/rockchip/rk3399-rockpro64-v2.dtb] Error 2
> make[3]: *** Waiting for unfinished jobs....
> arch/arm64/boot/dts/rockchip/rk3399.dtsi:221.23-266.4: ERROR
> (phandle_references): /pcie@f8000000: Reference to non-existent node
> or label "vcca_0v9"
>  also defined at 
> arch/arm64/boot/dts/rockchip/rk3399-rockpro64.dtsi:659.8-669.3
> ERROR: Input tree has errors, aborting (use -f to force output)
> make[3]: *** [scripts/Makefile.lib:423:
> arch/arm64/boot/dts/rockchip/rk3399-rockpro64.dtb] Error 2
> make[2]: *** [scripts/Makefile.build:480: arch/arm64/boot/dts/rockchip] 
> Error 2
> make[2]: *** Waiting for unfinished jobs....
> 
> Caused by commit: 1e4bd0ec5a47 ("arm64: dts: rockchip: Add missing
> PCIe supplies to RockPro64 board dtsi") -- PATCH 42/77 of this series.
> 
> We see same problem with 6.12.21-rc1 as well.
> 
> Notes:
> -----
> I think Dragan was referring to upstream commit: bd1c959f37f3 ("arm64:
> dts: rockchip: Add avdd HDMI supplies to RockPro64 board dtsi") which
> will fix this problem but fails to apply due to regulator renaming in
> commit: 5c96e6330197 ("arm64: dts: rockchip: adapt regulator nodenames
> to preferred form") which is not in stable kernels(6.6.y and 6.12.y)

Exactly, the direct dependency is the commit bd1c959f37f3 ("arm64:
dts: rockchip: Add avdd HDMI supplies to RockPro64 board dtsi"),
for which I haven't sent the backported version yet.

As Diederik pointed it out already in a separate message [*] from
a couple of days ago, it might be the best to include the commit
5c96e6330197 ("arm64: dts: rockchip: adapt regulator nodenames to
preferred form") into stable kernels as well.

Obviously, including the commit 5c96e6330197 pretty much goes
against the rules of stable kernels, but it would save a lot of
time and effort in the future.

[*] https://lore.kernel.org/stable/D8ONE4WEF7A2.1OE1YY8J34MM3@cknow.org/

  reply	other threads:[~2025-03-26  3:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-25 12:21 Greg Kroah-Hartman
2025-03-25 15:07 ` Naresh Kamboju
2025-03-25 16:07   ` Dragan Simic
2025-03-25 23:36     ` Greg Kroah-Hartman
2025-03-26  2:33     ` Harshit Mogalapalli
2025-03-26  3:56       ` Dragan Simic [this message]
2025-03-26 15:38         ` Greg Kroah-Hartman
2025-03-27  7:12           ` Dragan Simic
2025-03-25 17:25 ` Florian Fainelli

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=0001e7e020145983055d154488f5c460@manjaro.org \
    --to=dsimic@manjaro.org \
    --cc=akpm@linux-foundation.org \
    --cc=broonie@kernel.org \
    --cc=conor@kernel.org \
    --cc=darren.kenny@oracle.com \
    --cc=didi.debian@cknow.org \
    --cc=f.fainelli@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hargar@microsoft.com \
    --cc=harshit.m.mogalapalli@oracle.com \
    --cc=heiko@sntech.de \
    --cc=jonathanh@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=lkft-triage@lists.linaro.org \
    --cc=naresh.kamboju@linaro.org \
    --cc=patches@kernelci.org \
    --cc=patches@lists.linux.dev \
    --cc=pavel@denx.de \
    --cc=rwarsow@gmx.de \
    --cc=shuah@kernel.org \
    --cc=srw@sladewatkins.net \
    --cc=stable@vger.kernel.org \
    --cc=sudipm.mukherjee@gmail.com \
    --cc=torvalds@linux-foundation.org \
    --cc=vegard.nossum@oracle.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

all inboxes | Powered by JetHome®