public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Antti Palosaari <crope@iki.fi>
To: Alistair Buxton <a.j.buxton@gmail.com>
Cc: linux-media@vger.kernel.org,
	"Jan Hoogenraad" <jan-conceptronic@hoogenraad.net>,
	"Maxim Levitsky" <maximlevitsky@gmail.com>,
	"Sascha Wüstemann" <sascha@killerhippy.de>,
	"Thomas Holzeisen" <thomas@holzeisen.de>,
	stybla@turnovfree.net
Subject: Re: RTL2831U driver updates
Date: Mon, 08 Aug 2011 22:50:51 +0300	[thread overview]
Message-ID: <4E403E1B.3020806@iki.fi> (raw)
In-Reply-To: <CAO-Op+FY9KVPQFgF1ykNz_BqJu653yM2-1oj5BZotUOhLtKGVw@mail.gmail.com>

On 08/06/2011 08:13 AM, Alistair Buxton wrote:
> On 6 August 2011 04:56, Alistair Buxton <a.j.buxton@gmail.com> wrote:
>> With the latest driver my card never gets a signal lock, not even
>> once. As before there are no error messages. It does always probe
>> correctly now though.
> 
> I tracked this down to:
> 
> http://git.linuxtv.org/anttip/media_tree.git/commit/e5d3e4f27f0cf71c29d12ce39752195d8994dea3
> 
> and to this specific change:
> 
> @@ -459,21 +563,14 @@ static int rtl28xxu_power_ctrl(struct
> dvb_usb_device *d, int onoff)
>                 sys0 = sys0 & 0x0f;
>                 sys0 |= 0xe0;
>         } else {
> -
> -#if 0 /* keep */
>                 /*
>                  * FIXME: Use .fe_ioctl_override() to prevent demod
> -                * IOCTLs in case of device is powered off.
> -                *
> -                * For now we cannot power off device because most FE IOCTLs
> -                * can be performed only when device is powered.
> -                * Using IOCTLs when device is powered off will result errors
> -                * because register access to demod fails.
> +                * IOCTLs in case of device is powered off. Or change
> +                * RTL2830 demod not perform requestesd IOCTL & IO when sleep.
>                  */
>                 gpio &= (~0x01); /* GPIO0 = 0 */
>                 gpio |= 0x10; /* GPIO4 = 1 */
>                 sys0 = sys0 & (~0xc0);
> -#endif
>         }
> 
>         deb_info("%s: WR SYS0=%02x GPIO_OUT_VAL=%02x\n", __func__, sys0, gpio);
> 
> 
> Commenting those three lines makes the driver work again. Don't know
> yet if it will keep working for longer than a couple of days.

I suspect it is tuner GPIO. It is not clear which GPIO pins are used for
tuner reset. I should find this out soon. Most likely MXL5005S tuner
reset have connected to different GPIO than MT2060 design I have.

Could you test commenting out only gpio change to see if it helps?

regards
Antti
-- 
http://palosaari.fi/

  reply	other threads:[~2011-08-08 19:50 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-16  8:19 RTL2831U wont compile against 2.6.38 Thomas Holzeisen
2011-06-16 11:34 ` Sascha Wüstemann
2011-06-16 21:36   ` RTL2831U driver updates Jan Hoogenraad
2011-06-17  8:30     ` Sascha Wüstemann
2011-06-17 14:17       ` Thomas Holzeisen
2011-06-20 16:10     ` poma
2011-06-20 22:22     ` Antti Palosaari
2011-06-21  5:40       ` Jan Hoogenraad
2011-06-21  8:03         ` Steffen Barszus
2011-06-22  5:34           ` Jan Hoogenraad
2011-06-22  6:13             ` Steffen Barszus
2011-06-22 11:11               ` Antti Palosaari
2011-06-21  9:41       ` Maxim Levitsky
2011-06-21 10:00         ` Jan Hoogenraad
2011-07-09  3:27           ` Antti Palosaari
2011-08-04 23:43             ` Antti Palosaari
2011-08-06  3:56               ` Alistair Buxton
2011-08-06  5:13                 ` Alistair Buxton
2011-08-08 19:50                   ` Antti Palosaari [this message]
2011-08-09 13:22                     ` Alistair Buxton
2011-10-21 20:41                       ` Alistair Buxton
2011-06-17 10:39   ` RTL2831U wont compile against 2.6.38 Thomas Holzeisen
2011-06-17 19:28     ` Sascha Wüstemann
2011-06-18 12:44       ` Thomas Holzeisen
2011-06-18 12:56         ` Antti Palosaari

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=4E403E1B.3020806@iki.fi \
    --to=crope@iki.fi \
    --cc=a.j.buxton@gmail.com \
    --cc=jan-conceptronic@hoogenraad.net \
    --cc=linux-media@vger.kernel.org \
    --cc=maximlevitsky@gmail.com \
    --cc=sascha@killerhippy.de \
    --cc=stybla@turnovfree.net \
    --cc=thomas@holzeisen.de \
    /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