From: "mahendra varman" <mahendravarman15@gmail.com>
To: "David Brownell" <david-b@pacbell.net>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: usb detecting only high speed devices only - not detecting low speed devices
Date: Mon, 3 Mar 2008 15:01:00 +0530 [thread overview]
Message-ID: <4ac2955e0803030131t72354cecpbdaf53460ef3d09f@mail.gmail.com> (raw)
In-Reply-To: <200802261817.02830.david-b@pacbell.net>
On Wed, Feb 27, 2008 at 7:47 AM, David Brownell <david-b@pacbell.net> wrote:
> On Tuesday 26 February 2008, Andrew Morton wrote:
> > > usb 3-1: new low speed USB device using ohci_hcd and address 2
> > > ohci_hcd 0000:01:04.1: Unlink after no-IRQ? Controller is probably
> > > using the wrong IRQ.
>
> My diagnosis hasn't changed since last time he asked this question:
> it's related to IRQ handling, outside the scope of USB. If USB
> were getting the OHCI interrupts, it would not issue that message.
>
> Now as to *why* that happens, I don't know. We've certainly had folk
> using Philips/NXP EHCI controllers successfully before. Maybe this
> board has a hardware problem, like a bad chip or not having wired
> up the power lines that OHCI controller uses.
still the low speed devices are giving unlink after no IRQ.. My
hardware engineer says he followed the reference schematics of ISP1562
of philips. He says that ohci side, the power lines are wired up
My Ehci devices can be mounted and the files are read
Today I faced another issue
For some usb ehci devices its giving "device descriptor read/64, error
-71" ( for some usb stick of usb2.0)
but for others i can able to mount without this error.....
Sir, Any clue regarding the above problem iam facing currently ??
Thanks
next prev parent reply other threads:[~2008-03-03 9:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-26 13:43 mahendra varman
2008-02-27 0:05 ` Andrew Morton
2008-02-27 2:17 ` David Brownell
2008-03-03 9:31 ` mahendra varman [this message]
2008-03-03 19:07 ` David Brownell
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=4ac2955e0803030131t72354cecpbdaf53460ef3d09f@mail.gmail.com \
--to=mahendravarman15@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.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
all inboxes | Powered by JetHome®