From: Gerd Hoffmann <kraxel@redhat.com>
To: hikarupsp@gmail.com
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] xhci: Add No Op Command
Date: Wed, 14 Aug 2019 14:13:00 +0200 [thread overview]
Message-ID: <20190814121300.jft2mepwxydfxf5s@sirius.home.kraxel.org> (raw)
In-Reply-To: <20190720060427.50457-1-hikarupsp@gmail.com>
On Sat, Jul 20, 2019 at 03:04:27PM +0900, hikarupsp@gmail.com wrote:
> From: Hikaru Nishida <hikarupsp@gmail.com>
>
> This commit adds No Op Command (23) to xHC for verifying the operation
> of the Command Ring mechanisms.
> No Op Command is defined in XHCI spec (4.6.2) and just reports Command
> Completion Event with Completion Code == Success.
> Before this commit, No Op Command is not implemented so xHC reports
> Command Completion Event with Completion Code == TRB Error. This commit
> fixes this behaviour to report Completion Code correctly.
>
> Signed-off-by: Hikaru Nishida <hikarupsp@gmail.com>
Added to usb patch queue.
thanks,
Gerd
prev parent reply other threads:[~2019-08-14 12:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-20 6:04 [Qemu-devel] [PATCH] xhci: Add No Op Command hikarupsp
2019-08-05 15:38 ` Hikaru Nishida
2019-08-13 7:48 ` Hikaru Nishida
2019-08-14 12:13 ` Gerd Hoffmann [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=20190814121300.jft2mepwxydfxf5s@sirius.home.kraxel.org \
--to=kraxel@redhat.com \
--cc=hikarupsp@gmail.com \
--cc=qemu-devel@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).