From: Akashdeep Kaur <a-kaur@ti.com>
To: Kendall Willis <k-willis@ti.com>, <praneeth@ti.com>, <nm@ti.com>,
<afd@ti.com>, <vigneshr@ti.com>, <d-gole@ti.com>,
<u-kumar1@ti.com>, <sebin.francis@ti.com>, <kristo@kernel.org>,
<robh@kernel.org>, <krzk+dt@kernel.org>, <conor+dt@kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: <vishalm@ti.com>
Subject: Re: [PATCH v5 1/4] arm64: dts: ti: k3-am62p5-sk: Remove the unused cfg in USB1_DRVVBUS
Date: Tue, 9 Sep 2025 07:54:02 +0530 [thread overview]
Message-ID: <62f0c51c-3c04-4735-93c6-84766cf0e2a5@ti.com> (raw)
In-Reply-To: <5f5d78e2-5aec-4412-b900-3281c391a444@ti.com>
Hi Kendall,
On 09/09/25 02:51, Kendall Willis wrote:
> On 9/5/25 00:14, Akashdeep Kaur wrote:
>> After the SoC has entered the DeepSleep low power mode, USB1 can be used
>> to wakeup the SoC based on USB events triggered by USB devices. This
>> requires that the pin corresponding to the Type-A connector remains
>> pulled
>> up even after the SoC has entered the DeepSleep low power mode.
>> For that, either DeepSleep pullup configuration can be selected or the
>> pin
>> can have the same configuration that it had when SoC was in active mode.
>> But, in order for DeepSleep configuration to take effect, the DeepSleep
>> control bit has to be enabled.
>
> The last sentence wording is confusing because it sounds like a
> DeepSleep control bit still needs to be enabled which is not seen in the
> patch. If possible, drop this sentence and do the same for the other
> similar patch in this series.
Sounds good! Removed.
Regards,
Akashdeep Kaur
>
>> Remove the unnecessary DeepSleep state configuration from USB1_DRVBUS
>> pin,
>> as the DeepSleep control bit is not set and the active configuration is
>> sufficient to keep the pin pulled up. This simplifies the setup and
>> removes
>> redundant configuration.
>>
>> This reverts commit 115290c112952db27009668aa7ae2f29920704f0.
>>
>> Reviewed-by: Dhruva Gole <d-gole@ti.com>
>> Signed-off-by: Akashdeep Kaur <a-kaur@ti.com>
>
> Verified USB disconnect, USB connect, and USB remote wakeup on AM62P SKEVM.
>
> Tested-by: Kendall Willis <k-willis@ti.com>
>
>> ---
>> arch/arm64/boot/dts/ti/k3-am62p5-sk.dts | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/arch/arm64/boot/dts/ti/k3-am62p5-sk.dts b/arch/arm64/
>> boot/dts/ti/k3-am62p5-sk.dts
>> index 899da7896563..e8f0ac2c55e2 100644
>> --- a/arch/arm64/boot/dts/ti/k3-am62p5-sk.dts
>> +++ b/arch/arm64/boot/dts/ti/k3-am62p5-sk.dts
>> @@ -360,7 +360,7 @@ AM62PX_IOPAD(0x01b0, PIN_OUTPUT, 2) /* (G20)
>> MCASP0_ACLKR.UART1_TXD */
>> main_usb1_pins_default: main-usb1-default-pins {
>> pinctrl-single,pins = <
>> - AM62PX_IOPAD(0x0258, PIN_INPUT | PIN_DS_PULLUD_ENABLE |
>> PIN_DS_PULL_UP, 0) /* (G21) USB1_DRVVBUS */
>> + AM62PX_IOPAD(0x0258, PIN_INPUT, 0) /* (G21) USB1_DRVVBUS */
>> >;
>> };
>
next prev parent reply other threads:[~2025-09-09 6:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-05 5:14 [PATCH v5 0/4] Remove unused bits from dts and add support for remaining pinctrl macros Akashdeep Kaur
2025-09-05 5:14 ` [PATCH v5 1/4] arm64: dts: ti: k3-am62p5-sk: Remove the unused cfg in USB1_DRVVBUS Akashdeep Kaur
2025-09-08 21:21 ` Kendall Willis
2025-09-09 2:24 ` Akashdeep Kaur [this message]
2025-09-05 5:14 ` [PATCH v5 2/4] arm64: dts: ti: k3-am62x-sk-common: " Akashdeep Kaur
2025-09-08 21:40 ` Kendall Willis
2025-09-05 5:14 ` [PATCH v5 3/4] arm64: dts: ti: k3-pinctrl: Add the remaining macros Akashdeep Kaur
2025-09-05 6:16 ` Dhruva Gole
2025-09-08 23:34 ` Kendall Willis
2025-09-09 2:36 ` Akashdeep Kaur
2025-09-05 5:14 ` [PATCH v5 4/4] arm64: dts: ti: k3-pinctrl: Fix the bug in existing macros Akashdeep Kaur
2025-09-05 6:21 ` Dhruva Gole
2025-09-08 23:35 ` Kendall Willis
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=62f0c51c-3c04-4735-93c6-84766cf0e2a5@ti.com \
--to=a-kaur@ti.com \
--cc=afd@ti.com \
--cc=conor+dt@kernel.org \
--cc=d-gole@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=k-willis@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=praneeth@ti.com \
--cc=robh@kernel.org \
--cc=sebin.francis@ti.com \
--cc=u-kumar1@ti.com \
--cc=vigneshr@ti.com \
--cc=vishalm@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