public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Sean Young <sean@mess.org>
To: Mauro Carvalho Chehab <m.chehab@samsung.com>
Cc: Jarod Wilson <jarod@redhat.com>,
	Martin Kittel <linux@martin-kittel.de>,
	linux-media@vger.kernel.org
Subject: Re: Patch mceusb: fix invalid urb interval
Date: Tue, 4 Nov 2014 21:25:49 +0000	[thread overview]
Message-ID: <20141104212548.GA1508@gofer.mess.org> (raw)
In-Reply-To: <20141103144945.00288499.m.chehab@samsung.com>

On Mon, Nov 03, 2014 at 02:49:45PM -0200, Mauro Carvalho Chehab wrote:
> Em Mon, 20 Jan 2014 12:36:26 -0500
> Jarod Wilson <jarod@redhat.com> escreveu:
> 
> > On Sun, Jan 19, 2014 at 09:56:48PM +0000, Sean Young wrote:
> > > On Sun, Jan 19, 2014 at 10:05:15PM +0100, Martin Kittel wrote:
> > > > Hi Mauro, hi Sean,
> > ...
> > > > >From a71676dad29adef9cafb08598e693ec308ba2e95 Mon Sep 17 00:00:00 2001
> > > > From: Martin Kittel <linux@martin-kittel.de>
> > > > Date: Sun, 19 Jan 2014 21:24:55 +0100
> > > > Subject: [PATCH] mceusb: use endpoint xfer mode as advertised
> > > > 
> > > > mceusb always sets endpoints to interrupt transfer mode no matter
> > > > what the device itself is advertising. This causes trouble on xhci
> > > > hubs. This patch changes the behavior to honor the device endpoint
> > > > settings.
> > > 
> > > This patch is wrong. I get:
> > > 
> > > [   60.962727] ------------[ cut here ]------------
> > > [   60.962729] WARNING: CPU: 0 PID: 0 at drivers/usb/core/urb.c:452 usb_submit_u
> > > rb+0x1fd/0x5b0()
> > > [   60.962730] usb 3-2: BOGUS urb xfer, pipe 1 != type 3
> > > 
> > > This is because the patch no longer sets the endpoints to interrupt
> > > endpoints, but still uses the interrupt functions like
> > > usb_fill_int_urb().
> > 
> > Crap, I sent a working patch to everyone a few days ago, but from a new
> > host that didn't have relay stuff set up yet, so I don't think anyone got
> > the message. Oops... I'll try to dig it back up. Its a quick fix, but its
> > tested as fully functional on multiple devices here, including a mix of
> > ones that claim bulk and interrupt, ones with no bInterval, ones with
> > different non-0 bIntervals, etc.
> 
> Hi All,
> 
> This is still pending on my queue. Any news?

I'm pretty sure the proper fix for this problem has been merged already:

commit 0cacb46ace1f433f0ab02af10686f6dc50b5d268
Author: Matt DeVillier <matt.devillier@gmail.com>
Date:   Thu Apr 24 11:16:31 2014 -0300

    [media] fix mceusb endpoint type identification/handling


Sean

  reply	other threads:[~2014-11-04 21:25 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-10 10:50 Patch mceusb: fix invalid urb interval Martin Kittel
2013-12-10 16:20 ` Mauro Carvalho Chehab
2013-12-11 13:17 ` Sean Young
2013-12-11 20:34   ` Martin Kittel
2014-01-15 15:49     ` Mauro Carvalho Chehab
2014-01-15 16:52       ` Sean Young
2014-01-15 17:59         ` Mauro Carvalho Chehab
2014-01-19 21:05           ` Martin Kittel
2014-01-19 21:56             ` Sean Young
2014-01-20 17:36               ` Jarod Wilson
2014-11-03 16:49                 ` Mauro Carvalho Chehab
2014-11-04 21:25                   ` Sean Young [this message]
2014-11-04 22:39                     ` Mauro Carvalho Chehab
2014-01-16  2:55         ` Jarod Wilson
2014-01-20 21:29           ` Sean Young

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=20141104212548.GA1508@gofer.mess.org \
    --to=sean@mess.org \
    --cc=jarod@redhat.com \
    --cc=linux-media@vger.kernel.org \
    --cc=linux@martin-kittel.de \
    --cc=m.chehab@samsung.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