From: "Carl-Fredrik Sundstrom" <cf@blueflowamericas.com>
To: "'Devin Heitmueller'" <dheitmueller@kernellabs.com>
Cc: <linux-media@vger.kernel.org>
Subject: RE: lgdt3304
Date: Thu, 27 Jun 2013 22:00:11 -0500 [thread overview]
Message-ID: <011901ce73ab$9b81cce0$d28566a0$@blueflowamericas.com> (raw)
In-Reply-To: <CAGoCfiyjeqxVV8A_MM-iV58=s48FEhNPA=5MPg3WAOAKs8d2iA@mail.gmail.com>
I am able to detect two lgdt3304 one on each i2c bus now. As you suspected I
had to set GPIO pin 17 for them to come alive.
Now to my next question, how do I attach two front ends I have two lgdt3304
and two TDA18271HD/C2
Is there a good driver I can look at where they do that ?
Thanks /// Carl
-----Original Message-----
From: Devin Heitmueller [mailto:dheitmueller@kernellabs.com]
Sent: Thursday, June 27, 2013 1:59 PM
To: Carl-Fredrik Sundstrom
Cc: linux-media@vger.kernel.org
Subject: Re: lgdt3304
On Thu, Jun 27, 2013 at 2:38 PM, Carl-Fredrik Sundstrom
<cf@blueflowamericas.com> wrote:
>
> Has the driver for lgdt3304 been tested ? I am trying to get a new
> card working
>
> AVerMedia AVerTVHD Duet PCTV tuner (A188) A188-AF PCI-Express x1
> Interface
>
> It is using
>
> 1 x saa7160E
> 2 x LGDT3304
> 2 x TDA18271HD/C2
>
> I get so far that I can load a basic driver by modifying the existing
> saa716x driver, I can detect the TDA18271HD/C2, but I fail to detect
> the
> LGDT3304 when attaching it using the 3305 driver.
>
> I always fail at the first read from LGDT3305_GEN_CTRL_2, does this
> register even exist in lgdt3304 or is it specific to lgdt3305?
>
> /* verify that we're talking to a lg dt3304/5 */
> ret = lgdt3305_read_reg(state, LGDT3305_GEN_CTRL_2, &val);
> if ((lg_fail(ret)) | (val == 0))
> {
> printk("fail 1\n");
> goto fail;
> }
>
> Since I do find the TDA18271HD/C2 I don't think there is something
> wrong with the i2c buss. I also tried every possible i2c address without
success.
> The lgdt3305 has option between address 0x0e and 0x59, is it the same
> for
> 3304 ?
>
> This is the first time I am trying to get a driver to work in Linux.
> Please help me.
Either the i2c is broken or the lgdt3304 is being held in reset by a GPIO.
Also, that device has multiple i2c busses, so you could be looking on the
wrong bus.
Do you see *any* i2c devices (such as an eeprom).
Devin
--
Devin J. Heitmueller - Kernel Labs
http://www.kernellabs.com
next prev parent reply other threads:[~2013-06-28 3:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-27 18:38 lgdt3304 Carl-Fredrik Sundstrom
2013-06-27 18:58 ` lgdt3304 Steven Toth
2013-06-27 21:00 ` lgdt3304 Carl-Fredrik Sundstrom
2013-06-27 18:59 ` lgdt3304 Devin Heitmueller
2013-06-27 20:45 ` lgdt3304 Carl-Fredrik Sundstrom
2013-06-28 3:00 ` Carl-Fredrik Sundstrom [this message]
2013-06-28 15:23 ` lgdt3304 Steven Toth
2013-07-09 4:18 ` lgdt3304 Carl-Fredrik Sundstrom
2013-07-09 14:53 ` lgdt3304 Steven Toth
2013-07-10 1:40 ` lgdt3304 Carl-Fredrik Sundstrom
2013-07-10 13:51 ` lgdt3304 Steven Toth
2013-07-11 3:51 ` lgdt3304 Carl-Fredrik Sundstrom
2013-07-11 12:46 ` lgdt3304 Antti Palosaari
[not found] ` <01ab01ce7df1$e92cc9e0$bb865da0$@blueflowamericas.com>
2013-07-11 12:52 ` FW: lgdt3304 Steven Toth
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='011901ce73ab$9b81cce0$d28566a0$@blueflowamericas.com' \
--to=cf@blueflowamericas.com \
--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