[<prev] [next>] [day] [month] [year] [list]
Message-ID: <CANqn-rhFH+RivRdiGtdFpjFKEpsJ497Z-NrtJ+naSHE+gJrzMg@mail.gmail.com>
Date: Thu, 9 Feb 2023 21:02:58 +0800
From: Albert Wang <albertccwang@...gle.com>
To: Wesley Cheng <quic_wcheng@...cinc.com>
Cc: Thinh.Nguyen@...opsys.com, agross@...nel.org,
alsa-devel@...a-project.org, andersson@...nel.org,
bgoswami@...cinc.com, broonie@...nel.org,
devicetree@...r.kernel.org, Greg KH <gregkh@...uxfoundation.org>,
krzysztof.kozlowski+dt@...aro.org, lgirdwood@...il.com,
linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-usb@...r.kernel.org, mathias.nyman@...el.com, perex@...ex.cz,
Jack Pham <quic_jackp@...cinc.com>, quic_plai@...cinc.com,
robh+dt@...nel.org, srinivas.kandagatla@...aro.org, tiwai@...e.com
Subject: Re: [RFC PATCH v2 05/22] usb: xhci: Add XHCI APIs to support USB offloading
Hi Wesley,
It looks like I can get the transfer ring address by calling
xhci_get_xfer_resource,
and the xhci_get_ir_resource() is called to get access to the new structure
"xhci_interrupter" for the event ring address. From code review, I can
say these
APIs allow us to get the information we need.
Of course, we will integrate this patchset to verify if compatible
with our design.
Thanks,
Albert
Powered by blists - more mailing lists