From: Vignesh Raghavendra <vigneshr@ti.com>
To: Hrushikesh Salunke <h-salunke@ti.com>, <nm@ti.com>,
<kristo@kernel.org>, <robh@kernel.org>, <krzk+dt@kernel.org>,
<conor+dt@kernel.org>
Cc: <s-vadapalli@ti.com>, <linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<danishanwar@ti.com>
Subject: Re: [PATCH v2] arm64: dts: ti: k3-am642-evm-pcie0-ep: Add boot phase tag to "pcie0_ep"
Date: Wed, 11 Jun 2025 14:14:03 +0530 [thread overview]
Message-ID: <98e04654-a693-494d-9f60-930b6a4cd84a@ti.com> (raw)
In-Reply-To: <20250610054920.2395509-1-h-salunke@ti.com>
On 10/06/25 11:19, Hrushikesh Salunke wrote:
> AM64X SoC has one instance of PCIe which is PCIe0. To support PCIe boot
> on AM64X SoC, PCIe0 needs to be in endpoint mode and it needs to be
> functional at all stages of PCIe boot process. Thus add the
> "bootph-all" boot phase tag to "pcie0_ep" device tree node.
>
> Signed-off-by: Hrushikesh Salunke <h-salunke@ti.com>
> ---
> This patch is based on commit
> 475c850a7fdd Add linux-next specific files for 20250606
>
> Changes since v1
> As per feedback from Nishanth, changed the position of "bootph-all"
> tag, according to ordering rules for device tree properties.
>
> v1 : https://lore.kernel.org/all/20250609115930.w2s6jzg7xii55dlu@speckled/
>
> arch/arm64/boot/dts/ti/k3-am642-evm-pcie0-ep.dtso | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/arm64/boot/dts/ti/k3-am642-evm-pcie0-ep.dtso b/arch/arm64/boot/dts/ti/k3-am642-evm-pcie0-ep.dtso
> index 432751774853..a7e8d4ea98ac 100644
> --- a/arch/arm64/boot/dts/ti/k3-am642-evm-pcie0-ep.dtso
> +++ b/arch/arm64/boot/dts/ti/k3-am642-evm-pcie0-ep.dtso
> @@ -46,6 +46,7 @@ pcie0_ep: pcie-ep@f102000 {
> max-functions = /bits/ 8 <1>;
> phys = <&serdes0_pcie_link>;
> phy-names = "pcie-phy";
> + bootph-all;
> ti,syscon-pcie-ctrl = <&pcie0_ctrl 0x0>;
> };
> };
Are the patches for PCIe boot support merged to U-Boot or such other
bootloader repo?
--
Regards
Vignesh
https://ti.com/opensource
next prev parent reply other threads:[~2025-06-11 8:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-10 5:49 [PATCH v2] arm64: dts: ti: k3-am642-evm-pcie0-ep: Add boot phase tag to "pcie0_ep" Hrushikesh Salunke
2025-06-10 5:51 ` Siddharth Vadapalli
2025-06-11 8:44 ` Vignesh Raghavendra [this message]
2025-06-11 8:47 ` Hrushikesh Salunke
2025-06-12 10:16 ` Hrushikesh Salunke
2025-06-19 7:55 ` Vignesh Raghavendra
2025-06-19 8:33 ` Hrushikesh Salunke
2025-06-26 4:03 ` Vignesh Raghavendra
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=98e04654-a693-494d-9f60-930b6a4cd84a@ti.com \
--to=vigneshr@ti.com \
--cc=conor+dt@kernel.org \
--cc=danishanwar@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=h-salunke@ti.com \
--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 \
--cc=s-vadapalli@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox