From: Paul Walmsley <pjw@kernel.org>
To: Rob Herring <robh@kernel.org>
Cc: Paul Walmsley <pjw@kernel.org>,
Guenter Roeck <linux@roeck-us.net>,
Saravana Kannan <saravanak@google.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org, Han Gao <rabenda.cn@gmail.com>
Subject: Re: [PATCH] of: Skip devicetree kunit tests when RISCV+ACPI doesn't populate root node
Date: Thu, 23 Oct 2025 20:54:13 -0600 (MDT) [thread overview]
Message-ID: <1260cd8c-2904-1a21-d7ad-ba9b82f67797@kernel.org> (raw)
In-Reply-To: <CAL_JsqJjiB3h+hzstXSbnyFy+U39GgtT=rcb4r+QDv=uL54H8g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1881 bytes --]
On Thu, 23 Oct 2025, Rob Herring wrote:
> On Thu, Oct 23, 2025 at 11:48 AM Paul Walmsley <pjw@kernel.org> wrote:
> >
> > On Thu, 23 Oct 2025, Guenter Roeck wrote:
> >
> > > Starting with commit 69a8b62a7aa1 ("riscv: acpi: avoid errors caused by
> > > probing DT devices when ACPI is used"), riscv images no longer populate
> > > devicetree if ACPI is enabled. This causes unit tests to fail which require
> > > the root node to be set.
> > >
> > > # Subtest: of_dtb
> > > # module: of_test
> > > 1..2
> > > # of_dtb_root_node_found_by_path: EXPECTATION FAILED at drivers/of/of_test.c:21
> > > Expected np is not null, but is
> > > # of_dtb_root_node_found_by_path: pass:0 fail:1 skip:0 total:1
> > > not ok 1 of_dtb_root_node_found_by_path
> > > # of_dtb_root_node_populates_of_root: EXPECTATION FAILED at drivers/of/of_test.c:31
> > > Expected of_root is not null, but is
> > > # of_dtb_root_node_populates_of_root: pass:0 fail:1 skip:0 total:1
> > > not ok 2 of_dtb_root_node_populates_of_root
> > >
> > > Skip those tests for RISCV if the root node is not populated.
> > >
> > > Fixes: 69a8b62a7aa1 ("riscv: acpi: avoid errors caused by probing DT devices when ACPI is used")
> > > Cc: Han Gao <rabenda.cn@gmail.com>
> > > Cc: Paul Walmsley <pjw@kernel.org>
> > > Signed-off-by: Guenter Roeck <linux@roeck-us.net>
> >
> > Reviewed-by: Paul Walmsley <pjw@kernel.org> # arch/riscv
>
> FWIW, the fixed commit will also prevent enabling features like this
> series[1] enables. Arm64 is still disabled ATM because of disagreement
> with the arm64 maintainers, so that can was kicked down the road. It
> would be better to not disable this and address the issues as they
> happen rather than breaking people down the road.
Thanks for the context, Rob. Can you share a pointer to the ARM64
disagreement thread(s) (either publicly or privately)?
- Paul
next prev parent reply other threads:[~2025-10-24 2:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-23 16:04 [PATCH] of: Skip devicetree kunit tests when RISCV+ACPI doesn't populate root node Guenter Roeck
2025-10-23 16:48 ` Paul Walmsley
2025-10-24 1:00 ` Rob Herring
2025-10-24 2:54 ` Paul Walmsley [this message]
2025-10-24 12:02 ` Rob Herring
2025-10-24 3:45 ` Guenter Roeck
2025-11-12 19:58 ` Rob Herring (Arm)
2025-11-14 2:53 ` Paul Walmsley
2025-11-21 1:06 ` Rob Herring
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=1260cd8c-2904-1a21-d7ad-ba9b82f67797@kernel.org \
--to=pjw@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux@roeck-us.net \
--cc=rabenda.cn@gmail.com \
--cc=robh@kernel.org \
--cc=saravanak@google.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;
as well as URLs for NNTP newsgroup(s).