The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "Kumar, Udit" <u-kumar1@ti.com>
To: Siddharth Vadapalli <s-vadapalli@ti.com>, <nm@ti.com>,
	<vigneshr@ti.com>, <kristo@kernel.org>, <robh@kernel.org>,
	<krzk+dt@kernel.org>, <conor+dt@kernel.org>, <rogerq@kernel.org>
Cc: <devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<stable@vger.kernel.org>, <linux-arm-kernel@lists.infradead.org>,
	<srk@ti.com>, <u-kumar1@ti.com>
Subject: Re: [PATCH v2 1/2] arm64: dts: ti: k3-j722s-evm: Enable "serdes_wiz0" and "serdes_wiz1"
Date: Fri, 11 Apr 2025 19:26:35 +0530	[thread overview]
Message-ID: <b6cae091-caa8-41fa-97b1-fb243386b0b5@ti.com> (raw)
In-Reply-To: <20250408103606.3679505-2-s-vadapalli@ti.com>


On 4/8/2025 4:06 PM, Siddharth Vadapalli wrote:
> In preparation for disabling "serdes_wiz0" and "serdes_wiz1" device-tree
> nodes in the SoC file, enable them in the board file. The motivation for
> this change is that of following the existing convention of disabling
> nodes in the SoC file and only enabling the required ones in the board
> file.
>
> Fixes: 485705df5d5f ("arm64: dts: ti: k3-j722s: Enable PCIe and USB support on J722S-EVM")
> Cc: stable@vger.kernel.org
> Signed-off-by: Siddharth Vadapalli <s-vadapalli@ti.com>
> ---
>
> v1 of this patch is at:
> https://lore.kernel.org/r/20250408060636.3413856-2-s-vadapalli@ti.com/
> Changes since v1:
> - Added "Fixes" tag and updated commit message accordingly.
>
> Regards,
> Siddharth.
>
>   arch/arm64/boot/dts/ti/k3-j722s-evm.dts | 8 ++++++++
>   1 file changed, 8 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/ti/k3-j722s-evm.dts b/arch/arm64/boot/dts/ti/k3-j722s-evm.dts
> index 2127316f36a3..0bf2e1821662 100644
> --- a/arch/arm64/boot/dts/ti/k3-j722s-evm.dts
> +++ b/arch/arm64/boot/dts/ti/k3-j722s-evm.dts
> @@ -843,6 +843,10 @@ &serdes_ln_ctrl {
>   		      <J722S_SERDES1_LANE0_PCIE0_LANE0>;
>   };
>   
> +&serdes_wiz0 {
> +	status = "okay";
> +};
> +
>   &serdes0 {
>   	status = "okay";
>   	serdes0_usb_link: phy@0 {
> @@ -854,6 +858,10 @@ serdes0_usb_link: phy@0 {
>   	};
>   };
>   
> +&serdes_wiz1 {
> +	status = "okay";
> +};
> +

Reviewed-by: Udit Kumar <u-kumar1@ti.com>


>   &serdes1 {
>   	status = "okay";
>   	serdes1_pcie_link: phy@0 {

  reply	other threads:[~2025-04-11 13:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-08 10:36 [PATCH v2 0/2] J722S: Disable WIZ0 and WIZ1 in SoC file Siddharth Vadapalli
2025-04-08 10:36 ` [PATCH v2 1/2] arm64: dts: ti: k3-j722s-evm: Enable "serdes_wiz0" and "serdes_wiz1" Siddharth Vadapalli
2025-04-11 13:56   ` Kumar, Udit [this message]
2025-04-08 10:36 ` [PATCH v2 2/2] arm64: dts: ti: k3-j722s-main: Disable " Siddharth Vadapalli
2025-04-11 14:01   ` Kumar, Udit
2025-04-11 14:17     ` Siddharth Vadapalli
2025-04-11 15:52       ` Kumar, Udit
2025-04-12  5:33         ` Siddharth Vadapalli

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=b6cae091-caa8-41fa-97b1-fb243386b0b5@ti.com \
    --to=u-kumar1@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 \
    --cc=rogerq@kernel.org \
    --cc=s-vadapalli@ti.com \
    --cc=srk@ti.com \
    --cc=stable@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox