From: Lauri Laanmets <lauri.laanmets@proekspert.ee>
To: Devin Heitmueller <dheitmueller@kernellabs.com>
Cc: linux-media@vger.kernel.org
Subject: Re: DVB support for MSI DigiVox A/D II and KWorld 320U
Date: Tue, 13 Oct 2009 09:54:05 +0300 (EEST) [thread overview]
Message-ID: <5247569.9431255416845783.JavaMail.root@mail> (raw)
In-Reply-To: <31497292.9391255416643929.JavaMail.root@mail>
Hello
> Check the dvb_gpio setting in the board profile. On some of those
> boards you need to take put one of the GPO pins high to take the demod
> out of reset. The KWorld 315u and 330u are both like that.
Absolutely true. Using the same pin setting as KWorld 330U made the I2C communication work correctly and the device is found.
Now the trouble is that scanning channels doesn't work, blue LED doesn't light up and the device is not heated up.
I'm quite newbie in this field, is there a good way to know what registers to set exactly?
I see that the working "mcentral" code had the following setting:
#define EETI_DEFAULT_GPIO { \
.ts1_on = _BIT_VAL(EM28XX_GPIO0, 0, 0), \
.a_on = _BIT_VAL(EM28XX_GPIO1, 0, 0), \
.xc3028_sec = _BIT_VAL(EM28XX_GPIO2, 1, 0), \
/* reserved */ \
.t1_reset = _BIT_VAL(EM28XX_GPIO4, 0, 1), \
/* reserved */ \
.t1_on = _BIT_VAL(EM28XX_GPIO6, 0, 0), \
.t2_on = _BIT_VAL(EM28XX_GPIO7, 1, 0), \
\
.l1_on = _BIT_VAL(EM28XX_GOP2, 1, 0), \
.d1_reset = _BIT_VAL(EM28XX_GOP3, 0, 1), \
}
But the v4l-dvb uses:
static struct em28xx_reg_seq kworld_330u_digital[] = {
{EM28XX_R08_GPIO, 0x6e, ~EM_GPIO_4, 10},
{EM2880_R04_GPO, 0x08, 0xff, 10},
{ -1, -1, -1, -1},
};
Lauri
next parent reply other threads:[~2009-10-13 7:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <31497292.9391255416643929.JavaMail.root@mail>
2009-10-13 6:54 ` Lauri Laanmets [this message]
2009-11-13 8:37 ` Fwd: DVB support for MSI DigiVox A/D II and KWorld 320U Lauri Laanmets
2009-11-13 8:47 ` Markus Rechberger
2009-11-13 8:59 ` Lauri Laanmets
2009-11-14 18:42 viktor
-- strict thread matches above, loose matches on Subject: below --
2009-10-12 19:23 Lauri Laanmets
2009-10-12 20:13 ` Devin Heitmueller
2009-10-12 20:41 ` Lauri Laanmets
2009-10-12 20:45 ` Devin Heitmueller
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=5247569.9431255416845783.JavaMail.root@mail \
--to=lauri.laanmets@proekspert.ee \
--cc=dheitmueller@kernellabs.com \
--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