All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lukas Wunner <lukas@wunner.de>
To: Mathias Nyman <mathias.nyman@intel.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-usb@vger.kernel.org,
	Jonathan Bell <jonathan@raspberrypi.org>,
	Phil Elwell <phil@raspberrypi.com>,
	Nicolas Saenz Julienne <nsaenz@kernel.org>,
	Stefan Wahren <stefan.wahren@i2se.com>,
	Philipp Rosenberger <p.rosenberger@kunbus.com>,
	Lino Sanfilippo <LinoSanfilippo@gmx.de>
Subject: [PATCH 0/2] Multi-segment Event Ring support for XHCI
Date: Tue, 15 Aug 2023 14:40:37 +0200	[thread overview]
Message-ID: <cover.1692085657.git.lukas@wunner.de> (raw)

Enlarge the XHCI Event Ring to cope with high load situations
by allowing more than one segment (patch [2/2]).  The patch is
lifted from the Raspberry Pi kernel, it has been in use there
for 4 years.  I've taken the liberty to slightly edit the commit
message and the patch itself for upstream.

As a prerequisite for the patch, ensure that the DESI bits in the
ERDP register are set correctly (patch [1/2]).  Incorrect DESI bits
cause an interrupt storm on Renesas uPD720201 host controllers.

Jonathan Bell (1):
  xhci: Use more than one Event Ring segment

Lukas Wunner (1):
  xhci: Set DESI bits in ERDP register correctly

 drivers/usb/host/xhci-mem.c  | 35 ++++++++++++++++++-----------------
 drivers/usb/host/xhci-ring.c |  2 +-
 drivers/usb/host/xhci.h      |  6 ++++--
 3 files changed, 23 insertions(+), 20 deletions(-)

-- 
2.39.2


             reply	other threads:[~2023-08-15 12:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-15 12:40 Lukas Wunner [this message]
2023-08-15 12:40 ` [PATCH 1/2] xhci: Set DESI bits in ERDP register correctly Lukas Wunner
2023-08-17 13:26   ` Mathias Nyman
2023-08-15 12:40 ` [PATCH 2/2] xhci: Use more than one Event Ring segment Lukas Wunner
2023-08-17 13:46   ` Mathias Nyman

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=cover.1692085657.git.lukas@wunner.de \
    --to=lukas@wunner.de \
    --cc=LinoSanfilippo@gmx.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=jonathan@raspberrypi.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mathias.nyman@intel.com \
    --cc=nsaenz@kernel.org \
    --cc=p.rosenberger@kunbus.com \
    --cc=phil@raspberrypi.com \
    --cc=stefan.wahren@i2se.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.