From: Marco Felsch <m.felsch@pengutronix.de>
To: Ahmad Fatoum <a.fatoum@barebox.org>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 3/5] treewide: dts: describe deep probe support in device tree
Date: Wed, 28 May 2025 17:26:14 +0200 [thread overview]
Message-ID: <20250528152614.7hhq2r2zpjsu2bwu@pengutronix.de> (raw)
In-Reply-To: <20250528131411.935668-3-a.fatoum@barebox.org>
On 25-05-28, Ahmad Fatoum wrote:
> Now that we have CONFIG_DEEP_PROBE_DEFAULT, annotate our device trees to
> explicitly opt-out and opt-in from deep probe.
>
> The opt-out is necessary, so boards aren't broken by whether we have
> CONFIG_DEEP_PROBE_DEFAULT enabled or not. The opt-in is optional,
> because all deep-probe enabled boards have a BAREBOX_DEEP_PROBE_ENABLE
> in board code, but in future we could omit that.
>
> Signed-off-by: Ahmad Fatoum <a.fatoum@barebox.org>
Reviewed-by: Marco Felsch <m.felsch@pengutronix.de>
next prev parent reply other threads:[~2025-05-28 16:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-28 13:14 [PATCH 1/5] common: deep-probe: inform only about lack of deep-probe support Ahmad Fatoum
2025-05-28 13:14 ` [PATCH 2/5] common: deep-probe: support specifying support in DT Ahmad Fatoum
2025-05-28 15:24 ` Marco Felsch
2025-05-28 15:40 ` Ahmad Fatoum
2025-05-28 15:46 ` Marco Felsch
2025-05-28 13:14 ` [PATCH 3/5] treewide: dts: describe deep probe support in device tree Ahmad Fatoum
2025-05-28 15:26 ` Marco Felsch [this message]
2025-05-28 13:14 ` [PATCH 4/5] ARM: configs: enable deep probe for the most popular configs Ahmad Fatoum
2025-05-28 15:26 ` Marco Felsch
2025-05-28 13:14 ` [PATCH 5/5] Documentation: migration-2025.07.0: document CONFIG_DEEP_PROBE_DEFAULT Ahmad Fatoum
2025-05-28 15:28 ` Marco Felsch
2025-05-28 14:59 ` [PATCH 1/5] common: deep-probe: inform only about lack of deep-probe support 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=20250528152614.7hhq2r2zpjsu2bwu@pengutronix.de \
--to=m.felsch@pengutronix.de \
--cc=a.fatoum@barebox.org \
--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