All of lore.kernel.org
 help / color / mirror / Atom feed
From: Quentin Schulz <quentin.schulz@cherry.de>
To: Moteen Shah <m-shah@ti.com>, u-boot@lists.denx.de
Cc: trini@konsulko.com, sjg@chromium.org, alpernebiyasak@gmail.com,
	m-chawdhry@ti.com, n-francis@ti.com, vigneshr@ti.com,
	u-kumar1@ti.com
Subject: Re: [PATCH 1/2 v2] tools: binman: control.py: Propagate bootph-all/bootph-some-ram properties to supernodes
Date: Fri, 16 May 2025 15:34:46 +0200	[thread overview]
Message-ID: <5a645375-cab0-45e1-91c0-372ff8e8a186@cherry.de> (raw)
In-Reply-To: <20250516114148.3862114-2-m-shah@ti.com>

Hi Moteen,

On 5/16/25 1:41 PM, Moteen Shah wrote:
> As per bootph schema, bootph-* property in child node should be
> implied in their parent, but this feature is not implemented in
> the U-Boot proper stage (before relocation) resulting in devices
> not being bound because of the missing bootph-all or bootph-some-ram
> property in the parent node.
> 
> To mitigate this issue, add a function to scan through all the nodes
> in the device-tree for bootph-all and bootph-some-ram properties. If
> found, propagate it to all of its parent nodes up the hierarchy.
> 
> Signed-off-by: Moteen Shah <m-shah@ti.com>
> Signed-off-by: Simon Glass <sjg@chromium.org>
> 
> Reviewed-by: Simon Glass <sjg@chromium.org>
> 

Reviewed-by: Quentin Schulz <quentin.schulz@cherry.de>

Thanks!
Quentin

  reply	other threads:[~2025-05-16 13:34 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 [this message]
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
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=5a645375-cab0-45e1-91c0-372ff8e8a186@cherry.de \
    --to=quentin.schulz@cherry.de \
    --cc=alpernebiyasak@gmail.com \
    --cc=m-chawdhry@ti.com \
    --cc=m-shah@ti.com \
    --cc=n-francis@ti.com \
    --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.