From: Thinh Nguyen <Thinh.Nguyen@synopsys.com>
To: Ravineet Singh <ravineet.a.singh@est.tech>
Cc: Thinh Nguyen <Thinh.Nguyen@synopsys.com>,
Mike Looijmans <mike.looijmans@topic.nl>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"jura@vukad.in" <jura@vukad.in>,
"malin.jonsson@est.tech" <malin.jonsson@est.tech>
Subject: Re: [PATCH] usb: dwc3: gadget: Inform system of suspended state
Date: Fri, 6 Mar 2026 23:05:00 +0000 [thread overview]
Message-ID: <20260306230452.rfnxcqhy4ehjuubc@synopsys.com> (raw)
In-Reply-To: <jr5jzgvstxr7galevtc7p45q4jx7pk62itv2yki7fw6rlivltz@z6vkp5k5sfj6>
On Fri, Mar 06, 2026, Ravineet Singh wrote:
> Understood, my bad, will send a RFC patch in the future.
>
> Regdumps (without the patch) are attached.
Please no top-post.
This looks like an issue with the integration of the controller and the
phy/connector. Your phy vbus detection logic needs to properly assert
the proper signals (e.g. vbusvalid/powerpresent etc.) on
connection/disconnection detection.
It's best to fix it there. Forcing every U3/L2 transition to be treated
as if it's a disconnection is problematic. If there's a real U3/L2 state
change and then the host resumes, the device and host are out of sync.
I don't see a good workaround for this.
BR,
Thinh
next prev parent reply other threads:[~2026-03-06 23:05 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1b153bce-a66a-45ee-a5c6-963ea6fb1c82.949ef384-8293-46b8-903f-40a477c056ae.c5f44c79-75b2-43c1-a791-806fe8b693cd@emailsignatures365.codetwo.com>
2024-06-03 13:13 ` [PATCH] usb: dwc3: gadget: Inform system of suspended state Mike Looijmans
2024-06-04 1:03 ` Thinh Nguyen
2024-06-04 5:26 ` Mike Looijmans
2024-06-04 6:45 ` Krishna Kurapati PSSNV
2024-06-04 8:25 ` Mike Looijmans
2024-06-04 8:52 ` Krishna Kurapati PSSNV
2024-06-04 23:06 ` Thinh Nguyen
2024-06-05 14:32 ` Mike Looijmans
2024-06-06 0:28 ` Thinh Nguyen
2024-06-06 5:52 ` Mike Looijmans
2024-06-06 15:11 ` Mike Looijmans
2024-06-06 20:21 ` Thinh Nguyen
2024-06-07 6:10 ` Mike Looijmans
2024-06-07 22:57 ` Thinh Nguyen
2024-06-11 4:59 ` Mike Looijmans
2024-06-11 8:02 ` Mike Looijmans
2024-06-13 0:32 ` Thinh Nguyen
2024-06-13 8:51 ` Mike Looijmans
2024-06-17 23:46 ` Thinh Nguyen
2024-06-18 0:26 ` Thinh Nguyen
2024-06-05 14:41 ` Mike Looijmans
2024-06-06 0:29 ` Thinh Nguyen
2026-03-05 9:45 ` Ravineet Singh
2026-03-06 2:06 ` Thinh Nguyen
2026-03-06 12:07 ` Ravineet Singh
2026-03-06 23:05 ` Thinh Nguyen [this message]
2026-03-09 9:52 ` Ravineet Singh
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=20260306230452.rfnxcqhy4ehjuubc@synopsys.com \
--to=thinh.nguyen@synopsys.com \
--cc=gregkh@linuxfoundation.org \
--cc=jura@vukad.in \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=malin.jonsson@est.tech \
--cc=mike.looijmans@topic.nl \
--cc=ravineet.a.singh@est.tech \
/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