From: Tony Lindgren <tony@atomide.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Alexandre Courbot <gnurou@gmail.com>
Cc: linux-gpio@vger.kernel.org, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: [PATCHv2 0/3] omap gpio add level idle, cpu_pm and drop runtime_irq_safe
Date: Thu, 20 Sep 2018 12:35:29 -0700 [thread overview]
Message-ID: <20180920193532.7714-1-tony@atomide.com> (raw)
Hi,
Here's v2 of the patches to add support for omap4 and later level interrupt
idle support, get rid of the custom pm calls, and finally after these we can
drop pm_runtime_irq_safe().
Linus, assuming people are happy with these, I'd appreciate an immutable branch
with these in case we run into merge conflicts for arch/arm/mach-omap2 changes.
Regards,
Tony
Changes since v1:
- Fix issue noted in v1 set and update comments accordingly
- Don't call pm_runtime from cpu_pm to avoid further dependencies to
pm_runtime_irq_safe() as discussed offline with Grygorii
- Add a patch to drop pm_runtime_irq_safe() as it's no longer needed
Tony Lindgren (3):
gpio: omap: Add level wakeup handling for omap4 based SoCs
gpio: omap: Remove custom PM calls and use cpu_pm instead
gpio: omap: Get rid of pm_runtime_irq_safe()
arch/arm/mach-omap2/pm24xx.c | 7 +-
arch/arm/mach-omap2/pm34xx.c | 14 +-
drivers/gpio/gpio-omap.c | 331 ++++++++++++++++--------
include/linux/platform_data/gpio-omap.h | 15 +-
4 files changed, 237 insertions(+), 130 deletions(-)
--
2.19.0
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv2 0/3] omap gpio add level idle, cpu_pm and drop runtime_irq_safe
Date: Thu, 20 Sep 2018 12:35:29 -0700 [thread overview]
Message-ID: <20180920193532.7714-1-tony@atomide.com> (raw)
Hi,
Here's v2 of the patches to add support for omap4 and later level interrupt
idle support, get rid of the custom pm calls, and finally after these we can
drop pm_runtime_irq_safe().
Linus, assuming people are happy with these, I'd appreciate an immutable branch
with these in case we run into merge conflicts for arch/arm/mach-omap2 changes.
Regards,
Tony
Changes since v1:
- Fix issue noted in v1 set and update comments accordingly
- Don't call pm_runtime from cpu_pm to avoid further dependencies to
pm_runtime_irq_safe() as discussed offline with Grygorii
- Add a patch to drop pm_runtime_irq_safe() as it's no longer needed
Tony Lindgren (3):
gpio: omap: Add level wakeup handling for omap4 based SoCs
gpio: omap: Remove custom PM calls and use cpu_pm instead
gpio: omap: Get rid of pm_runtime_irq_safe()
arch/arm/mach-omap2/pm24xx.c | 7 +-
arch/arm/mach-omap2/pm34xx.c | 14 +-
drivers/gpio/gpio-omap.c | 331 ++++++++++++++++--------
include/linux/platform_data/gpio-omap.h | 15 +-
4 files changed, 237 insertions(+), 130 deletions(-)
--
2.19.0
next reply other threads:[~2018-09-20 19:35 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-20 19:35 Tony Lindgren [this message]
2018-09-20 19:35 ` [PATCHv2 0/3] omap gpio add level idle, cpu_pm and drop runtime_irq_safe Tony Lindgren
2018-09-20 19:35 ` [PATCH 1/3] gpio: omap: Add level wakeup handling for omap4 based SoCs Tony Lindgren
2018-09-20 19:35 ` Tony Lindgren
2018-09-21 5:45 ` Keerthy
2018-09-21 5:45 ` Keerthy
2018-09-20 19:35 ` [PATCH 2/3] gpio: omap: Remove custom PM calls and use cpu_pm instead Tony Lindgren
2018-09-20 19:35 ` Tony Lindgren
2018-09-20 23:01 ` Grygorii Strashko
2018-09-20 23:01 ` Grygorii Strashko
2018-09-20 23:47 ` Tony Lindgren
2018-09-20 23:47 ` Tony Lindgren
2018-09-21 0:58 ` Grygorii Strashko
2018-09-21 0:58 ` Grygorii Strashko
2018-09-20 19:35 ` [PATCH 3/3] gpio: omap: Get rid of pm_runtime_irq_safe() Tony Lindgren
2018-09-20 19:35 ` Tony Lindgren
2018-09-22 3:12 ` [PATCHv2 0/3] omap gpio add level idle, cpu_pm and drop runtime_irq_safe Grygorii Strashko
2018-09-22 3:12 ` Grygorii Strashko
2018-09-25 6:53 ` Linus Walleij
2018-09-25 6:53 ` Linus Walleij
2018-09-25 14:35 ` Tony Lindgren
2018-09-25 14:35 ` Tony Lindgren
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=20180920193532.7714-1-tony@atomide.com \
--to=tony@atomide.com \
--cc=gnurou@gmail.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 \
/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.