I found the mask_keycode: 0x02F200
Not mask_keydown bit.
Not mask_keydown bit.
When the card is working some bits of the read gpio are changing.
In line 58 of saa7134-input.c:
gpio = saa_readl(SAA7134_GPIGPSTATUS0 >2);
always return the last key pressed.
There is a way to clear the last key pressed from gpio?
How I can know if a key is pressed?
Thanks.
Jose Alberto

Saturday 06 May 2006 12:35, Jose Alberto Reguero wrote:
I found the mask_keycode: 0x02F200
Not mask_keydown bit.
Not mask_keydown bit.
When the card is working some bits of the read gpio are changing.

In line 58 of saa7134-input.c:

gpio = saa_readl(SAA7134_GPIGPSTATUS0 >2);

always return the last key pressed.

There is a way to clear the last key pressed from gpio?
How I can know if a key is pressed?

You need to find out how the card is flagging "key down". maybe the card
needs you to operate an output GPI pin to acknowledge the read.

This is all card specific, so you either need to spy on how the Windows driver
does it, or reverse engineer the hardware.

regards,
Peter

El S, 6 de Mayo de 2006 12:52, Peter Missel :
Saturday 06 May 2006 12:35, Jose Alberto Reguero wrote:
I found the mask_keycode: 0x02F200
Not mask_keydown bit.
Not mask_keydown bit.
When the card is working some bits of the read gpio are changing.

In line 58 of saa7134-input.c:

gpio = saa_readl(SAA7134_GPIGPSTATUS0 >2);

always return the last key pressed.

There is a way to clear the last key pressed from gpio?
How I can know if a key is pressed?

You need to find out how the card is flagging "key down". maybe the card
needs you to operate an output GPI pin to acknowledge the read.

This is all card specific, so you either need to spy on how the Windows
driver does it, or reverse engineer the hardware.

regards,
Peter

Thanks, I found it. The attached patch work.
There is still a problem. When the card is working the gpio is changing
constantly, and generate a lot of debug output.

saa7134[0]/ir: build_key gpio=0x1c14f mask=0x2f200 data=24
saa7134[1]/ir: build_key gpio=0x3b3c5 mask=0x2f200 data=55
saa7134[2]/ir: build_key gpio=0x13f326 mask=0x2f200 data=63
saa7134[0]/ir: build_key gpio=0x1c1d8 mask=0x2f200 data=24
saa7134[1]/ir: build_key gpio=0x13b34f mask=0x2f200 data=55
saa7134[2]/ir: build_key gpio=0x3f3ff mask=0x2f200 data=63
saa7134[0]/ir: build_key gpio=0x11c120 mask=0x2f200 data=24
saa7134[1]/ir: build_key gpio=0x3b33d mask=0x2f200 data=55
saa7134[2]/ir: build_key gpio=0x13f3e6 mask=0x2f200 data=63
saa7134[0]/ir: build_key gpio=0x11c1d8 mask=0x2f200 data=24
saa7134[1]/ir: build_key gpio=0x13b302 mask=0x2f200 data=55
saa7134[2]/ir: build_key gpio=0x3f350 mask=0x2f200 data=63
saa7134[0]/ir: build_key gpio=0x1c15b mask=0x2f200 data=24
saa7134[1]/ir: build_key gpio=0x3b3b7 mask=0x2f200 data=55
saa7134[2]/ir: build_key gpio=0x13f3cc mask=0x2f200 data=63

Signed-off-by: Jose Alberto Reguero <jareguero (AT) telefonica (DOT) net>

Thanks
Jose Alberto

Wednesday 10 May 2006 20:58, Jose Alberto Reguero wrote:
You need to find out how the card is flagging "key down". maybe the
card needs you to operate an output GPI pin to acknowledge the read.

Thanks, I found it. The attached patch work.
There is still a problem. When the card is working the gpio is changing
constantly, and generate a lot of debug output.

