From: Antti Palosaari <crope@iki.fi>
To: linux-media@vger.kernel.org
Subject: Re: [PATCH] rtl28xxu: fix control message flaws
Date: Thu, 15 Oct 2015 09:54:29 +0300 [thread overview]
Message-ID: <561F4DA5.2040806@iki.fi> (raw)
In-Reply-To: <20151014221124.GA31954@minime.bse>
On 10/15/2015 01:11 AM, Daniel Glöckner wrote:
> On Sat, Oct 10, 2015 at 07:45:30PM +0300, Antti Palosaari wrote:
>> Add lock to prevent concurrent access for control message as control
>> message function uses shared buffer. Without the lock there may be
>> remote control polling which messes the buffer causing IO errors.
>
> This patch fixes the Problems I had with my Astrometa stick's I2C bus
> locking up at the end of each dvbv5-scan run until it is disconnected.
> There is another source of IO errors in the current driver, though.
> The delayed work closing the I2C gate to the tuner is often executed
> after rtl2832_power_ctrl has disabled the PLL. This will cause the
> USB transfer accessing the gate control register to fail with -EPIPE.
I saw that few times too, but it does not cause any other harm than
error printing. It went away when canceled that delayed gate closing
timer during demod sleep. But that was device which doesn't have slave
demod at all, so it does not apply to your case as integrated demod
sleep is not called at all. I think some callback which does opposite
than "enable_slave_ts()" is needed. Like "disable_slave_ts()" which
kills that timer before demod is powered off.
regards
Antti
--
http://palosaari.fi/
next prev parent reply other threads:[~2015-10-15 6:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-10 16:45 [PATCH] rtl28xxu: fix control message flaws Antti Palosaari
2015-10-14 22:11 ` Daniel Glöckner
2015-10-15 6:54 ` Antti Palosaari [this message]
2015-11-06 23:15 ` Benjamin Larsson
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=561F4DA5.2040806@iki.fi \
--to=crope@iki.fi \
--cc=linux-media@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).