From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Greg KH <greg@kroah.com>
Cc: Ezequiel Garcia <elezegarcia@gmail.com>,
linux-media <linux-media@vger.kernel.org>,
michael hartup <michael.hartup@gmail.com>,
linux-rpi-kernel@lists.infradead.org
Subject: Re: Regarding bulk transfers on stk1160
Date: Tue, 13 Nov 2012 13:29:16 -0200 [thread overview]
Message-ID: <20121113132916.5d9fd72f@redhat.com> (raw)
In-Reply-To: <20121113145809.GA15029@kroah.com>
Em Tue, 13 Nov 2012 06:58:09 -0800
Greg KH <greg@kroah.com> escreveu:
> On Tue, Nov 13, 2012 at 10:56:48AM -0300, Ezequiel Garcia wrote:
> > Hello,
> >
> > A user (Michael Hartup in Cc) wants to use stk1160 on low power, low
> > cost devices (like raspberrypi).
> >
> > At the moment raspberrypi can't stream using isoc urbs due to problems
> > with usb host driver (dwc-otg)
> > preventing it from achieving the required throughput.
> > For instance, on my rpi setup I can stream (using dd) at 16MB/s; but
> > at least 20 MB/s are required.
> >
> > Having read that bulk transfers may work better with rpi usb driver, I
> > decided to try to implement
> > those at stk1160. However, I later discovered stk1160 doesn't have any
> > bulk endpoint (see lsusb below).
> > (I'm no expert, but I assume lack of bulk endpoint means I can't use
> > bulk urbs, right?).
Typically, a media device either uses isoc or bulk transfer. When the device
has both, one transfer type is generally used by analog and the other one
for digital. So, it is not a driver's choice; it is up to the a hardware's
manufacturer to decide it.
> Correct, you need to fix the rpi host controller driver in order to make
> this work properly. Please push back on the developers of that hardware
> so we can get the specs to write a proper driver for it.
>
> Or better yet, buy a board with a working USB port, like a BeagleBone or
> the like :)
>
> Sorry, there's really nothing we can do here,
I fully agree with Greg: if the rpi host controller is broken, there's nothing
we can do at media driver.
Either put pressure at the hardware manufacturer for the fix to happen,
or just return it back to it and use another hardware.
Regards,
Mauro
next prev parent reply other threads:[~2012-11-13 15:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-13 13:56 Regarding bulk transfers on stk1160 Ezequiel Garcia
2012-11-13 14:05 ` Gordon Hollingworth
2012-11-13 15:15 ` Ezequiel Garcia
2012-11-13 14:58 ` Greg KH
2012-11-13 15:29 ` Mauro Carvalho Chehab [this message]
2012-11-14 22:53 ` Ezequiel Garcia
2012-11-14 23:18 ` Michael Hartup
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=20121113132916.5d9fd72f@redhat.com \
--to=mchehab@redhat.com \
--cc=elezegarcia@gmail.com \
--cc=greg@kroah.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=michael.hartup@gmail.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