LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Chen <hzpeterchen@gmail.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Michael Tessier <michael.tessier@axiontech.ca>,
	"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: Re: PROBLEM: USB isochronous urb leak on EHCI driver
Date: Fri, 9 Jan 2015 15:20:58 +0800	[thread overview]
Message-ID: <CAL411-qA2Q-eTvdKCo-9kY2wHZehas5uRuH-R3bSKRZX67BEoA@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1501061316030.1602-100000@iolanthe.rowland.org>

On Wed, Jan 7, 2015 at 2:22 AM, Alan Stern <stern@rowland.harvard.edu> wrote:
> On Tue, 6 Jan 2015, Michael Tessier wrote:
>
>> > > > > That is interresting, however, I have an older kernel running an
>> > > > > OHCI driver which is able to handle 4 codecs. Same usb hardware
>> > > > > (codecs and hub), but older kernel on a different CPU, with much
>> > > > > less power. This makes me believe that there's a solution to make it work...
>> > > >
>> > > > Of course there is: Install an OHCI host controller and use it to drive your codecs.  It should work fine.
>>
>> What do you mean by that? The host controller is embedded in the i.MX CPU...
>> Changing the CPU is not really an option to me. Unless I am missing
>> something?
>
> I didn't realize you were talking about an i.MX-based system.  On a
> computer with a free PCI slot, it's easy to add an OHCI controller.
> iMX isn't as accomodating.
>

iMX uses chipidea controller which TT is build-in, and it does NOT support
OHCI controller.

> If there's no way to add an extra USB controller to your system then
> the only choice is to upgrade the driver software.
>
> Alan Stern
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-usb" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html



-- 
BR,
Peter Chen

  reply	other threads:[~2015-01-09  7:21 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-15 20:53 PROBLEM: USB isochronous urb leak on EHCI driver Michael Tessier
2014-12-15 21:48 ` Greg KH
2014-12-15 23:13 ` Fabio Estevam
2014-12-17  2:21 ` Peter Chen
2014-12-17 14:06   ` Michael Tessier
2014-12-17 16:40 ` Alan Stern
2015-01-05 15:12   ` Michael Tessier
2015-01-05 16:00     ` Alan Stern
2015-01-06 16:40       ` Michael Tessier
2015-01-06 16:48         ` Alan Stern
2015-01-06 17:38           ` Michael Tessier
2015-01-06 18:22             ` Alan Stern
2015-01-09  7:20               ` Peter Chen [this message]
2015-02-09 23:21               ` Michael Tessier
2015-02-10  2:09                 ` Alan Stern
2015-02-10 15:11                   ` Michael Tessier
2015-02-10 16:01                     ` Alan Stern
2015-01-05 17:28     ` Fabio Estevam
2015-01-06 16:50       ` Michael Tessier

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=CAL411-qA2Q-eTvdKCo-9kY2wHZehas5uRuH-R3bSKRZX67BEoA@mail.gmail.com \
    --to=hzpeterchen@gmail.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=michael.tessier@axiontech.ca \
    --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