From: Antti Palosaari <crope@iki.fi>
To: adq <adq@lidskialf.net>
Cc: "Juan Jesús García de Soria Lucena" <skandalfo@gmail.com>,
linux-media@vger.kernel.org
Subject: Re: [patch] Fix AF9015 Dual tuner i2c write failures
Date: Sat, 02 Apr 2011 20:24:06 +0300 [thread overview]
Message-ID: <4D975BB6.1090207@iki.fi> (raw)
In-Reply-To: <BANLkTimW8B=Q=SvsJLsMf-YRJYH-e99zbA@mail.gmail.com>
On 04/02/2011 04:45 PM, adq wrote:
> 2011/4/2 Antti Palosaari<crope@iki.fi>:
>> On 04/02/2011 02:06 PM, adq wrote:
>>>
>>> 2011/4/2 Antti Palosaari<crope@iki.fi>:
>>>>
>>>> On 04/02/2011 04:24 AM, adq wrote:
>>>>>
>>>>> Hi, just been trying it out, with no success. On my test machine, FE0
>>>>> no longer tunes, but FE1 is still fine, so I've just been testing FE0.
>>>>
>>>> You try to say other frontend / tuner is physically dead? Which one?
>>>
>>> No no - I can revive it by simply unplugging and replugging the
>>> device, but I was avoiding doing that to see if we could either track
>>> down something erroneous, or be able to reset it from software.
>>>
>>> It'd be /really/ handy if they'd connected that reset tuner GPIO :(
>>> There isn't a way to completely reset the device from software I take
>>> it? Or any other GPIOs hanging about I could test with?
>>
>> There is few I know, USB command 0x13 boots AF9015 somehow, USB command 0x5a
>> reconnects it from USB bus. But most interesting one is demodulator reset
>> register 0xe205, write 1 to that reg should reset it.
>
> Just tried writing 1 to 0xe205 - no change.
OK.
> Looks like USB commands 0x13/0x5a will be done as part of a normal
> module reload? (In which case it doesn't fix it).
>
> I can actually reboot the machine completely, and the problem stays!
> Only physically unplugging the device sorts it.
You are correct. I don't have any idea anymore. Only is wish to know if
that happens in Windows too.
Antti
--
http://palosaari.fi/
next prev parent reply other threads:[~2011-04-02 17:24 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-04 21:37 [patch] Fix AF9015 Dual tuner i2c write failures Andrew de Quincey
2011-03-04 22:13 ` Antti Palosaari
2011-03-04 22:44 ` Andrew de Quincey
2011-03-04 22:59 ` Antti Palosaari
2011-03-04 23:11 ` Andrew de Quincey
2011-03-05 1:43 ` adq
2011-03-05 1:51 ` adq
2011-03-05 9:56 ` Antti Palosaari
[not found] ` <AANLkTi=YMtTbgwxNA1O6zp03OoeGKJvn8oYDB9kHjti1@mail.gmail.com>
2011-03-05 9:23 ` Antti Palosaari
2011-03-05 11:56 ` Andrew de Quincey
2011-03-05 11:55 ` adq
2011-03-06 11:56 ` adq
2011-03-06 12:24 ` adq
2011-03-06 13:04 ` Antti Palosaari
2011-03-06 13:08 ` adq
2011-03-06 13:24 ` adq
2011-03-07 18:26 ` adq
2011-03-07 22:12 ` adq
2011-03-18 15:46 ` Antti Palosaari
2011-03-21 20:11 ` adq
2011-04-02 1:24 ` adq
2011-04-02 8:20 ` Antti Palosaari
2011-04-02 11:06 ` adq
2011-04-02 11:15 ` adq
2011-04-02 12:18 ` Antti Palosaari
2011-04-02 13:45 ` adq
2011-04-02 17:24 ` Antti Palosaari [this message]
2011-03-05 10:49 ` Antti Palosaari
2011-03-22 9:00 ` Mauro Carvalho Chehab
2011-03-22 18:26 ` adq
2011-03-22 18:36 ` Mauro Carvalho Chehab
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=4D975BB6.1090207@iki.fi \
--to=crope@iki.fi \
--cc=adq@lidskialf.net \
--cc=linux-media@vger.kernel.org \
--cc=skandalfo@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