public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: "Bjørn Mork" <bjorn@mork.no>
Cc: stable@vger.kernel.org, Jonathan Bell <jonathan@raspberrypi.org>,
	Mathias Nyman <mathias.nyman@linux.intel.com>
Subject: Re: [PATCH backport for v5.10] xhci: add quirk for host controllers that don't update endpoint DCS
Date: Wed, 20 Oct 2021 14:36:37 +0200	[thread overview]
Message-ID: <YXANVUanKdpnH+Gh@kroah.com> (raw)
In-Reply-To: <20211018170634.5673-1-bjorn@mork.no>

On Mon, Oct 18, 2021 at 07:06:34PM +0200, Bjørn Mork wrote:
> From: Jonathan Bell <jonathan@raspberrypi.org>
> 
> upstream commit 5255660b208a
> 
> Seen on a VLI VL805 PCIe to USB controller. For non-stream endpoints
> at least, if the xHC halts on a particular TRB due to an error then
> the DCS field in the Out Endpoint Context maintained by the hardware
> is not updated with the current cycle state.
> 
> Using the quirk XHCI_EP_CTX_BROKEN_DCS and instead fetch the DCS bit
> from the TRB that the xHC stopped on.
> 
> See: https://github.com/raspberrypi/linux/issues/3060
> 
> Signed-off-by: Jonathan Bell <jonathan@raspberrypi.org>
> Signed-off-by: Bjørn Mork <bjorn@mork.no>
> Cc: Mathias Nyman <mathias.nyman@linux.intel.com>
> ---
> 
> This isn't really a backport.  It's the original patch for 5.10 from
> https://github.com/raspberrypi/linux.git , which was forward ported
> and ended up as upstream commit 5255660b208a
> 
> The XHCI_EP_CTX_BROKEN_DCS constant has been syncronozed with upstream
> to avoid collisions, though.

Now queued up, thanks.

greg k-h

      reply	other threads:[~2021-10-20 12:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-18 17:06 [PATCH backport for v5.10] xhci: add quirk for host controllers that don't update endpoint DCS Bjørn Mork
2021-10-20 12:36 ` Greg KH [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=YXANVUanKdpnH+Gh@kroah.com \
    --to=greg@kroah.com \
    --cc=bjorn@mork.no \
    --cc=jonathan@raspberrypi.org \
    --cc=mathias.nyman@linux.intel.com \
    --cc=stable@vger.kernel.org \
    /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