public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Kathiravan Thirumoorthy
	<kathiravan.thirumoorthy@oss.qualcomm.com>,
	Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: qcom: ipq5210: add the bootph-all property
Date: Thu, 9 Apr 2026 12:03:37 +0200	[thread overview]
Message-ID: <8fe36a5e-1ebc-4c5f-9c3b-3c50ebd2274e@kernel.org> (raw)
In-Reply-To: <20260409-add_bootph-v1-1-cb2b5093f7d7@oss.qualcomm.com>

On 09/04/2026 11:28, Kathiravan Thirumoorthy wrote:
> Add the bootph-all property to the nodes which are utilized by the
> bootloaders.

Uh oh, so it started for qcom too? I really don't like how these bootph
properties spread all over, so please provide arguments - which pure
upstream bootloaders exactly and why exactly these nodes.

> 
> Signed-off-by: Kathiravan Thirumoorthy <kathiravan.thirumoorthy@oss.qualcomm.com>
> ---
>  arch/arm64/boot/dts/qcom/ipq5210-rdp504.dts |  5 +++++
>  arch/arm64/boot/dts/qcom/ipq5210.dtsi       | 10 ++++++++++
>  2 files changed, 15 insertions(+)
> 
> diff --git a/arch/arm64/boot/dts/qcom/ipq5210-rdp504.dts b/arch/arm64/boot/dts/qcom/ipq5210-rdp504.dts
> index 941f866ecfe9..56dbc506da78 100644
> --- a/arch/arm64/boot/dts/qcom/ipq5210-rdp504.dts
> +++ b/arch/arm64/boot/dts/qcom/ipq5210-rdp504.dts
> @@ -17,6 +17,7 @@ aliases {
>  
>  	chosen {
>  		stdout-path = "serial0";
> +		bootph-all;

Since when do we add bootph-all to chosen? Which broken bootloader
ignores chosen?

This really makes me wonder that you do all this for some downstream forks.

>  	};
>  };
>  
> @@ -41,6 +42,7 @@ qup_uart1_default_state: qup-uart1-default-state {
>  		function = "qup_se1";
>  		drive-strength = <6>;
>  		bias-pull-down;
> +		bootph-all;
>  	};
And that's a pin, not a device. What is the point of marking it? The
device needing this pin will have phandle which must pull the node.

Best regards,
Krzysztof

      reply	other threads:[~2026-04-09 10:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-09  9:28 [PATCH] arm64: dts: qcom: ipq5210: add the bootph-all property Kathiravan Thirumoorthy
2026-04-09 10:03 ` Krzysztof Kozlowski [this message]

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=8fe36a5e-1ebc-4c5f-9c3b-3c50ebd2274e@kernel.org \
    --to=krzk@kernel.org \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=kathiravan.thirumoorthy@oss.qualcomm.com \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.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