From: Moteen Shah <m-shah@ti.com>
To: <u-boot@lists.denx.de>, Tom Rini <trini@konsulko.com>
Cc: <sjg@chromium.org>, <alpernebiyasak@gmail.com>,
<quentin.schulz@cherry.de>, <m-chawdhry@ti.com>,
<n-francis@ti.com>, <vigneshr@ti.com>, <u-kumar1@ti.com>
Subject: Re: [PATCH 0/2 v2] Propagate bootph-all and bootph-some-ram property to all supernodes
Date: Thu, 26 Jun 2025 14:21:10 +0530 [thread overview]
Message-ID: <32e126ee-1c0e-4db6-aecd-601ffae37265@ti.com> (raw)
In-Reply-To: <f2e58917-85c0-42ef-8e26-0a059da0c6ae@ti.com>
Hey Tom,
Just wanted to have a check on the patch series.
Is there any change expected on this or is it good to go?
Regards,
Moteen
On 09/06/25 11:52, Moteen Shah wrote:
> Hello all,
>
> On 16/05/25 17:11, Moteen Shah wrote:
>> In the U-Boot pre-relocation stage, if the parent node lacks
>> bootph-all/bootph-some-ram property and the driver lacks a pre-reloc
>> flag, all of its subsequent subnodes gets skipped over from driver
>> binding—even if they have a bootph* property.
>>
>> This series addresses the issue by scanning through all the nodes during
>> build time and propagating the applicable property to all of its
>> supernode.
>>
>> Changes since v1:
>> - Carry reviewed-by from Simon
>> - Add a subnode-4 in testcase
>> - Change commit message and comments in control.py
>>
>> Link to v1:
>> https://lore.kernel.org/u-boot/20250512115028.1783305-1-m-shah@ti.com/
>>
>> Moteen Shah (2):
>> tools: binman: control.py: Propagate bootph-all/bootph-some-ram
>> properties to supernodes
>> tools: binman: ftest.py: Add testcase for bootph-* propagation
>>
>> tools/binman/control.py | 54 +++++++++++++++++++++++++++
>> tools/binman/ftest.py | 24 ++++++++++++
>> tools/binman/test/347_bootph_prop.dts | 21 +++++++++++
>> 3 files changed, 99 insertions(+)
>> create mode 100644 tools/binman/test/347_bootph_prop.dts
>>
>
> A gentle ping on this. Does this series requires any further changes?
>
> Regards,
> Moteen
>
next prev parent reply other threads:[~2025-06-26 8:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-16 11:41 [PATCH 0/2 v2] Propagate bootph-all and bootph-some-ram property to all supernodes Moteen Shah
2025-05-16 11:41 ` [PATCH 1/2 v2] tools: binman: control.py: Propagate bootph-all/bootph-some-ram properties to supernodes Moteen Shah
2025-05-16 13:34 ` Quentin Schulz
2025-05-16 11:41 ` [PATCH 2/2 v2] tools: binman: ftest.py: Add testcase for bootph-* propagation Moteen Shah
2025-06-09 6:22 ` [PATCH 0/2 v2] Propagate bootph-all and bootph-some-ram property to all supernodes Moteen Shah
2025-06-26 8:51 ` Moteen Shah [this message]
2025-06-26 17:56 ` Tom Rini
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=32e126ee-1c0e-4db6-aecd-601ffae37265@ti.com \
--to=m-shah@ti.com \
--cc=alpernebiyasak@gmail.com \
--cc=m-chawdhry@ti.com \
--cc=n-francis@ti.com \
--cc=quentin.schulz@cherry.de \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=u-kumar1@ti.com \
--cc=vigneshr@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.