From: Hendrik Skarpeid <skarp@online.no>
To: "Igor M. Liplianin" <liplianin@me.by>
Cc: linux-media@vger.kernel.org, Nameer Kazzaz <nameer.kazzaz@gmail.com>
Subject: Re: DM1105: could not attach frontend 195d:1105
Date: Sat, 06 Mar 2010 20:18:28 +0100 [thread overview]
Message-ID: <4B92AA84.5010908@online.no> (raw)
In-Reply-To: <201003061352.06763.liplianin@me.by>
Igor M. Liplianin skrev:
> On 5 марта 2010 00:16:07 Hendrik Skarpeid wrote:
>
>> Igor M. Liplianin skrev:
>>
>>> On 3 марта 2010 18:42:42 Hendrik Skarpeid wrote:
>>>
>>>> Igor M. Liplianin wrote:
>>>>
>>>>> Now to find GPIO's for LNB power control and ... watch TV :)
>>>>>
>>>> Yep. No succesful tuning at the moment. There might also be an issue
>>>> with the reset signal and writing to GPIOCTR, as the module at the
>>>> moment loads succesfully only once.
>>>> As far as I can make out, the LNB power control is probably GPIO 16 and
>>>> 17, not sure which is which, and how they work.
>>>> GPIO15 is wired to tuner #reset
>>>>
>>> New patch to test
>>>
>>> ------------------------------------------------------------------------
>>>
>>>
>>> No virus found in this incoming message.
>>> Checked by AVG - www.avg.com
>>> Version: 9.0.733 / Virus Database: 271.1.1/2721 - Release Date: 03/03/10
>>> 20:34:00
>>>
>> modprobe si21xx debug=1 produces this output when scanning.
>>
>> [ 2187.998349] si21xx: si21_read_status : FE_READ_STATUS : VSTATUS: 0x02
>> [ 2187.998353] si21xx: si21xx_set_frontend : FE_SET_FRONTEND
>> [ 2187.999881] si21xx: si21xx_setacquire
>> [ 2187.999884] si21xx: si21xx_set_symbolrate : srate = 27500000
>> [ 2188.022645] si21xx: si21_read_status : FE_READ_STATUS : VSTATUS: 0x01
>> [ 2188.054350] si21xx: si21_read_status : FE_READ_STATUS : VSTATUS: 0x02
>> [ 2188.054355] si21xx: si21xx_set_frontend : FE_SET_FRONTEND
>> [ 2188.055875] si21xx: si21xx_setacquire
>> [ 2188.055879] si21xx: si21xx_set_symbolrate : srate = 27500000
>> [ 2188.110359] si21xx: si21_read_status : FE_READ_STATUS : VSTATUS: 0x02
>> [ 2188.110366] si21xx: si21xx_set_frontend : FE_SET_FRONTEND
>> [ 2188.111885] si21xx: si21xx_setacquire
>> [ 2188.111889] si21xx: si21xx_set_symbolrate : srate = 27500000
>> [ 2188.166350] si21xx: si21_read_status : FE_READ_STATUS : VSTATUS: 0x02
>> [ 2188.166354] si21xx: si21xx_set_frontend : FE_SET_FRONTEND
>>
>> Since the tuner at hand uses a Si2109 chip, VSTATUS 0x01 and 0x02 would
>> indicate that blind scanning is used. Blind scanning is a 2109/2110
>> specific function, and may not very usable since we always use initial
>> tuning files anyway. 2109/10 also supports the legacy scanning method
>> which is supported by Si2107708.
>>
>> Is the use of blind scanning intentional?
>>
> Yes, of course, it's intentional. Why not?
> User has freedom to make little errors in channels.conf file. Also the chip didn't support DVB-S2.
> And last, has who si2107/08 ? My chip is si2109.
>
>
>
I agree, it's best to use the hardware features. I was worried that I
may be getting bad i2c data.
If I understand you correctly, you have a working Si2109 frontend driver?
Here's what I'm getting:
Added a few printouts to si21xx.c
u8 signal = si21_readreg(state, ANALOG_AGC_POWER_LEVEL_REG);
dprintk("%s : FE_READ_STATUS : AGC_POWER: 0x%02x\n", __func__,
signal);
si21_readregs(state, LOCK_STATUS_REG_1, regs_read, 0x02);
reg_read = 0;
for (i = 0; i < 7; ++i)
reg_read |= ((regs_read[0] >> i) & 0x01) << (6 - i);
lock = ((reg_read & 0x7f) | (regs_read[1] & 0x80));
dprintk("%s : FE_READ_STATUS : VSTATUS: 0x%02x\n", __func__, lock);
dprintk("%s : FE_READ_REGS : REGS[0]: 0x%02x\n", __func__,
regs_read[0]);
dprintk("%s : FE_READ_REGS : REGS[1]: 0x%02x\n", __func__,
regs_read[1]);
hendrik@iptv:~$ scan -a 1 Sirius-5.0E
[72933.818871] si21xx: si21xx_set_symbolrate : srate = 27500000
[72933.900276] si21xx: si21_read_status : FE_READ_STATUS : AGC_POWER: 0x20
[72933.908807] si21xx: si21_read_status : FE_READ_STATUS : VSTATUS: 0x02
[72933.908812] si21xx: si21_read_status : FE_READ_REGS : REGS[0]: 0x20
[72933.908815] si21xx: si21_read_status : FE_READ_REGS : REGS[1]: 0x00
[72933.908827] si21xx: si21xx_set_frontend : FE_SET_FRONTEND
[72933.914962] si21xx: si21xx_setacquire
[72933.914967] si21xx: si21xx_set_symbolrate : srate = 27500000
[72933.949370] si21xx: si21_read_status : FE_READ_STATUS : AGC_POWER: 0x21
[72933.957877] si21xx: si21_read_status : FE_READ_STATUS : VSTATUS: 0x01
[72933.957882] si21xx: si21_read_status : FE_READ_REGS : REGS[0]: 0xc0
[72933.957885] si21xx: si21_read_status : FE_READ_REGS : REGS[1]: 0x60
[72933.996316] si21xx: si21_read_status : FE_READ_STATUS : AGC_POWER: 0x20
[72934.004959] si21xx: si21_read_status : FE_READ_STATUS : VSTATUS: 0x02
[72934.004964] si21xx: si21_read_status : FE_READ_REGS : REGS[0]: 0x20
[72934.004968] si21xx: si21_read_status : FE_READ_REGS : REGS[1]: 0x00
So, we have signal and sometimes we are getting carrier also.
What worries me most is the FE_READ_REGS : REGS[1]: 0x60
According to the datasheet this register 0x10 Lock status 2, is RCVL 0
0 0 0 0 BSDA BSDO so 0x60 would seem meaningless.
Same results using szap.
hendrik@iptv:~$ szap -a 1 -r -n 170
reading channels from file '/home/hendrik/.szap/channels.conf'
zapping to 170 'NRK1;NRK':
sat 0, frequency = 12015 MHz V, symbolrate 27500000, vpid = 0x0200, apid
= 0x0280 sid = 0x0240
using '/dev/dvb/adapter1/frontend0' and '/dev/dvb/adapter1/demux0'
status 01 | signal c600 | snr 0000 | ber 000000b1 | unc 00000000 |
status 01 | signal c600 | snr 0000 | ber 0000000f | unc 00000000 |
status 01 | signal c000 | snr 0000 | ber 0000980f | unc 00000000 |
status 03 | signal c600 | snr 0000 | ber 000098a3 | unc 00000000 |
status 03 | signal c000 | snr 0000 | ber 000098c7 | unc 00000000 |
Signal but no lock.
Any ideas?
next prev parent reply other threads:[~2010-03-06 19:18 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4B7D83B2.4030709@online.no>
2010-02-20 17:49 ` DM1105: could not attach frontend 195d:1105 Igor M. Liplianin
2010-02-22 20:56 ` Nameer Kazzaz
2010-02-23 12:14 ` Hendrik Skarpeid
2010-02-23 13:12 ` Nameer Kazzaz
2010-02-23 17:40 ` Igor M. Liplianin
2010-02-23 19:40 ` Nameer Kazzaz
2010-03-02 13:06 ` Hendrik Skarpeid
2010-03-02 19:09 ` Hendrik Skarpeid
2010-03-02 23:10 ` Igor M. Liplianin
2010-03-03 8:38 ` Hendrik Skarpeid
2010-03-03 15:49 ` Igor M. Liplianin
2010-03-03 16:42 ` Hendrik Skarpeid
2010-03-03 19:05 ` Igor M. Liplianin
2010-03-04 21:27 ` Hendrik Skarpeid
2010-03-04 22:16 ` Hendrik Skarpeid
2010-03-04 22:46 ` Hendrik Skarpeid
2010-03-06 11:52 ` Igor M. Liplianin
2010-03-06 19:18 ` Hendrik Skarpeid [this message]
2010-03-07 10:12 ` Igor M. Liplianin
2010-03-10 12:15 ` Hendrik Skarpeid
2010-03-31 10:47 ` Hendrik Skarpeid
2010-10-23 9:20 ` Igor M. Liplianin
2011-01-31 9:33 ` Matt Vickers
2011-01-31 17:55 ` Igor M. Liplianin
2011-02-01 5:17 ` Matt Vickers
2011-02-02 18:39 ` Igor M. Liplianin
2011-02-02 18:41 ` Igor M. Liplianin
2011-05-03 21:33 ` Mauro Carvalho Chehab
2011-05-05 18:41 Igor M. Liplianin
2011-05-05 19:01 ` Mauro Carvalho Chehab
-- strict thread matches above, loose matches on Subject: below --
2010-01-16 11:55 Igor M. Liplianin
2010-01-16 2:49 paul10
2010-01-16 3:11 ` paul10
2010-01-16 13:18 ` paul10
2010-01-16 14:12 ` Igor M. Liplianin
2010-01-19 8:51 ` paul10
2010-01-19 13:45 ` Igor M. liplianin
2010-01-20 21:20 ` paul10
2010-01-31 13:45 ` Igor M. Liplianin
2010-02-01 12:17 ` Nameer Kazzaz
2010-02-02 15:21 ` Nameer Kazzaz
2010-02-02 16:57 ` Igor M. Liplianin
2010-02-02 17:16 ` Nameer Kazzaz
2010-02-02 22:07 ` Nameer Kazzaz
2010-02-03 17:41 ` Igor M. Liplianin
2010-02-04 9:56 ` Nameer Kazzaz
2010-01-15 23:14 paul10
2010-01-15 23:54 ` Igor M. Liplianin
2010-01-16 0:10 ` Igor M. Liplianin
2010-01-15 9:15 paul10
2010-01-15 15:21 ` Igor M. Liplianin
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=4B92AA84.5010908@online.no \
--to=skarp@online.no \
--cc=linux-media@vger.kernel.org \
--cc=liplianin@me.by \
--cc=nameer.kazzaz@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.