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: Mon, 9 Feb 2015 23:21:45 +0000	[thread overview]
Message-ID: <66A26A9AA227D947AF088537F041526E224CCB@VSVR-EX10-MB1.pocatec.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1501061316030.1602-100000@iolanthe.rowland.org>


> > > > > > That is interresting, however, I have an older kernel running=20
> > > > > > an OHCI driver which is able to handle 4 codecs. Same usb=20
> > > > > > hardware (codecs and hub), but older kernel on a different=20
> > > > > > CPU, with much less power. This makes me believe that there's a=
 solution to make it work...
> > > > >=20
> > > > > Of course there is: Install an OHCI host controller and use it to=
 drive your codecs.  It should work fine.
> >=20
> > What do you mean by that? The host controller is embedded in the i.MX C=
PU...
> > Changing the CPU is not really an option to me. Unless I am missing=20
> > something?
>
> I didn't realize you were talking about an i.MX-based system.  On a compu=
ter with a free PCI slot, it's easy to add an OHCI controller. =20
> iMX isn't as accomodating.
>
> 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

Okay; I did my homeworks. We've loaded kernel V3.16 (Oct 14th, 2015) on an =
i.MX51 plattform and the problem is still there. Unless an important change=
 occured in V3.19, it appears that the latest kernel is not the solution fo=
r us. So we're still not able to use 4 codecs on our i.MX plattform.

So just to make things clearer:
- We have customers waiting for a solution with that hardware (this hardwar=
e is already delivred AND used);
- We have important comittments and severe penalties ($$$) if we're not abl=
e to deliver on time (due for March 15th);
- We've already looked at a hardware solution, which corresponds to replace=
 current units ($$$$$), so that is not really an option for us;

So as a last resort, I'm wondering, where is the USB expert who could help =
us solving our problem? Any suggestions?

If we are to get into debugging the USB driver, we would do it with the cur=
rent kernel used (V2.6.31). What are the better tools to get into that? I g=
uess a USB analyzer (hardware) would be the smart thing? Any brand name to =
suggest?

Any other ideas for a solution will be really appreciated.

Regards,
Michael Tessier.

  parent reply	other threads:[~2015-02-09 23: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
2015-02-09 23:21               ` Michael Tessier [this message]
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=66A26A9AA227D947AF088537F041526E224CCB@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.