All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junjie Cao <junjie.cao@linux.dev>
To: qemu-devel@nongnu.org
Cc: farosas@suse.de, lvivier@redhat.com, pbonzini@redhat.com,
	thuth@redhat.com, peter.maydell@linaro.org, junjie.cao@intel.com
Subject: [PATCH v1 0/7] tests/qtest: Extend USB host controller transfer coverage
Date: Thu, 22 Oct 2026 13:45:54 +0000	[thread overview]
Message-ID: <20261022134601.1207204-1-junjie.cao@linux.dev> (raw)

From: Junjie Cao <junjie.cao@intel.com>

Peter's discussion of isochronous endpoint mismatches highlighted the
lack of tests as a concern for moving the checks into the USB core [1].
This series adds transfer tests motivated by that discussion, without
changing controller or USB core code.

The tests cover EHCI control transfers and isochronous IN/OUT requests
to EP0, UHCI interrupt retries and isochronous completion on NAK, and
successful UHCI/xHCI isochronous OUT transfers to USB audio. The audio
tests configure the device and enable its streaming interface through
EP0 before submitting a packet.

These cases exercise both rejection/retry behavior and successful
isochronous transfers. EHCI isochronous success and USB_RET_ASYNC
completion remain outside the coverage of this series.

Suggestions for other transfer paths to cover in follow-up patches
are welcome.

[1] https://lore.kernel.org/qemu-devel/CAFEAcA8jcNzVT9QuFfog4GZRWt8ZpysKbOy9R-SxmtTrAZ67JQ@mail.gmail.com/

Junjie Cao (7):
  tests/qtest/usb-hcd-ehci: Test a control transfer
  tests/qtest/usb-hcd-ehci: Cover isochronous IN to EP0
  tests/qtest/usb-hcd-ehci: Cover isochronous OUT to EP0
  tests/qtest/usb-hcd-uhci: Test interrupt NAK retries
  tests/qtest/usb-hcd-uhci: Test isochronous NAK completion
  tests/qtest/usb-hcd-uhci: Test a successful isochronous transfer
  tests/qtest/usb-hcd-xhci: Test a successful isochronous transfer

 tests/qtest/usb-hcd-ehci-test.c | 208 +++++++++++++++++++++++++++++
 tests/qtest/usb-hcd-uhci-test.c | 229 ++++++++++++++++++++++++++++++++
 tests/qtest/usb-hcd-xhci-test.c |  95 ++++++++++++-
 3 files changed, 526 insertions(+), 6 deletions(-)


base-commit: ed698be7700160c74d24ef7830adccd2a28d840a
-- 
2.43.0



             reply	other threads:[~2026-10-22 13:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-22 13:45 Junjie Cao [this message]
2026-10-22 13:45 ` [PATCH v1 1/7] tests/qtest/usb-hcd-ehci: Test a control transfer Junjie Cao
2026-10-22 13:45 ` [PATCH v1 2/7] tests/qtest/usb-hcd-ehci: Cover isochronous IN to EP0 Junjie Cao
2026-10-22 13:45 ` [PATCH v1 3/7] tests/qtest/usb-hcd-ehci: Cover isochronous OUT " Junjie Cao
2026-10-22 13:45 ` [PATCH v1 4/7] tests/qtest/usb-hcd-uhci: Test interrupt NAK retries Junjie Cao
2026-10-22 13:45 ` [PATCH v1 5/7] tests/qtest/usb-hcd-uhci: Test isochronous NAK completion Junjie Cao
2026-10-22 13:46 ` [PATCH v1 6/7] tests/qtest/usb-hcd-uhci: Test a successful isochronous transfer Junjie Cao
2026-10-22 13:46 ` [PATCH v1 7/7] tests/qtest/usb-hcd-xhci: " Junjie Cao

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=20261022134601.1207204-1-junjie.cao@linux.dev \
    --to=junjie.cao@linux.dev \
    --cc=farosas@suse.de \
    --cc=junjie.cao@intel.com \
    --cc=lvivier@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.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.