From: Marco Felsch <m.felsch@pengutronix.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 1/2] of: base: add new barebox,status property
Date: Wed, 21 Jan 2026 12:22:13 +0100 [thread overview]
Message-ID: <20260121112213.yo7eyytvssk3vufj@pengutronix.de> (raw)
In-Reply-To: <20260120181333.3375979-1-a.fatoum@pengutronix.de>
On 26-01-20, Ahmad Fatoum wrote:
> I am confronted with an occasional hang on the Radxa Rock 3A during
> PCI probe. The board has no PCI devices connected.
>
> This hang doesn't happen in Linux and doesn't happen on the QNAP
> TS433-eU, which is also RK3568, but actually has PCIe devices, which are
> probed normally.
>
> For such purposes, add a barebox,status property as setting the status
> to disabled, would impact Linux as well if barebox were to pass along
> its own device tree.
>
> Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
> ---
> .../devicetree/bindings/barebox/barebox,status.rst | 8 ++++++++
> drivers/of/base.c | 4 +++-
> 2 files changed, 11 insertions(+), 1 deletion(-)
> create mode 100644 Documentation/devicetree/bindings/barebox/barebox,status.rst
>
> diff --git a/Documentation/devicetree/bindings/barebox/barebox,status.rst b/Documentation/devicetree/bindings/barebox/barebox,status.rst
> new file mode 100644
> index 000000000000..06524b218fb1
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/barebox/barebox,status.rst
> @@ -0,0 +1,8 @@
> +barebox,status property
> +=======================
> +
> +barebox interprets ``barebox,status`` the same as it does ``status``,
> +but gives the former precedence if both exist.
> +
> +Use this property only for devices for which barebox has a driver, but
> +that barebox should not be probing on a per-board basis.
I would rephrase the 2nd sentence a bit:
"""
The purpose of this property is to keep the status property of the
upstream DT, provided by Linux, untouched.
This may be necessary to temporary workaround broken barebox drivers on
a per-board basis in case you can't disable the driver due to a
multi-config build.
"""
Regards,
Marco
> diff --git a/drivers/of/base.c b/drivers/of/base.c
> index 54fd458bd9a1..4e83a757a4e9 100644
> --- a/drivers/of/base.c
> +++ b/drivers/of/base.c
> @@ -2149,7 +2149,9 @@ int of_device_is_available(const struct device_node *device)
> const char *status;
> int statlen;
>
> - status = of_get_property(device, "status", &statlen);
> + status = of_get_property(device, "barebox,status", &statlen);
> + if (status == NULL)
> + status = of_get_property(device, "status", &statlen);
> if (status == NULL)
> return 1;
>
> --
> 2.47.3
>
>
>
--
#gernperDu
#CallMeByMyFirstName
Pengutronix e.K. | |
Steuerwalder Str. 21 | https://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-9 |
next prev parent reply other threads:[~2026-01-21 11:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-20 18:13 Ahmad Fatoum
2026-01-20 18:13 ` [PATCH 2/2] arm: dts: rk356x: rock3a: disable pcie3x2 Ahmad Fatoum
2026-01-21 0:07 ` Marco Felsch
2026-01-21 7:52 ` Ahmad Fatoum
2026-01-21 9:16 ` Marco Felsch
2026-01-21 9:41 ` Ahmad Fatoum
2026-01-21 10:15 ` Marco Felsch
2026-01-21 11:02 ` Ahmad Fatoum
2026-01-21 11:22 ` Marco Felsch [this message]
2026-01-21 11:31 [PATCH 1/2] of: base: add new barebox,status property Ahmad Fatoum
2026-01-21 11:33 ` Ahmad Fatoum
2026-01-21 11:59 ` Marco Felsch
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=20260121112213.yo7eyytvssk3vufj@pengutronix.de \
--to=m.felsch@pengutronix.de \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
/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