From: Morvan Le Meut <mlemeut@gmail.com>
To: hermann pitton <hermann-pitton@arcor.de>
Cc: "linux-media@vger.kernel.org" <linux-media@vger.kernel.org>
Subject: Re: (Saa7134) Re: ADS-Tech Instant TV PCI, no remote support, giving up.
Date: Mon, 14 Sep 2009 09:33:56 +0200 [thread overview]
Message-ID: <4AADF1E4.80705@gmail.com> (raw)
In-Reply-To: <1252881711.4318.46.camel@pc07.localdom.local>
So, if i understand correctly, i should change "in" to 0xBF to get the
missing bit.
( and if it work, i will be able to use ir_codes_adstech_dvb_t_pci
instead of rolling my own keymap )
Thanks.
hermann pitton a écrit :
> Hi,
>
> Am Sonntag, den 13.09.2009, 23:59 +0200 schrieb Morvan Le Meut:
>
>> just out of curiosity ( and because google showed me a new trick to try
>> ), i tried to load the module with gpio_tracking=1.
>> this gave me a new thing in dmesg :
>> gpio: mode=0x0000000 in=0x000007f out=0x0000000 [pre-init]
>> Am i correct by thinkig that the in=0x000007f part is the mask ? If it
>> is that then i am a problem : i did specify it as 0xff. Did i miss
>> something ?
>>
>
> it does not cover the IR gpio settings, but what happens in the card
> entry at saa7134-cards.c.
>
> "mode" is the gpio mask defined there, if any. You have nothing set
> there.
> "in" is the actual configuration of the gpio pins. This can reflect
> changes made to them, for example from using an other cards entry
> previously, which can change some pins or changes in different modes on
> them, which are not yet reset. By default it shows the manufacturers
> gpio configuration. 0x7f can mean that the first seven pins (0-6) are
> used for the gpio remote. That would be your mask keycode then.
>
> "out" is what the driver writes to the gpios of that card.
> In this mode only pins are changed, which are high in the mask,
> this is called masked writes. In your case nothing happens.
>
> See my next mail for a simple example of changing the single gpio21 pin
> to 0 in Television mode.
>
> Cheers,
> Hermann
>
next prev parent reply other threads:[~2009-09-14 7:33 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-07 16:59 ADS-Tech Instant TV PCI Morvan Le Meut
2009-09-08 8:25 ` (Saa7134) Re: ADS-Tech Instant TV PCI, no remote support Morvan Le Meut
2009-09-08 9:51 ` Samuel Rakitnican
2009-09-08 10:04 ` Morvan Le Meut
2009-09-08 10:38 ` Morvan Le Meut
2009-09-08 16:18 ` Morvan Le Meut
2009-09-08 17:31 ` Samuel Rakitnican
2009-09-08 17:35 ` Morvan Le Meut
2009-09-08 17:46 ` Morvan Le Meut
2009-09-08 18:25 ` Morvan Le Meut
2009-09-09 8:31 ` Morvan Le Meut
2009-09-09 9:03 ` Morvan Le Meut
2009-09-09 9:04 ` semiRocket
2009-09-09 9:15 ` Morvan Le Meut
2009-09-09 9:33 ` Morvan Le Meut
2009-09-09 14:57 ` Morvan Le Meut
[not found] ` <op.uzzz96se6dn9rq@crni>
2009-09-09 17:09 ` Morvan Le Meut
2009-09-09 21:00 ` Morvan Le Meut
2009-09-10 8:38 ` Morvan Le Meut
2009-09-10 15:22 ` (Saa7134) Re: ADS-Tech Instant TV PCI, no remote support, no idea what to try Morvan Le Meut
2009-09-11 7:54 ` Morvan Le Meut
2009-09-12 8:14 ` (Saa7134) Re: ADS-Tech Instant TV PCI, no remote support, giving up Morvan Le Meut
2009-09-13 4:15 ` hermann pitton
2009-09-13 21:59 ` Morvan Le Meut
2009-09-13 22:41 ` hermann pitton
2009-09-14 7:33 ` Morvan Le Meut [this message]
2009-11-18 9:55 ` Morvan Le Meut
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=4AADF1E4.80705@gmail.com \
--to=mlemeut@gmail.com \
--cc=hermann-pitton@arcor.de \
--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