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
> hermann pitton a écrit :
> > Am Samstag, den 12.09.2009, 10:14 +0200 schrieb Morvan Le Meut:
> >
> >> Since i don't know where to look, i finally decided to use a basic
> >> incorrect keymap :
> >> /* ADS Tech Instant TV PCI Remote */
> >> static struct ir_scancode ir_codes_adstech_pci[] = {
> >> /* too many repeating codes : incorrect gpio ?. */
> >>
> >> { 0x1f, KEY_MUTE },
> >> { 0x1d, KEY_SEARCH },
> >> { 0x17, KEY_EPG }, /* Guide */
> >> { 0x0f, KEY_UP },
> >> { 0x6, KEY_DOWN },
> >> { 0x16, KEY_LEFT },
> >> { 0x1e, KEY_RIGHT },
> >> { 0x0e, KEY_SELECT }, /* Enter */
> >> { 0x1a, KEY_INFO },
> >> { 0x12, KEY_EXIT },
> >> { 0x19, KEY_PREVIOUS },
> >> { 0x11, KEY_NEXT },
> >> { 0x18, KEY_REWIND },
> >> { 0x10, KEY_FORWARD },
> >> { 0x4, KEY_PLAYPAUSE },
> >> { 0x07, KEY_STOP },
> >> { 0x1b, KEY_RECORD },
> >> { 0x13, KEY_TUNER }, /* Live */
> >> { 0x0a, KEY_A },
> >> { 0x03, KEY_PROG1 }, /* 1 */
> >> { 0x01, KEY_PROG2 }, /* 2 */
> >> { 0x0, KEY_VIDEO },
> >> { 0x0b, KEY_CHANNELUP },
> >> { 0x08, KEY_CHANNELDOWN },
> >> { 0x15, KEY_VOLUMEUP },
> >> { 0x1c, KEY_VOLUMEDOWN },
> >> };
> >>
> >> struct ir_scancode_table ir_codes_adstech_pci_table = {
> >> .scan = ir_codes_adstech_pci,
> >> .size = ARRAY_SIZE(ir_codes_adstech_pci),
> >> };
> >> EXPORT_SYMBOL_GPL(ir_codes_adstech_pci_table);
> >>
> >> No numbers in favor of arrows and ch+/- Vol+/- . Well 246 will be arrows
> >> and 5 select, 7 and 8 are undefined, 9 become vol-, 1 epg and 3 is tuner.
> >> If someone, one day, wants to find that missig bit, i'll be happy to
> >> help. ( Strange anyway : it's as if there was a 0x7f mask even when i
> >> specify a 0xff one )
> >> Feel free to write a patch.
> >>
> >> Morvan Le Meut a écrit :
> >>
> >>> um .. help, please ?
> >>> how can i make the driver read 1011011 instead of 011011 when i press
> >>> Power instead of record on the remote ?
> >>>
> >>> thanks
> >>>
> >>>
> >
> > Morvan,
> >
> > I still have a huge mail backlash and are not in details what you may
> > have tried already, but if you have a missing/unknown gpio on such a
> > remote, you start to test for that one with mask_keycode = 0x0 in
> > saa7134-input.c and if it is then found, you do add it to that mask.
> >
> > If that doesn't help, it might be something special.
> >
> > Cheers,
> > Hermann
> >
--
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
