[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <b029c775-a0cf-4991-95b7-a02187c0863b@linux.intel.com>
Date: Wed, 8 Jan 2025 16:10:12 +0200
From: Mathias Nyman <mathias.nyman@...ux.intel.com>
To: Wesley Cheng <quic_wcheng@...cinc.com>, srinivas.kandagatla@...aro.org,
mathias.nyman@...el.com, perex@...ex.cz, conor+dt@...nel.org,
dmitry.torokhov@...il.com, corbet@....net, broonie@...nel.org,
lgirdwood@...il.com, krzk+dt@...nel.org,
pierre-louis.bossart@...ux.intel.com, Thinh.Nguyen@...opsys.com,
tiwai@...e.com, robh@...nel.org, gregkh@...uxfoundation.org
Cc: linux-kernel@...r.kernel.org, devicetree@...r.kernel.org,
linux-sound@...r.kernel.org, linux-input@...r.kernel.org,
linux-usb@...r.kernel.org, linux-arm-msm@...r.kernel.org,
linux-doc@...r.kernel.org
Subject: Re: [PATCH v32 02/32] xhci: sideband: add initial api to register a
secondary interrupter entity
On 8.1.2025 3.21, Wesley Cheng wrote:
> From: Mathias Nyman <mathias.nyman@...ux.intel.com>
>
> Introduce XHCI sec intr, which manages the USB endpoints being requested by
> a client driver. This is used for when client drivers are attempting to
> offload USB endpoints to another entity for handling USB transfers. XHCI
> sec intr will allow for drivers to fetch the required information about the
> transfer ring, so the user can submit transfers independently. Expose the
> required APIs for drivers to register and request for a USB endpoint and to
> manage XHCI secondary interrupters.
The "sec intr" above should also be renamed back to "sideband"
-Mathias
Powered by blists - more mailing lists