From: Tony Lindgren <tony@atomide.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>
Cc: Tero Kristo <t-kristo@ti.com>,
Grygorii Strashko <grygorii.strashko@ti.com>,
Aaro Koskinen <aaro.koskinen@iki.fi>, Keerthy <j-keerthy@ti.com>,
Peter Ujfalusi <peter.ujfalusi@ti.com>,
linux-gpio@vger.kernel.org,
Russell King <rmk+kernel@armlinux.org.uk>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] simplify idle gpio handling for omaps
Date: Mon, 25 Mar 2019 15:43:15 -0700 [thread overview]
Message-ID: <20190325224318.15076-1-tony@atomide.com> (raw)
Hi all,
Based on some comments from Grygorii I noticed that parts of old 24xx
errata 1.101 handling has become part of the GPIO idle handling over
the years. Here are few patches to clarify and simplify the handling
a bit.
Regards,
Tony
Tony Lindgren (3):
gpio: gpio-omap: limit errata 1.101 handling to wkup domain gpios only
gpio: gpio-omap: always scan for triggered non-wakeup capable
interrupts
gpio: gpio-omap: add check for off wake capable gpios
drivers/gpio/gpio-omap.c | 61 ++++++++++++++++++++++------------------
1 file changed, 33 insertions(+), 28 deletions(-)
--
2.21.0
next reply other threads:[~2019-03-25 22:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-25 22:43 Tony Lindgren [this message]
2019-03-25 22:43 ` [PATCH 1/3] gpio: gpio-omap: limit errata 1.101 handling to wkup domain gpios only Tony Lindgren
2019-03-25 22:43 ` [PATCH 2/3] gpio: gpio-omap: always scan for triggered non-wakeup capable interrupts Tony Lindgren
2019-03-25 22:43 ` [PATCH 3/3] gpio: gpio-omap: add check for off wake capable gpios Tony Lindgren
2019-03-27 13:29 ` [PATCH 0/3] simplify idle gpio handling for omaps Bartosz Golaszewski
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=20190325224318.15076-1-tony@atomide.com \
--to=tony@atomide.com \
--cc=aaro.koskinen@iki.fi \
--cc=bgolaszewski@baylibre.com \
--cc=grygorii.strashko@ti.com \
--cc=j-keerthy@ti.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=peter.ujfalusi@ti.com \
--cc=rmk+kernel@armlinux.org.uk \
--cc=t-kristo@ti.com \
/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).