Skip to contentSkip to conversation

omap4-keypad mystery

DISCUSSION Andreas Kemnade 2 participants 2 messages Nov 16, 2022 – Nov 18, 2022

lore
Share & tools
lore
#0 lore raw

Hi,

I am investigating how to use the omap4 keypad driver in dts and I am quite confused. Nobody seems to add any pinmux to it. Why?

I muxed the rows0-3 and cols0-3 to MODE1 without any wakeup.

When I set /sys/bus/platform/devices/4a31c000.keypad/power/control to on I get keypad interrupts and events in evtest. but with it set to auto, nothing happens. Setting the rows pinmux to 0x4119 instead of 0x119 does not change anything.

Nobody seems to add provisions to wake up independently of the keypad hwmod which seems to be odd. I would expect interrupt-extended along with the keypad definitions.

Confused,
Andreas

#1 lore raw
Quoted 7 lines · Andreas Kemnade

Hi,

I am investigating how to use the omap4 keypad driver in dts and I am quite confused. Nobody seems to add any pinmux to it. Why?

I muxed the rows0-3 and cols0-3 to MODE1 without any wakeup.

Quoted 8 lines

When I set /sys/bus/platform/devices/4a31c000.keypad/power/control to on I get keypad interrupts and events in evtest. but with it set to auto, nothing happens. Setting the rows pinmux to 0x4119 instead of 0x119 does not change anything.

Nobody seems to add provisions to wake up independently of the keypad hwmod which seems to be odd. I would expect interrupt-extended along with the keypad definitions.

I think the keypad is in the wkup domain so it's always listening for events like gpio1 instance. So there should not be any need for padconf interrupts.

Regards,

Tony