From: Tony Lindgren <tony@atomide.com>
To: Andreas Kemnade <andreas@kemnade.info>
Cc: linux-omap@vger.kernel.org
Subject: Re: omap4-keypad mystery
Date: Fri, 18 Nov 2022 10:28:51 +0200 [thread overview]
Message-ID: <Y3dCQy3blizKD4NW@atomide.com> (raw)
In-Reply-To: <20221116231146.2edf8322@aktux>
* Andreas Kemnade <andreas@kemnade.info> [221116 22:02]:
> 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.
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
prev parent reply other threads:[~2022-11-18 8:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 22:11 omap4-keypad mystery Andreas Kemnade
2022-11-18 8:28 ` Tony Lindgren [this message]
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=Y3dCQy3blizKD4NW@atomide.com \
--to=tony@atomide.com \
--cc=andreas@kemnade.info \
--cc=linux-omap@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.