From: Peter Chen <hzpeterchen@gmail.com>
To: Mathias Nyman <mathias.nyman@linux.intel.com>
Cc: mathias.nyman@intel.com, linux-usb@vger.kernel.org
Subject: WARN: Success on ctrl setup TRB without IOC set??
Date: Fri, 9 Feb 2018 10:03:36 +0800 [thread overview]
Message-ID: <20180209020335.GA31390@b29397-desktop> (raw)
On Fri, Feb 09, 2018 at 09:59:46AM +0800, Peter Chen wrote:
> On Wed, Feb 07, 2018 at 03:43:23PM +0200, Mathias Nyman wrote:
> > On 07.02.2018 11:45, Peter Chen wrote:
> > >Hi Mathias,
> > >
> > >I am implementing USB2 EHSET SINGLE_STEP_SET_FEATURE Test for XHCI port,
> > >(see ehset_single_step_set_feature for EHCI), it needs to set IOC
> > >for setup packet, and software waits 15 seconds before DATA + STATUS stage.
> > >After porting such design for XHCI, it triggers above warning, and
> > >returns -ESHUTDOWN for URB. Any reasons why we don't allow completion
> > >interrupt for SETUP stage? Thanks.
> > >
> >
> > Current xhci driver control transfer implementation doesn't support
> > queuing a control transfer in parts. we set the IOC only for the status
> > stage, and we always queue a status stage (and possibly data stage) automatically
> > when queuing a control transfer URB.
> >
> > If we get a success event for the SETUP stage the driver will finish the TD and
> > return the whole URB.
> >
> > For testing purposes you would need to make sure we don't call finish_td() for
> > a success event at the SETUP stage, something like this (untested):
> >
> > diff --git a/drivers/usb/host/xhci-ring.c b/drivers/usb/host/xhci-ring.c
> > index c5cbc68..f6d005e 100644
> > --- a/drivers/usb/host/xhci-ring.c
> > +++ b/drivers/usb/host/xhci-ring.c
> > @@ -2014,12 +2014,8 @@ static int process_ctrl_td(struct xhci_hcd *xhci, struct xhci_td *td,
> > switch (trb_comp_code) {
> > case COMP_SUCCESS:
> > - if (trb_type != TRB_STATUS) {
> > - xhci_warn(xhci, "WARN: Success on ctrl %s TRB without IOC set?\n",
> > - (trb_type == TRB_DATA) ? "data" : "setup");
> > - *status = -ESHUTDOWN;
> > - break;
> > - }
> > + if (trb_type == TRB_SETUP)
> > + return 0;
> > *status = 0;
> > break;
> > case COMP_SHORT_PACKET:
> >
>
> Thanks, Mathias. I need to call finish_td since it needs to
> giveback and cleanup URB. And I see below code at process_ctrl_td,
> why we can't call it? In fact, I only see warning message, but
> without any errors for transactions. How about only delete message
> or change debug level as xhci_dbg?
Should be "or change debug message level and *status value as zero."
>
> /* stopped at setup stage, no data transferred */
> if (trb_type == TRB_SETUP)
> goto finish_td;
>
> --
>
next reply other threads:[~2018-02-09 2:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-09 2:03 Peter Chen [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-02-24 2:35 WARN: Success on ctrl setup TRB without IOC set?? Peter Chen
2018-02-09 9:39 Mathias Nyman
2018-02-09 1:59 Peter Chen
2018-02-07 13:43 Mathias Nyman
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=20180209020335.GA31390@b29397-desktop \
--to=hzpeterchen@gmail.com \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=mathias.nyman@linux.intel.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;
as well as URLs for NNTP newsgroup(s).