From: Siddharth Vadapalli <s-vadapalli@ti.com>
To: Ravi Gunasekaran <r-gunasekaran@ti.com>
Cc: <nm@ti.com>, <vigneshr@ti.com>, <afd@ti.com>, <robh@kernel.org>,
<rogerq@kernel.org>, <kristo@kernel.org>, <krzk+dt@kernel.org>,
<conor+dt@kernel.org>, <srk@ti.com>, <s-vadapalli@ti.com>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 3/3] arm64: dts: ti: k3-j722s-evm: Update USB0 and USB1
Date: Fri, 24 May 2024 11:14:16 +0530 [thread overview]
Message-ID: <a94bccd1-c0a9-4381-ac36-32c73aad07e5@ti.com> (raw)
In-Reply-To: <20240513114443.16350-4-r-gunasekaran@ti.com>
On Mon, May 13, 2024 at 05:14:43PM +0530, Ravi Gunasekaran wrote:
> The GPIO expander on the EVM allows the USB selection for Type-C
> port to either USB0 or USB1 via USB hub. By default, let the Type-C
> port select USB0 via the GPIO expander port P05.
>
> Enable super-speed on USB1 by updating SerDes0 lane configuration.
>
> Signed-off-by: Ravi Gunasekaran <r-gunasekaran@ti.com>
> ---
>
[...]
> @@ -384,3 +399,43 @@
> status = "okay";
> bootph-all;
> };
> +
> +&serdes0_ln_ctrl {
> + idle-states = <J722S_SERDES0_LANE0_USB>,
> + <J722S_SERDES1_LANE0_PCIE0_LANE0>;
Patch 1/3 only added the Mux for Serdes0. So the idle-states property
for Serdes1 is incorrect and should be dropped.
[...]
Regards,
Siddharth.
prev parent reply other threads:[~2024-05-24 5:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-13 11:44 [PATCH v2 0/3] arm64: dts: ti: Add USB support for J722S EVM Ravi Gunasekaran
2024-05-13 11:44 ` [PATCH v2 1/3] arm64: dts: ti: k3-j722s-main: Add support for SERDES0 Ravi Gunasekaran
2024-05-13 11:49 ` Ravi Gunasekaran
2024-05-13 11:44 ` [PATCH v2 2/3] arm64: dts: ti: k3-j722s-main: Redefine USB1 node description Ravi Gunasekaran
2024-05-13 11:44 ` [PATCH v2 3/3] arm64: dts: ti: k3-j722s-evm: Update USB0 and USB1 Ravi Gunasekaran
2024-05-24 5:44 ` Siddharth Vadapalli [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=a94bccd1-c0a9-4381-ac36-32c73aad07e5@ti.com \
--to=s-vadapalli@ti.com \
--cc=afd@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=r-gunasekaran@ti.com \
--cc=robh@kernel.org \
--cc=rogerq@kernel.org \
--cc=srk@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 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®