From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Michael Grzeschik <m.grzeschik@pengutronix.de>
Cc: linux-input@vger.kernel.org
Subject: Re: [PATCH] Input: imx_keypad - reset the hardware before enabling
Date: Tue, 21 Aug 2012 22:06:16 -0700 [thread overview]
Message-ID: <20120822050616.GA20624@core.coreip.homeip.net> (raw)
In-Reply-To: <1345476893-4737-1-git-send-email-m.grzeschik@pengutronix.de>
On Mon, Aug 20, 2012 at 05:34:53PM +0200, Michael Grzeschik wrote:
> assert the hardware is correctly initialized before requesting the
> interrupt. Otherwise if a key was already touched since power-on the
> kernel enters an interrupt loop. To fix this issue we clear pending
> interrupt sources. We have to ensure to enable clks while changing the
> keypad registers.
>
> Signed-off-by: Michael Grzeschik <m.grzeschik@pengutronix.de>
Applied, thank you Michael.
--
Dmitry
next prev parent reply other threads:[~2012-08-22 5:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-20 15:34 [PATCH] Input: imx_keypad - reset the hardware before enabling Michael Grzeschik
2012-08-22 5:06 ` Dmitry Torokhov [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-08-20 21:34 Michael Grzeschik
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=20120822050616.GA20624@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=m.grzeschik@pengutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).