From: Antti Palosaari <crope@iki.fi>
To: Malcolm Priestley <tvboxspy@gmail.com>
Cc: linux-media@vger.kernel.org
Subject: Re: [PATCH 5/7] af9015 usb bus repeater.
Date: Sat, 12 Nov 2011 18:54:05 +0200 [thread overview]
Message-ID: <4EBEA4AD.4070906@iki.fi> (raw)
In-Reply-To: <4ebe9728.4dc6e30a.47c5.ffff8fc3@mx.google.com>
On 11/12/2011 05:56 PM, Malcolm Priestley wrote:
> This a bus repeater for af9015 devices. Commands usually fail because of other
> activity on the usb bus.
>
> Afatech drivers can repeat up to ten times on the usb bus.
>
> bulk failures that report -ETIMEDOUT or -EBUSY are repeated. If the device fails
> it usually return 0x55 in the first byte.
>
> I am working on a patch to move parts of this to the dvb-usb common area to
> be used by other drivers.
Repeating does not help for those I2C errors. I have already tested it.
IIRC 01 and 02 was the error codes returned in case of I2C read / write.
Which command gives 0x55 for failing?
And generally only very first command will fail. There is already repeat
for that. Generally I think it is good idea to add some repeating, since
it is needed. But it does not make much sense to repeat for those common
I2C errors since it does not matter - you can repeat forever it still
fails. So first need to fix main error source.
And it is indeed good idea to generalize it, but I think it is possible
only for error situations when error is returned by platform call.
1. general repeat for platform calls
2. repeat for firmware command fail (is there need?)
regards
Antti
--
http://palosaari.fi/
prev parent reply other threads:[~2011-11-12 16:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-12 15:56 [PATCH 5/7] af9015 usb bus repeater Malcolm Priestley
2011-11-12 16:54 ` Antti Palosaari [this message]
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=4EBEA4AD.4070906@iki.fi \
--to=crope@iki.fi \
--cc=linux-media@vger.kernel.org \
--cc=tvboxspy@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