All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Tessier <michael.tessier@axiontech.ca>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: "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: Tue, 6 Jan 2015 17:38:29 +0000	[thread overview]
Message-ID: <66A26A9AA227D947AF088537F041526E2009E5@VSVR-EX10-MB1.pocatec.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1501061144320.1602-100000@iolanthe.rowland.org>

> > > > That is interresting, however, I have an older kernel running an=20
> > > > OHCI driver which is able to handle 4 codecs. Same usb hardware=20
> > > > (codecs and hub), but older kernel on a different CPU, with much=20
> > > > less power. This makes me believe that there's a solution to make i=
t work...
> > >=20
> > > Of course there is: Install an OHCI host controller and use it to dri=
ve 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?

> > >=20
> > > The periodic scheduling algorithm for OHCI is very different from the=
 algorithm for EHCI.
> >=20
> > According to your knowledge, how much time would you think it takes to=
=20
> > change the EHCI driver with an OHCI one?
>
> I don't understand the question.
>
> >  And can you tell if the OHCI driver
> > will work on my hardware given that the Host controller of the i.MX512=
=20
> > is a USB2.0 host controller? (OHCI was implemented for USB 1.x from=20
> > what I
> > understand)
>
> The OHCI driver works with OHCI hardware and the EHCI driver works with E=
HCI hardware.  OHCI is USB-1.1 and EHCI is USB-2.  They are not interchange=
able.

That was what I thought first...

>
> > I tried to do so several days ago with the built-in configurator (I am=
=20
> > using "ltib"), but the configurator does not allow selecting the OHCI=20
> > driver; I tried manually but it turned into compiler errors...
>
> It looks like the configurator is smart; it won't let you select the wron=
g driver for your hardware.
>
> Alan Stern

  reply	other threads:[~2015-01-06 17:38 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 [this message]
2015-01-06 18:22             ` Alan Stern
2015-01-09  7:20               ` Peter Chen
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=66A26A9AA227D947AF088537F041526E2009E5@VSVR-EX10-MB1.pocatec.com \
    --to=michael.tessier@axiontech.ca \
    --cc=linux-usb@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.