From: Mauro Carvalho Chehab <mchehab@s-opensource.com>
To: Anders Eriksson <aeriksson2@gmail.com>
Cc: Mauro Carvalho Chehab <mchehab@redhat.com>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>
Subject: Re: em28xx i2c writing error
Date: Sun, 16 Apr 2017 22:55:33 -0300 [thread overview]
Message-ID: <20170416225533.6d83fc6c@vento.lan> (raw)
In-Reply-To: <CAGncdOYtM3PkJWDcBdSdONY8VbP5gDccBO777=j+ARQFXQMJBw@mail.gmail.com>
Em Sat, 15 Apr 2017 20:28:20 +0200
Anders Eriksson <aeriksson2@gmail.com> escreveu:
> Hi Mauro,
>
> I've two devices using this driver, and whenever I have them both in
> use I eventually (between 10K and 100K secs uptime) i2c write errors
> such as in the log below. If only have one of the devices in use, the
> machine is stable.
>
> The machine never recovers from the error.
>
> All help apreciated.
> -Anders
>
>
>
> [ 0.000000] Booting Linux on physical CPU 0xf00
> [ 0.000000] Initializing cgroup subsys cpuset
> [ 0.000000] Initializing cgroup subsys cpu
> [ 0.000000] Initializing cgroup subsys cpuacct
> [ 0.000000] Linux version 4.4.15-v7+ (dc4@dc4-XPS13-9333) (gcc
> version 4.9.3 (crosstool-NG crosstool-ng-1.22.0-88-g8460611) ) #897
> SMP Tue Jul 12 18:42:55 BST 2016
> [ 0.000000] CPU: ARMv7 Processor [410fc075] revision 5 (ARMv7), cr=10c5387d
> [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing
> instruction cache
> [ 0.000000] Machine model: Raspberry Pi 2 Model B Rev 1.1
Hmm.. RPi2... that explains a lot ;)
I've seen similar behaviors on some arm devices with just one device.
That's likely due to some problem with isochronous transfers at the
USB host driver.
The thing is that ISOC transfers are heavily used by USB cameras:
they require that the USB chip would provide a steady throughput
that can eat up to 60% of the USB maximum bitrate, with just one
video stream.
My experience says that several USB drivers can't sustain such
bit rates for a long time.
The RPi tree uses an out-of-tree driver for the USB host driver
(otgdwc - I guess). Upstream uses a different driver (dwc2).
My recent experiences with upstream(dwc2) and USB cameras
is even worse: it doesn't work, if the camera supports only
ISOC frames.
I'll eventually try to fix the upstream driver if I find
spare time for it, but I won't touch at the proprietary
driver that is shipped with the downstream Kernel.
Thanks,
Mauro
next prev parent reply other threads:[~2017-04-17 1:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-15 18:28 em28xx i2c writing error Anders Eriksson
2017-04-16 17:59 ` Frank Schäfer
2017-04-17 18:44 ` Anders Eriksson
2017-04-17 1:55 ` Mauro Carvalho Chehab [this message]
2017-04-18 14:00 ` Anders Eriksson
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=20170416225533.6d83fc6c@vento.lan \
--to=mchehab@s-opensource.com \
--cc=aeriksson2@gmail.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@redhat.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