RE: lgdt3304
] tda18271_lookup_pll_map: [1-0060|M] (31) main_pll: post div = 0x20, div = 0x10 [ 4800.236205] lgdt3305_set_modulation: [ 4800.236211] lgdt3305_read_reg: reg: 0x [ 4800.236761] lgdt3305_write_reg: reg: 0x, val: 0x03 [ 4800.237057] lgdt3305_passband_digital_agc: agc ref: 0x32c4 [ 4800.237060] lgdt3305_write_reg: reg: 0x0012, val: 0x32 [ 4800.237433] lgdt3305_write_reg: reg: 0x0013, val: 0xc4 [ 4800.237810] lgdt3305_agc_setup: lockdten = 0, acqen = 0 [ 4800.237812] lgdt3305_write_reg: reg: 0x0314, val: 0xe1 [ 4800.238186] lgdt3305_set_reg_bit: reg: 0x030e, bit: 2, level: 0 [ 4800.238188] lgdt3305_read_reg: reg: 0x030e [ 4800.238745] lgdt3305_write_reg: reg: 0x030e, val: 0x18 [ 4800.239041] lgdt3305_rfagc_loop: ifbw: 0x8000 [ 4800.239044] lgdt3305_write_reg: reg: 0x0308, val: 0x80 [ 4800.239416] lgdt3305_write_reg: reg: 0x0309, val: 0x00 [ 4800.239793] lgdt3305_write_reg: reg: 0x030d, val: 0x00 [ 4800.240176] lgdt3305_write_reg: reg: 0x0106, val: 0x4f [ 4800.240552] lgdt3305_write_reg: reg: 0x0107, val: 0x0c [ 4800.240927] lgdt3305_write_reg: reg: 0x0108, val: 0xac [ 4800.241304] lgdt3305_write_reg: reg: 0x0109, val: 0xba [ 4800.241680] lgdt3305_spectral_inversion: (1) [ 4800.241683] lgdt3305_write_reg: reg: 0x0126, val: 0xf9 [ 4800.242057] lgdt3305_mpeg_mode: (1) [ 4800.242060] lgdt3305_set_reg_bit: reg: 0x050e, bit: 5, level: 1 [ 4800.242062] lgdt3305_read_reg: reg: 0x050e [ 4800.242616] lgdt3305_write_reg: reg: 0x050e, val: 0x7b [ 4800.242911] lgdt3305_mpeg_mode_polarity: edge = 1, valid = 1 [ 4800.242913] lgdt3305_read_reg: reg: 0x050e [ 4800.243471] lgdt3305_write_reg: reg: 0x050e, val: 0x7b [ 4800.243767] lgdt3305_soft_reset: [ 4800.243770] lgdt3305_set_reg_bit: reg: 0x0002, bit: 0, level: 0 [ 4800.243772] lgdt3305_read_reg: reg: 0x0002 [ 4800.244333] lgdt3305_write_reg: reg: 0x0002, val: 0x9a [ 4800.268013] lgdt3305_set_reg_bit: reg: 0x0002, bit: 0, level: 1 [ 4800.268017] lgdt3305_read_reg: reg: 0x0002 [ 4800.268479] lgdt3305_write_reg: reg: 0x0002, val: 0x9b [ 4800.397037] lgdt3305_read_reg: reg: 0x0003 [ 4800.397499] lgdt3305_read_status: SIGNALEXIST INLOCK [ 4800.397502] lgdt3305_read_reg: reg: 0x011d [ 4800.397979] lgdt3305_read_cr_lock_status: (1) CLOCKVSB [ 4800.397998] function : dvb_dmxdev_filter_set, PID=0x1ffb, flags=05, timeout=0 [ 4800.436025] function : dvb_dmxdev_filter_set, PID=0x, flags=05, timeout=0 [ 4800.768016] lgdt3305_read_reg: reg: 0x0003 [ 4800.768479] lgdt3305_read_status: SIGNALEXIST INLOCK SYNCLOCK NOFECERR SNRGOOD [ 4800.768482] lgdt3305_read_reg: reg: 0x011d [ 4800.768959] lgdt3305_read_cr_lock_status: (1) CLOCKVSB [ 4800.768961] lgdt3305_get_frontend: [ 4802.132014] lgdt3305_read_reg: reg: 0x0003 [ 4802.132477] lgdt3305_read_status: SIGNALEXIST INLOCK SYNCLOCK NOFECERR SNRGOOD [ 4802.132480] lgdt3305_read_reg: reg: 0x011d [ 4802.132955] lgdt3305_read_cr_lock_status: (1) CLOCKVSB [ 4803.508016] lgdt3305_read_reg: reg: 0x0003 [ 4803.508479] lgdt3305_read_status: SIGNALEXIST INLOCK SYNCLOCK NOFECERR SNRGOOD [ 4803.508482] lgdt3305_read_reg: reg: 0x011d [ 4803.508957] lgdt3305_read_cr_lock_status: (1) CLOCKVSB [ 4804.900042] lgdt3305_read_reg: reg: 0x0003 [ 4804.900506] lgdt3305_read_status: SIGNALEXIST INLOCK SYNCLOCK NOFECERR SNRGOOD [ 4804.900508] lgdt3305_read_reg: reg: 0x011d [ 4804.900984] lgdt3305_read_cr_lock_status: (1) CLOCKVSB [ 4806.292015] lgdt3305_read_reg: reg: 0x0003 [ 4806.292479] lgdt3305_read_status: SIGNALEXIST INLOCK SYNCLOCK NOFECERR SNRGOOD [ 4806.292481] lgdt3305_read_reg: reg: 0x011d [ 4806.292957] lgdt3305_read_cr_lock_status: (1) CLOCKVSB [ 4807.448098] lgdt3305_get_tune_settings: [ 4807.448120] lgdt3304_set_parameters: (479028615, 7) [ 4807.448129] tda18271_tune: [1-0060|M] freq = 479028615, ifc = 3250, bw = 600, agc_mode = 3, std = 4 [ 4807.448133] tda18271_agc: [1-0060|M] no agc configuration provided -Original Message- From: linux-media-ow...@vger.kernel.org [mailto:linux-media-ow...@vger.kernel.org] On Behalf Of Steven Toth Sent: Wednesday, July 10, 2013 8:51 AM To: Carl-Fredrik Sundstrom Cc: Devin Heitmueller; linux-media@vger.kernel.org Subject: Re: lgdt3304 On Tue, Jul 9, 2013 at 9:40 PM, Carl-Fredrik Sundstrom c...@blueflowamericas.com wrote: I don't have digital cable only over the air ATSC. No one else on this list has this card ? You are very welcome, thank you. We generally recommend Linux users purchase cards that are already supported (or semi supported), such as the HVR2250. If you're keen enough to tackle adding support for a new board then that's great news, but very few people usually have experience with hardware not yet supported. The channels.conf is capable of support digital cable and ATSC, simply change the modulation scheme and your target frequency and try again. A quick google for an equivalent ATSC channels.conf provides a lot of useful information. Create your channels.conf to match your target frequencies in Hz and use azap to debug. Eg. KPAX-CW:177028615:8VSB:65:68:2 Thanks
RE: lgdt3304
I don't have digital cable only over the air ATSC. No one else on this list has this card ? Thanks /// Carl -Original Message- From: linux-media-ow...@vger.kernel.org [mailto:linux-media-ow...@vger.kernel.org] On Behalf Of Steven Toth Sent: Tuesday, July 09, 2013 9:54 AM To: Carl-Fredrik Sundstrom Cc: Devin Heitmueller; linux-media@vger.kernel.org Subject: Re: lgdt3304 using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' tune to: 57028615:8VSB WARNING: tuning failed!!! tune to: 57028615:8VSB (tuning failed) I don't have a box in front of me but that's usually a sign that the frequency details you are passing in are bogus, so the tuner driver is rejecting it. Check your command line tuning tools and args. Here's a one line channels.conf for azap (US digital cable) that works fine, and the azap console output: ch86:59700:QAM_256:0:0:101 stoth@mythbackend:~/.azap$ azap ch86 using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' tuning to 59700 Hz video pid 0x, audio pid 0x status 00 | signal | snr b770 | ber | unc | status 1f | signal 0154 | snr 0154 | ber 00ad | unc 00ad | FE_HAS_LOCK status 1f | signal 0156 | snr 0156 | ber | unc | FE_HAS_LOCK -- Steven Toth - Kernel Labs http://www.kernellabs.com -- 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 -- 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
RE: lgdt3304
,snd_rawmidi,snd_hda_codec,snd_hda_intel, snd_seq_device,snd_hda_codec_analog asus_atk0110 17390 0 mac_hid13037 0 soundcore 12600 1 snd lp 13299 0 parport40753 3 lp,ppdev,parport_pc pata_acpi 12886 0 firewire_ohci 35292 0 firewire_core 61718 1 firewire_ohci crc_itu_t 12627 1 firewire_core usb_storage47684 0 pata_jmicron 12662 0 floppy 55441 0 sky2 52846 0 ahci 25507 0 libahci26108 1 ahci -Original Message- From: linux-media-ow...@vger.kernel.org [mailto:linux-media-ow...@vger.kernel.org] On Behalf Of Steven Toth Sent: Friday, June 28, 2013 10:23 AM To: Carl-Fredrik Sundstrom Cc: Devin Heitmueller; linux-media@vger.kernel.org Subject: Re: lgdt3304 On Thu, Jun 27, 2013 at 11:00 PM, Carl-Fredrik Sundstrom c...@blueflowamericas.com wrote: 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 ? The SAA7164 driver (amongst others) demonstrates how to expose multiple tuners on a single card via multiple adapters, /dev/dvb/adapterX. The cx88 driver demonstrates how to expose multiple tuners/demods via a single transport bus, via a single dvb adapter. /dev/dvb/adapter0/frontendX - Steve -- Steven Toth - Kernel Labs http://www.kernellabs.com -- 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 -- 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
lgdt3304
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.
Thanks /// Carl-Fredrik
--
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
RE: lgdt3304
One of the TDA18271HD/C2 is detected on the secondary i2c bus at address
0x60. I haven't tried yet to find the second one.
The SAA7160E PCI-E interface has the following GPIO
GPIO_[15:1]: interrupts from other external devices
GPIO_[23:16]: chip select to other external devices
GPIO_[29:26]: general purpose
BOOT_0 and BOOT_1: boot mode. The boot mode pins can be used as application
GPIO pins after 500 ms (after power-up). The boot mode has been latched.
All of them are input and output with internal pull-up, so they should all
be set high.
Should I just try to change them all to outputs and then set them low one by
one until something answers at address 0x0e or 0x59?
Thanks /// Carl
-Original Message-
From: Devin Heitmueller [mailto:dheitmuel...@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
c...@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
--
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
RE: lgdt3304
I found a datasheet for lgdt3305 it does indeed have a reset pin at pin 37 active low with internal pull up. I will try to attach a probe to that pin and walk through all of the GPIO until I find the right one. I hope that lgdt3304 and lgdt3305 are pin compatible otherwise I might not have much success. -Original Message- From: linux-media-ow...@vger.kernel.org [mailto:linux-media-ow...@vger.kernel.org] On Behalf Of Steven Toth Sent: Thursday, June 27, 2013 1:59 PM To: Carl-Fredrik Sundstrom Cc: linux-media@vger.kernel.org Subject: Re: lgdt3304 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. A GPIO holding the 3304 in reset? -- Steven Toth - Kernel Labs http://www.kernellabs.com -- 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 -- 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
RE: lgdt3304
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:dheitmuel...@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
c...@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
--
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
