From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Marco Felsch <m.felsch@pengutronix.de>
Cc: Ahmad Fatoum <a.fatoum@barebox.org>, barebox@lists.infradead.org
Subject: Re: [PATCH 2/5] common: deep-probe: support specifying support in DT
Date: Mon, 2 Jun 2025 11:53:47 +0200 [thread overview]
Message-ID: <5ab3d160-8696-45ad-9ef7-ae537be9be62@pengutronix.de> (raw)
In-Reply-To: <20250528154650.rubzl2djaq4x6m5h@pengutronix.de>
Hi Marco,
On 28.05.25 17:46, Marco Felsch wrote:
> On 25-05-28, Ahmad Fatoum wrote:
>> Hi,
>>
>> On 5/28/25 17:24, Marco Felsch wrote:
>>> On 25-05-28, Ahmad Fatoum wrote:
>>>> New boards should be deep probe enabled by default, which is currently
>>>> done via board code. We want to support second stage boot on new boards
>>>> without board code however, which means we need the possibility to make
>>>> deep probe opt-out instead of opt-in.
>>>>
>>>> Signed-off-by: Ahmad Fatoum <a.fatoum@barebox.org>
>>>> ---
>>
>> [snip]
>>
>>>> + /* deep probe requires resources to be described in DT */
>>>> + root = of_get_root_node();
>>>> + if (!root)
>>>> + return false;
>>>
>>> if (!root) {
>>> boardstate = DEEP_PROBE_NOT_SUPPORTED;
>>
>> No, the omission is intentional. I want to repeat the check for the
>> root node on every call to avoid issues where this function is
>> called once too early.
>
> Good point albeit I wouldn't assume that this happens.
>
> Also what if caller-1 receives "no" does the "no-deep-probe-handling"
> accordingly and shortly after caller-2 receives "yes". Sounds like a
> source of trouble.
If a driver requests a resource and it is not available, it returns
-EPROBE_DEFER, even with deep probe enabled, so I think barebox
shouldn't handle such a case too badly.
> Anyway could we add a comment that this is intentional please?
Done for v2.
Thanks,
Ahmad
>
> Regards,
> Marco
>
>
>>
>>>> - boardstate = DEEP_PROBE_NOT_SUPPORTED;
>>>> - pr_info("not activated\n");
>>>> - return false;
>>>
>>> Can we please add a comment about the below if-else, e.g. referencing
>>> the barebox,deep-probe.rst as well?
>>
>> Yes, will do for v2.
>>
>> Thanks for reviewing,
>> Ahmad
>> --
>> Pengutronix e.K. | |
>> Steuerwalder Str. 21 | http://www.pengutronix.de/ |
>> 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
>> Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
>>
>>
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2025-06-02 9:54 UTC|newest]
Thread overview: 13+ 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-06-02 9:53 ` Ahmad Fatoum [this message]
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
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=5ab3d160-8696-45ad-9ef7-ae537be9be62@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=a.fatoum@barebox.org \
--cc=barebox@lists.infradead.org \
--cc=m.felsch@pengutronix.de \
/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