From: Nameer Kazzaz <nameer.kazzaz@gmail.com>
To: "Igor M. Liplianin" <liplianin@me.by>
Cc: paul10@planar.id.au, linux-media <linux-media@vger.kernel.org>,
"Christian Hüppe" <christian.hueppe@web.de>
Subject: Re: DM1105: could not attach frontend 195d:1105
Date: Tue, 02 Feb 2010 15:21:46 +0000 [thread overview]
Message-ID: <4B68430A.7010500@gmail.com> (raw)
In-Reply-To: <4B66C649.7010500@gmail.com>
Hi Igor,
What do you think ? if I can help you solve this, let me know what I
can do.
Thanks
Nameer
Nameer Kazzaz wrote:
> Hi there,
> dmesg output with patched dm1105.c against current v4l-dvb 'modprob
> dm1105 card=4'
>
> dm1105 0000:05:0f.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
> DVB: registering new adapter (dm1105)
> dm1105 0000:05:0f.0: MAC dd49b0dc
> dm1105 0000:05:0f.0: could not attach frontend
> dm1105 0000:05:0f.0: PCI INT A disabled
>
> Thanks
> Nameer Kazzaz
>
> Igor M. Liplianin wrote:
>> On 20 ?????? 2010 23:20:20 paul10@planar.id.au wrote:
>>
>>> Igor wrote:
>>>
>>>> Oh, that is wrong. It is registers addresses, Never touch this.
>>>>
>>>> Let's look on that part of code:
>>>>
>>>> /* GPIO's for LNB power control */
>>>> #define DM1105_LNB_MASK 0x00000000 // later in
>>>>
>>> code write it to
>>>
>>>
>>>> DM1105_GPIOCTR, all GPIO's as OUT
>>>> #define DM1105_LNB_OFF 0x00020000 // later in
>>>>
>>> code write it to
>>>
>>>
>>>> DM1105_GPIOVAL, set GPIO17 to HIGH
>>>>
>>>> But you have not to change this.
>>>> Right way is to write another entry in cards structure and so on.
>>>> Better leave it to me.
>>>>
>>>> Regards
>>>> Igor
>>>>
>>> Thanks for all your help, I understand better now. I have moved to
>>> code
>>> like that at the bottom. It still doesn't work, but feels a lot
>>> closer.
>>>
>>> Before I keep playing with values, I want to check I'm on the right
>>> track.
>>> Does it look right? Specific questions:
>>> 1. I see there is a hw_init function. Should I be using that? I
>>> put the
>>> logic into fe_attach because there was already card-specific logic in
>>> there. But this feels like hw initialisation.
>>>
>>> 2. Should I set the control to input or output? I'm assuming input
>>> = 1.
>>>
>>> 3. Would pin 15 be numbered from the left or right - is it 0x4, or
>>> 0x2000?
>>>
>>> Thanks,
>>>
>>> Paul
>>>
>>> *** dm1105.c.old 2010-01-13 16:15:00.000000000 +1100
>>> --- dm1105.c 2010-01-21 08:13:14.000000000 +1100
>>> ***************
>>> *** 51,56 ****
>>> --- 51,57 ----
>>> #define DM1105_BOARD_DVBWORLD_2002 1
>>> #define DM1105_BOARD_DVBWORLD_2004 2
>>> #define DM1105_BOARD_AXESS_DM05 3
>>> + #define DM1105_BOARD_UNBRANDED 4
>>>
>>> /* ----------------------------------------------- */
>>> /*
>>> ***************
>>> *** 171,176 ****
>>> --- 172,181 ----
>>> #define DM05_LNB_13V 0x00020000
>>> #define DM05_LNB_18V 0x00030000
>>>
>>> + /* GPIO's for demod reset for unbranded 195d:1105 */
>>> + #define UNBRANDED_DEMOD_MASK 0x00008000
>>> + #define UNBRANDED_DEMOD_RESET 0x00008000
>>> +
>>> static unsigned int card[] = {[0 ... 3] = UNSET };
>>> module_param_array(card, int, NULL, 0444);
>>> MODULE_PARM_DESC(card, "card type");
>>> ***************
>>> *** 206,211 ****
>>> --- 211,219 ----
>>> [DM1105_BOARD_AXESS_DM05] = {
>>> .name = "Axess/EasyTv DM05",
>>> },
>>> + [DM1105_BOARD_UNBRANDED] = {
>>> + .name = "Unbranded 195d:1105",
>>> + },
>>> };
>>>
>>> static const struct dm1105_subid dm1105_subids[] = {
>>> ***************
>>> *** 229,234 ****
>>> --- 237,246 ----
>>> .subvendor = 0x195d,
>>> .subdevice = 0x1105,
>>> .card = DM1105_BOARD_AXESS_DM05,
>>> + }, {
>>> + .subvendor = 0x195d,
>>> + .subdevice = 0x1105,
>>> + .card = DM1105_BOARD_UNBRANDED,
>>> },
>>> };
>>>
>>> ***************
>>> *** 698,703 ****
>>> --- 710,727 ----
>>> dm1105dvb->fe->ops.set_voltage =
>>> dm1105dvb_set_voltage;
>>>
>>> break;
>>> + case DM1105_BOARD_UNBRANDED:
>>> + printk(KERN_ERR "Attaching as board_unbranded\n");
>>> + outl(UNBRANDED_DEMOD_MASK, dm_io_mem(DM1105_GPIOCTR));
>>> + outl(UNBRANDED_DEMOD_RESET ,
>>> dm_io_mem(DM1105_GPIOVAL));
>>> + dm1105dvb->fe = dvb_attach(
>>> + si21xx_attach, &serit_config,
>>> + &dm1105dvb->i2c_adap);
>>> + if (dm1105dvb->fe)
>>> + dm1105dvb->fe->ops.set_voltage =
>>> + dm1105dvb_set_voltage;
>>> +
>>> + break;
>>> case DM1105_BOARD_DVBWORLD_2002:
>>> case DM1105_BOARD_AXESS_DM05:
>>> default:
>>>
>> Some things are missed, like keep GPIO15 high in set_voltage function.
>> Try attached patch against current v4l-dvb tree with modprobe option
>> card=4
>> modprobe dm1105 card=4
>>
>
next prev parent reply other threads:[~2010-02-02 15:21 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-16 2:49 DM1105: could not attach frontend 195d:1105 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2011-05-05 18:41 Igor M. Liplianin
2011-05-05 19:01 ` Mauro Carvalho Chehab
[not found] <4B7D83B2.4030709@online.no>
2010-02-20 17:49 ` 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
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
2010-01-16 11:55 Igor M. Liplianin
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=4B68430A.7010500@gmail.com \
--to=nameer.kazzaz@gmail.com \
--cc=christian.hueppe@web.de \
--cc=linux-media@vger.kernel.org \
--cc=liplianin@me.by \
--cc=paul10@planar.id.au \
/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