Linux USB
 help / color / mirror / Atom feed
From: Jason Sun <jason.sun689@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
	sunqian@senarytech.com, jason.sun689@gmail.com
Subject: Re: [PATCH v2] dwc2: Delay resume until device connection is stable
Date: Wed, 24 Dec 2025 20:51:28 +0800	[thread overview]
Message-ID: <20251224125128.dwiahkuwbpmfiugb@e45ae8f13cb0> (raw)
In-Reply-To: <2025122444-handcraft-hammock-c020@gregkh>

On Wed, Dec 24, 2025 at 09:40:03AM +0100, Greg KH wrote:
>On Wed, Dec 24, 2025 at 04:20:13PM +0800, Jason Sun wrote:
>> Tested on:
>>   - Kernel: v5.15.140
>
>That's a very old kernel version.  How about 6.18?
>
>thanks,
>
>greg k-h

Hi Greg,

Sorry for the formatting issues in my previous email.

Thanks for the feedback.

At the moment I only have access to this board on a 5.15-based BSP,
so I can only run-time test on v5.15.140. I don't currently have a
working mainline (v6.x) boot chain for this hardware.

The patch applies cleanly and builds on the current usb.git tree
(v6.15-based, build-tested only). The change is based on reviewing
the resume path around VBUS enable, which still proceeds after a fixed
usleep_range(3000, 5000) delay and can observe an unstable CONNSTS
window on our setup.

Please let me know if build-tested on usb.git is acceptable for now,
or if you'd prefer the change to be conditional (e.g. via DT or a
module parameter).

Thanks,
Jason Sun

      parent reply	other threads:[~2025-12-24 12:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-15 12:53 [PATCH 1/1] dwc2: Delay resume until device connection is stable sunqian
2025-12-23 14:29 ` Greg KH
2025-12-24  8:20 ` [PATCH v2] " Jason Sun
2025-12-24  8:39   ` Greg KH
2025-12-24  8:40   ` Greg KH
2025-12-24 11:06     ` Jason Sun
2025-12-24 12:51     ` Jason Sun [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=20251224125128.dwiahkuwbpmfiugb@e45ae8f13cb0 \
    --to=jason.sun689@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=sunqian@senarytech.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