linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Allen Blaylock <AllenB@epiloglaser.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Manu Gautam <mgautam@codeaurora.org>,
	Peter Chen <peter.chen@nxp.com>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: RE: EHSET with hub and PCIe root hub
Date: Thu, 12 Sep 2019 14:29:41 +0000	[thread overview]
Message-ID: <BYAPR20MB250145E476D5A086285FB8B8CCB00@BYAPR20MB2501.namprd20.prod.outlook.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1909121008160.1440-100000@iolanthe.rowland.org>

Thank you Alan,

I am still working through understanding the usbmon and this is a helpful hint. I will contact the device manufacturer and see if there is some alternative method they recommend for testing.

>Most of the usbmon output shows that a device was attached to port 3 of hub 2 and enumerated as usual over the course of about half a second.
>
>The very last two lines show the computer sending the hub a Set-Port-Test request on port 3 for test mode 4, which is Test Packet.
>The hub's response is a STALL, indicating that the hub doesn't understand or doesn't implement this request.
>
>Alan Stern
>

      parent reply	other threads:[~2019-09-12 14:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-10 22:01 EHSET with hub and PCIe root hub Allen Blaylock
2019-09-11  2:57 ` Peter Chen
2019-09-11  3:54   ` Manu Gautam
2019-09-11 20:34     ` Allen Blaylock
2019-09-12  0:49       ` Peter Chen
2019-09-12 14:20       ` Alan Stern
2019-09-12 14:28         ` Alan Stern
2019-09-12 20:32           ` Allen Blaylock
2019-09-12 20:51             ` Alan Stern
2019-09-16  1:11               ` Peter Chen
2019-09-12 14:29         ` Allen Blaylock [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=BYAPR20MB250145E476D5A086285FB8B8CCB00@BYAPR20MB2501.namprd20.prod.outlook.com \
    --to=allenb@epiloglaser.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=mgautam@codeaurora.org \
    --cc=peter.chen@nxp.com \
    --cc=stern@rowland.harvard.edu \
    /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).