From: Alan Stern <stern@rowland.harvard.edu>
To: Mathias Nyman <mathias.nyman@linux.intel.com>
Cc: Kishon Vijay Abraham I <kishon@ti.com>,
Mathias Nyman <mathias.nyman@intel.com>,
linux-usb@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Lokesh Vutla <lokeshvutla@ti.com>
Subject: Re: [QUERY] Cold plugged USB device to Inateck PCIE USB card is not detected
Date: Thu, 19 Aug 2021 11:09:46 -0400 [thread overview]
Message-ID: <20210819150946.GC228422@rowland.harvard.edu> (raw)
In-Reply-To: <970f741a-54ee-0fa7-46d9-51f77764c6bb@linux.intel.com>
On Thu, Aug 19, 2021 at 04:18:12PM +0300, Mathias Nyman wrote:
> On 19.8.2021 10.54, Kishon Vijay Abraham I wrote:
> > Hi All,
> >
> > I was trying to test PCIe USB card (Inateck) connected to AM64 EVM and
> > J7200 EVM. Inateck uses Renesas uPD720201 USB3 host controller.
> >
> > So if I connect USB pendrive and then boot the board (cold plug), I
> > don't see the pendrive getting detected. But if I remove and plug it
> > again, it gets detected.
> >
> > For the cold plug case, I see this message
> > "usb usb1-port3: couldn't allocate usb_device"
> >
> > It actually fails in
> > xhci_alloc_dev()->xhci_queue_slot_control()->queue_command()->XHCI_STATE_HALTED
> >
> > I'm not familiar with xhci but it looks like port event is invoked
> > before the controller is fully initialized (?).
>
> Maybe this controller is capable of generating interrupts before it's running?
Mathias and Kishon:
Note that this issue has also been reported in Bugzilla:
https://bugzilla.kernel.org/show_bug.cgi?id=214021
Alan Stern
next prev parent reply other threads:[~2021-08-19 15:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-19 7:54 [QUERY] Cold plugged USB device to Inateck PCIE USB card is not detected Kishon Vijay Abraham I
2021-08-19 13:18 ` Mathias Nyman
2021-08-19 15:09 ` Alan Stern [this message]
2021-08-20 8:26 ` Mathias Nyman
2021-08-20 12:18 ` Kishon Vijay Abraham I
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=20210819150946.GC228422@rowland.harvard.edu \
--to=stern@rowland.harvard.edu \
--cc=gregkh@linuxfoundation.org \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=lokeshvutla@ti.com \
--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).