From: Vignesh Raghavendra <vigneshr@ti.com>
To: Bryan Brattlof <bb@ti.com>, Nishanth Menon <nm@ti.com>,
Tero Kristo <kristo@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: <linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arm64: dts: ti: k3-am62: copy bootph flags to Linux
Date: Thu, 26 Jun 2025 09:32:22 +0530 [thread overview]
Message-ID: <02a85bf3-0c2e-48b6-9938-c4f8a50d662b@ti.com> (raw)
In-Reply-To: <20250624-62-uboot-cleanup-v1-1-c36230ab0375@ti.com>
On 24/06/25 20:20, Bryan Brattlof wrote:
> To keep things as organized as possible, copy the bootph-all properties
> from U-Boot for the packet DMA controller to indicate it should be
> available during all phases of bootup.
>
Above isn't a valid reason to add bootph-all properties to a node. You
would need to say why this DMA controller is needed during all phases of
boot, does this enable a certain boot-mode? Fix $subject to reflect the
same.
> Signed-off-by: Bryan Brattlof <bb@ti.com>
> ---
> arch/arm64/boot/dts/ti/k3-am62-main.dtsi | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/arm64/boot/dts/ti/k3-am62-main.dtsi b/arch/arm64/boot/dts/ti/k3-am62-main.dtsi
> index 9e0b6eee9ac77d66869915b2d7bec3e2275c03ea..2a727caf36ec44e4a023c5985d1bad9b80737633 100644
> --- a/arch/arm64/boot/dts/ti/k3-am62-main.dtsi
> +++ b/arch/arm64/boot/dts/ti/k3-am62-main.dtsi
> @@ -150,6 +150,7 @@ main_pktdma: dma-controller@485c0000 {
> "ring", "tchan", "rchan", "rflow";
> msi-parent = <&inta_main_dmss>;
> #dma-cells = <2>;
> + bootph-all;
>
> ti,sci = <&dmsc>;
> ti,sci-dev-id = <30>;
>
> ---
> base-commit: 19272b37aa4f83ca52bdf9c16d5d81bdd1354494
> change-id: 20250623-62-uboot-cleanup-dbec66f9e257
>
> Best regards,
--
Regards
Vignesh
https://ti.com/opensource
next prev parent reply other threads:[~2025-06-26 4:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-24 14:50 Bryan Brattlof
2025-06-26 4:02 ` Vignesh Raghavendra [this message]
2025-06-26 11:33 ` Bryan Brattlof
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=02a85bf3-0c2e-48b6-9938-c4f8a50d662b@ti.com \
--to=vigneshr@ti.com \
--cc=bb@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--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
all inboxes | Powered by JetHome®