linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mathias Nyman <mathias.nyman@linux.intel.com>
To: Udipto Goswami <quic_ugoswami@quicinc.com>,
	Pavan Kondeti <quic_pkondeti@quicinc.com>
Cc: s.shtylyov@omp.ru, linux-usb@vger.kernel.org
Subject: Re: [RFT PATCH] xhci: make xhci_handshake timeout for xhci_reset() adjustable
Date: Mon, 28 Feb 2022 13:39:10 +0200	[thread overview]
Message-ID: <27f7aec3-cd86-3f55-dfa6-8f2b76437c90@linux.intel.com> (raw)
In-Reply-To: <0edc0822-d75b-238a-16d4-d828710c1b60@quicinc.com>

On 24.2.2022 10.44, Udipto Goswami wrote:
> Hi Pavan, Mathias,
> 
> we have tested the patch in the testing environment where initially we were hitting the issue. We don't see any issue after including this.
> 
> On 18-02-2022 03:11 pm, Pavan Kondeti wrote:
>> On Thu, Feb 17, 2022 at 03:56:43PM +0200, Mathias Nyman wrote:
>>> xhci_reset() timeout was increased from 250ms to 10 seconds in order to
>>> give Renesas 720201 xHC enough time to get ready in probe.
>>>
>>> xhci_reset() is called with interrupts disabled in other places, and
>>> waiting for 10 seconds there is not acceptable.
>>>
>>> Add a timeout parameter to xhci_reset(), and adjust it back to 250ms
>>> when called from xhci_stop() or xhci_shutdown() where interrupts are
>>> disabled, and successful reset isn't that critical.
>>>
>>> Additionally change the signed integer timeout parameter in
>>> xhci_handshake() to a u64 to match the timeout value we pass to
>>> readl_poll_timeout_atomic()
>>>
>>> Reported-by: Sergey Shtylyov <s.shtylyov@omp.ru>
>>> Reported-by: Pavan Kondeti <quic_pkondeti@quicinc.com>
>>> Fixes: 22ceac191211 ("xhci: Increase reset timeout for Renesas 720201 host.")
>>> Signed-off-by: Mathias Nyman <mathias.nyman@linux.intel.com>
>> We have tested the patch and found no issues. Since the issue happens
>> very rarely, we have included in our builds for the wider testing.
>>
>> Thanks,
>> Pavan

Thanks 
Can I add a "Tested-by: Pavan Kondeti <quic_pkondeti@quicinc.com>" tag?

-Mathias

  reply	other threads:[~2022-02-28 11:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-17 13:56 [RFT PATCH] xhci: make xhci_handshake timeout for xhci_reset() adjustable Mathias Nyman
2022-02-18  9:41 ` Pavan Kondeti
2022-02-24  8:44   ` Udipto Goswami
2022-02-28 11:39     ` Mathias Nyman [this message]
2022-02-28 12:10       ` Pavan Kondeti
2022-03-01  1:49 ` Jack Pham
2022-03-01  4:03   ` Pavan Kondeti
2022-03-01  8:47     ` Mathias Nyman
2022-03-02  3:23       ` Pavan Kondeti
2022-03-02  7:49         ` Greg Kroah-Hartman
2022-03-02  7:57           ` Pavan Kondeti

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=27f7aec3-cd86-3f55-dfa6-8f2b76437c90@linux.intel.com \
    --to=mathias.nyman@linux.intel.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=quic_pkondeti@quicinc.com \
    --cc=quic_ugoswami@quicinc.com \
    --cc=s.shtylyov@omp.ru \
    /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;
as well as URLs for NNTP newsgroup(s).