saa7134[0]/ir: build_key gpio=0x1c14f mask=0x2f200 data=24
saa7134[1]/ir: build_key gpio=0x3b3c5 mask=0x2f200 data=55

That looks like your mask is including too many bits. Normally, five data bits
are enough for a typical 20- to 30-button remote. You got eight bits there.

regards,
Peter

El Jueves, 11 de Mayo de 2006 12:39, Jose Alberto Reguero :
El Jueves, 11 de Mayo de 2006 11:56, Jose Alberto Reguero :
El M, 10 de Mayo de 2006 22:52, Peter Missel :
Wednesday 10 May 2006 20:58, Jose Alberto Reguero wrote:
You need to find out how the card is flagging "key down". maybe
the card needs you to operate an output GPI pin to acknowledge the
read.

Thanks, I found it. The attached patch work.
There is still a problem. When the card is working the gpio is
changing constantly, and generate a lot of debug output.

saa7134[0]/ir: build_key gpio=0x1c14f mask=0x2f200 data=24
saa7134[1]/ir: build_key gpio=0x3b3c5 mask=0x2f200 data=55

That looks like your mask is including too many bits. Normally, five
data bits are enough for a typical 20- to 30-button remote. You got
eight bits there.

regards,
Peter

The mask_keycode is good. The gpio bits that change are not part of the
mask. Data change because I have three cards([0], [1], [2]). In each card
the data is the same.
When the driver is loaded all works well. But when I start vdr (DVB-T)
some gpio bits are changing.

Thanks.
Jose Alberto

Here is another patch that solve the problem.
Thanks.
Jose Alberto

Sorry, I forgot to cc to linux-dvb.
Thanks.
Jose Alberto

El Jueves, 11 de Mayo de 2006 11:56, Jose Alberto Reguero :
El M, 10 de Mayo de 2006 22:52, Peter Missel :
Wednesday 10 May 2006 20:58, Jose Alberto Reguero wrote:
You need to find out how the card is flagging "key down". maybe
the card needs you to operate an output GPI pin to acknowledge the
read.

Thanks, I found it. The attached patch work.
There is still a problem. When the card is working the gpio is changing
constantly, and generate a lot of debug output.

saa7134[0]/ir: build_key gpio=0x1c14f mask=0x2f200 data=24
saa7134[1]/ir: build_key gpio=0x3b3c5 mask=0x2f200 data=55

That looks like your mask is including too many bits. Normally, five data
bits are enough for a typical 20- to 30-button remote. You got eight bits
there.

regards,
Peter

The mask_keycode is good. The gpio bits that change are not part of the
mask. Data change because I have three cards([0], [1], [2]). In each card
the data is the same.
When the driver is loaded all works well. But when I start vdr (DVB-T) some
gpio bits are changing.

Thanks.
Jose Alberto

Here is another patch that solve the problem.
Thanks.
Jose Alberto

El M, 10 de Mayo de 2006 22:52, Peter Missel :
Wednesday 10 May 2006 20:58, Jose Alberto Reguero wrote:
You need to find out how the card is flagging "key down". maybe the
card needs you to operate an output GPI pin to acknowledge the read.

Thanks, I found it. The attached patch work.
There is still a problem. When the card is working the gpio is changing
constantly, and generate a lot of debug output.

saa7134[0]/ir: build_key gpio=0x1c14f mask=0x2f200 data=24
saa7134[1]/ir: build_key gpio=0x3b3c5 mask=0x2f200 data=55

That looks like your mask is including too many bits. Normally, five data
bits are enough for a typical 20- to 30-button remote. You got eight bits
there.

regards,
Peter

The mask_keycode is good. The gpio bits that change are not part of the mask.
Data change because I have three cards([0], [1], [2]). In each card the data
is the same.
When the driver is loaded all works well. But when I start vdr (DVB-T) some
gpio bits are changing.

Thanks.
Jose Alberto