On 05/28/2012 04:48 PM, Thomas Mair wrote:
> On 28.05.2012 08:58, Thomas Mair wrote:
>> On 26.05.2012 04:47, poma wrote:
>>> On 05/20/2012 11:12 PM, Thomas Mair wrote:
>>>> On 20.05.2012 22:08, Antti Palosaari wrote:
>>>>> On 20.05.2012 20:04, poma wrote:
>>>>>> After hard/cold boot:
>>>>>
>>>>>> DVB: register adapter0/net0 @ minor: 2 (0x02)
>>>>>> rtl2832u_frontend_attach:
>>>>>> rtl28xxu_ctrl_msg: failed=-32
>>>>>> rtl28xxu_ctrl_msg: failed=-32
>>>>>> rtl28xxu_ctrl_msg: failed=-32
>>>>>> rtl28xxu_ctrl_msg: failed=-32
>>>>>> rtl28xxu_ctrl_msg: failed=-32
>>>>>> rtl28xxu_ctrl_msg: failed=-32
>>>>>> rtl28xxu_ctrl_msg: failed=-32
>>>>>> rtl28xxu_ctrl_msg: failed=-32
>>>>>> rtl28xxu_ctrl_msg: failed=-32
>>>>>> rtl28xxu_ctrl_msg: failed=-32
>>>>>> No compatible tuner found
>>>>>
>>>>> These errors are coming from tuner probe. As it still goes to probing and 
>>>>> did not jump out earlier when gate is opened it means that demod is 
>>>>> answering commands but tuner are not.
>>>>>
>>>>> My guess is that tuner is still on the reset or not powered at all. It is 
>>>>> almost 100% sure error is wrong tuner GPIO.
>>>>
>>>> There is an issue with GPIO, as FC0012 tuner callback will set 
>>>> the value of one of the GPIO outputs. However fixing that, will
>>>> not resolve the issue. So I need to debug the problem further.
>>>>
>>> True. Whatever a value is changed - 'rtl2832u_power_ctrl', it brakes
>>> even more.
>>> Precisely, what breaks a tuner on next soft [re]boot are apps/utils
>>> which engage tzap/scan[dvb].
>>>
>>
>> To reproduce the bug it is not necessary to reboot the machine. Simply 
>> unload and load of the dvb_usb_rtl28xxu module will lead to the same 
>> situation.
>>
>> I suspect, that when power is turned off, the tuner power is not 
>> switched on correctly. The mistake is not related to the OUTPUT_VAL
>> registers but probably to the OUTPUT_DIR or OUTPUT_EN registers.
>>
>> What makes me wonder is if no tuning operation is performed before
>> reboot, the driver does work correctly after that, as poma already
>> noticed.
>>
>> I have some spare time today and will investigate the problem further.
>>
> 
> I tried a few things regarding the problem today and could find out a 
> few more details, but could not resolve the issue.
> 
> The GPIO pin configuration for the devices with the fc0012 (and probably
> also with the fc0013) tuner is the following:
> 
> GPIO0: demod power
> GPIO3: tuner power? (the realtek driver puts this to 1 and never touches it 
> again)
> GPIO4: tuner power? (maybe antenna power?)
> GPIO5: tuner reset
> GPIO6: UHF/VHF band selection
> 
> All of these GPIOs are configured as output. When the device is plugged in
> the tuner is powered up correctly, but I am not able to power it up when
> a reboot is performed. What I tried was the following:
> 
> - on rtl28xxu_power_ctrl off:
>   - GPIO4 = 1 (off)
>   - GPIO5 = 0 
>   - GPIO6 = 0 (default state)
> 
> - on rtl28xxu_power_ctrl on:
>   - GPIO3 = 1
>   - GPIO4 = 0 (on)
>   - GPIO5 = 0 
>   - GPIO6 = 0 (default state)
> 
> - on rtl2832_frontend_attach:
>   - GPIO5 = 1 
>   - GPIO5 = 0 
> 
> This sequence should ensure that the tuner is powered on when the frontend
> is attached, and a tuner reset is being performed before the tuner is probed.
> However this sequence fails the same way as it did before. I tried to add
> timeouts to be sure that the tuner is not probed while it is reset but that
> did not help either.
> 
> Right now I really don't know where I should look for the solution of
> the problem. It seems that the tuner reset does not have any effect on the 
> tuner whatsoever.
> 
> Is there anybody who could look at the code, or maybe knows what could be
> the cause of the problem? I suspect I am just too blind to see my own 
> mistakes.
> 
> Regards
> Thomas
> 

Cheers Thomas, Hans-Frieder, Antti, Mauro!
Hans-Frieder, are you having the same issue with fc0011&af9035?
Antti, no tricks up your sleeve?
Senhor Mauro, is rtl2832 demod going to be merged?

regards,
poma
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to