From: Wesley Cheng <wesley.cheng@oss.qualcomm.com>
To: Mathias Nyman <mathias.nyman@linux.intel.com>,
Mathias Nyman <mathias.nyman@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Michal Pecio <michal.pecio@gmail.com>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-sound@vger.kernel.org, 胡连勤 <hulianqin@vivo.com>
Subject: Re: [PATCH v4 0/5] Add larger page size support for USB audio offload path
Date: Thu, 1 Oct 2026 18:42:17 -0700 [thread overview]
Message-ID: <b61c4087-3ccd-409e-8b3d-df75795b014d@oss.qualcomm.com> (raw)
In-Reply-To: <92d80a55-4422-4659-8f2d-e28693d6d9d7@linux.intel.com>
On 10/1/2026 3:33 PM, Mathias Nyman wrote:
> On 10/1/26 01:23, Wesley Cheng wrote:
>>
>> Hi Mathias,
>>
>> Just checking to see if there was anything that we needed to account for
>> in this series? I think there was the discussion that came up here:
>> https://lore.kernel.org/all/
>> TYUPR06MB6217000B59003EDF233D7246D2B22@TYUPR06MB6217.apcprd06.prod.outlook.com/
>
> Patch v4 1/5: Looks good, is useful even as a standalone patch. Can be
> taken immediately.
> Patch v4 2/5: Looks good, not useful as standalone patch, can be taken with
> rest of series.
> Patch v4 3/5: I need to revisit this and look at new dma pool lifetime vs
> xHC accessing those DMA addresses.
> PAtch v4 Rest: ALSA, no opinion.
>
Great, thanks for the inputs.
>>
>> But, I think your suggestion about adding the sideband check in the
>> xhci_setup_device() would mitigate that problem. Esp, if we don't want
>> xHCI core to really know about sideband ops.
>
> That would be the bandaid in:
> https://lore.kernel.org/all/c6c9890f-46d8-42f1-
> a7e7-8a5d551fa22c@linux.intel.com/
>
> I can turn that into a proper patch.
> Lianqin also gave some preliminary positive feedback, but I'm not sure if
> the code was
> ever properly tested.
>
I can chime in a bit here. I did work with Lianqin offline, and I was able
to reproduce the problem (w/ this series included in the codebase), and
your suggestion did work. I provided some feedback to them, so hopefully
they can convey that on the other thread.
Thanks
Wesley Cheng
prev parent reply other threads:[~2026-10-02 1:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-10 1:50 Wesley Cheng
2026-09-10 1:50 ` [PATCH v4 1/5] usb: xhci: sideband: fix ring sg table for sub-page TRB segments Wesley Cheng
2026-09-10 1:50 ` [PATCH v4 2/5] usb: xhci: Allow to specify a different segment pool for allocations Wesley Cheng
2026-09-10 1:50 ` [PATCH v4 3/5] usb: xhci: sideband: allocate sideband ring segments from a dedicated pool Wesley Cheng
2026-09-10 1:51 ` [PATCH v4 4/5] ALSA: usb-audio: qcom: tag sideband endpoints before ring allocation Wesley Cheng
2026-09-10 1:51 ` [PATCH v4 5/5] ALSA: usb-audio: qcom: fix xfer ring IOMMU unmap on 16K+ page kernels Wesley Cheng
2026-09-30 22:23 ` [PATCH v4 0/5] Add larger page size support for USB audio offload path Wesley Cheng
2026-10-01 22:33 ` Mathias Nyman
2026-10-02 1:42 ` Wesley Cheng [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=b61c4087-3ccd-409e-8b3d-df75795b014d@oss.qualcomm.com \
--to=wesley.cheng@oss.qualcomm.com \
--cc=gregkh@linuxfoundation.org \
--cc=hulianqin@vivo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=mathias.nyman@linux.intel.com \
--cc=michal.pecio@gmail.com \
--cc=perex@perex.cz \
--cc=tiwai@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®