From: "Miroslav Šustek" <sustmidown@centrum.cz>
To: Trent Piepho <xyzzy@speakeasy.org>
Cc: linux-media@vger.kernel.org, mchehab@infradead.org
Subject: Re: [PATCH] Leadtek WinFast DTV-1800H support
Date: Sun, 31 May 2009 21:28:03 +0200 [thread overview]
Message-ID: <1243798083.6400.25.camel@localhost> (raw)
In-Reply-To: <Pine.LNX.4.58.0905310536500.32713@shell2.speakeasy.net>
Trent Piepho píše v Ne 31. 05. 2009 v 06:34 -0700:
> Instead of raising the reset line here, why not change the gpio settings in
> the card definition to have it high? Change gpio1 for television to 0x7050
> and radio to 0x7010.
Personally, I don't know when these .gpioX members are used (before firmware loads or after...).
But I assume that adding the high on reset pin shouldn't break anything, so we can do this.
> Then the reset can be done with:
>
> case XC2028_TUNER_RESET:
> /* GPIO 12 (xc3028 tuner reset) */
> cx_write(MO_GP1_IO, 0x101000);
> mdelay(50);
> cx_write(MO_GP1_IO, 0x101010);
> mdelay(50);
> return 0;
>
> Though I have to wonder why each card needs its own xc2028 reset function.
> Shouldn't they all be the same other than what gpio they change?
>
>
> @@ -2882,6 +2946,16 @@
> cx_set(MO_GP0_IO, 0x00000080); /* 702 out of reset */
> udelay(1000);
> break;
> +
> + case CX88_BOARD_WINFAST_DTV1800H:
> + /* GPIO 12 (xc3028 tuner reset) */
> + cx_set(MO_GP1_IO, 0x1010);
> + mdelay(50);
> + cx_clear(MO_GP1_IO, 0x10);
> + mdelay(50);
> + cx_set(MO_GP1_IO, 0x10);
> + mdelay(50);
> + break;
> }
> }
>
> Couldn't you replace this with:
>
> case CX88_BOARD_WINFAST_DTV1800H:
> cx88_xc3028_winfast1800h_callback(code, XC2028_TUNER_RESET, 0);
> break;
>
next prev parent reply other threads:[~2009-05-31 19:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200905291638.9584@centrum.cz>
2009-05-29 14:39 ` [PATCH] Leadtek WinFast DTV-1800H support Miroslav Šustek
2009-05-31 13:34 ` Trent Piepho
2009-05-31 17:39 ` Miroslav Šustek
2009-05-31 19:58 ` Mauro Carvalho Chehab
2009-06-01 1:58 ` hermann pitton
2009-06-01 9:07 ` Mauro Carvalho Chehab
2009-06-01 22:26 ` hermann pitton
2009-05-31 19:28 ` Miroslav Šustek [this message]
[not found] <200905311925.19140@centrum.cz>
[not found] ` <200905311926.3696@centrum.cz>
[not found] ` <200905311927.20442@centrum.cz>
[not found] ` <200905311928.4713@centrum.cz>
[not found] ` <200905311929.21561@centrum.cz>
[not found] ` <200905311930.5668@centrum.cz>
[not found] ` <200905311931.18645@centrum.cz>
[not found] ` <200905311932.22284@centrum.cz>
[not found] ` <200905311933.22524@centrum.cz>
2009-05-31 20:50 ` Trent Piepho
[not found] <200905291628.32305@centrum.cz>
[not found] ` <200905291629.364@centrum.cz>
[not found] ` <200905291630.21607@centrum.cz>
[not found] ` <200905291631.1309@centrum.cz>
[not found] ` <200905291632.13608@centrum.cz>
2009-05-29 14:32 ` Miroslav Šustek
2009-05-31 18:04 ` CityK
[not found] <200905102337.22307@centrum.cz>
[not found] ` <200905102338.14151@centrum.cz>
[not found] ` <200905102339.24789@centrum.cz>
2009-05-10 21:39 ` Miroslav Šustek
2009-05-28 18:44 ` Miroslav Šustek
2009-05-28 19:42 ` hermann pitton
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=1243798083.6400.25.camel@localhost \
--to=sustmidown@centrum.cz \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=xyzzy@speakeasy.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