From: Ulf Hansson <ulf.hansson@linaro.org>
To: "Rafael J . Wysocki" <rjw@rjwysocki.net>, linux-pm@vger.kernel.org
Cc: Thomas Gleixner <tglx@linutronix.de>,
Jason Cooper <jason@lakedaemon.net>,
Marc Zyngier <marc.zyngier@arm.com>,
Linus Walleij <linus.walleij@linaro.org>,
Simon Horman <horms@verge.net.au>,
Niklas Soderlund <niklas.soderlund+renesas@ragnatech.se>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Ulf Hansson <ulf.hansson@linaro.org>,
linux-renesas-soc@vger.kernel.org, linux-gpio@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/3] renesas: irqchip: Use WAKEUP_PATH driver PM flag
Date: Fri, 29 Dec 2017 14:31:41 +0100 [thread overview]
Message-ID: <1514554304-18989-1-git-send-email-ulf.hansson@linaro.org> (raw)
From: Geert Uytterhoeven <geert+renesas@glider.be>
Changes in v2: [By Ulf Hansson]
- I have picked up the series from Geert [1] and converted it into use
the WAKEUP_PATH driver PM flag. This includes some minor changes to each
patch and updates to the changelogs.
- An important note, the WAKEUP_PATH driver PM flag is introduced in a
separate series [2], not yet applied, so @subject series depends on it.
- One more note, two of the patches has a checkpatch error, however I
did not fix them, becuase I think that should be done separate.
[1]
https://lkml.org/lkml/2017/11/9/382
[2]
https://marc.info/?l=linux-pm&m=151454744124661&w=2
More information below, picked from Geert's previous cover letter.
Kind regards
Uffe
Hi all,
If an interrupt controller in a Renesas ARM SoC is part of a Clock
Domain, and it is part of the wakeup path, it must be kept active during
system suspend.
Currently this is handled in all interrupt controller drivers by
explicitly increasing the use count of the module clock when the device
is part of the wakeup path. However, this explicit clock handling is
merely a workaround for a failure to properly communicate wakeup
information to the device core.
Hence this series fixes the affected drivers by setting the devices'
power.wakeup_path fields instead, to indicate they are part of the
wakeup path. Depending on the PM Domain's active_wakeup configuration,
the genpd core code will keep the device enabled (and the clock running)
during system suspend when needed.
Note that most of these patches depend on the series "[PATCH v2 0/3] PM
/ Domain: renesas: Fix active wakeup behavior", hence they should not be
applied yet.
This has been tested on r8a73a4/ape6evm, r8a7740/armadillo,
r8a7791/koelsch, r8a7795/salvator-x and -xs, r8a7796/salvator-x, and
sh73a0/kzm9g.
Thanks for your comments!
Geert Uytterhoeven (3):
irqchip/renesas-intc-irqpin: Use WAKEUP_PATH driver PM flag
irqchip/renesas-irqc: Use WAKEUP_PATH driver PM flag
gpio: rcar: Use WAKEUP_PATH driver PM flag
drivers/gpio/gpio-rcar.c | 40 +++++++++++------------------
drivers/irqchip/irq-renesas-intc-irqpin.c | 42 +++++++++++--------------------
drivers/irqchip/irq-renesas-irqc.c | 32 +++++++++++------------
3 files changed, 45 insertions(+), 69 deletions(-)
--
2.7.4
next reply other threads:[~2017-12-29 13:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-29 13:31 Ulf Hansson [this message]
2017-12-29 13:31 ` [PATCH v2 1/3] irqchip/renesas-intc-irqpin: Use WAKEUP_PATH driver PM flag Ulf Hansson
2017-12-31 0:58 ` Rafael J. Wysocki
2017-12-29 13:31 ` [PATCH v2 2/3] irqchip/renesas-irqc: " Ulf Hansson
2017-12-29 13:31 ` [PATCH v2 3/3] gpio: rcar: " Ulf Hansson
2018-01-02 9:27 ` Linus Walleij
2018-01-02 9:37 ` Geert Uytterhoeven
2018-01-02 10:26 ` Rafael J. Wysocki
2018-01-02 10:32 ` Rafael J. Wysocki
2018-01-02 10:44 ` Geert Uytterhoeven
2018-01-02 10:48 ` Rafael J. Wysocki
2018-01-02 12:53 ` Ulf Hansson
2018-01-02 13:53 ` Geert Uytterhoeven
2018-01-02 15:41 ` Ulf Hansson
2018-01-02 13:02 ` Ulf Hansson
2018-01-02 13:57 ` Geert Uytterhoeven
2017-12-31 0:56 ` [PATCH v2 0/3] renesas: irqchip: " Rafael J. Wysocki
2017-12-31 9:22 ` Geert Uytterhoeven
2017-12-31 11:47 ` Rafael J. Wysocki
2018-01-05 9:16 ` Geert Uytterhoeven
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=1514554304-18989-1-git-send-email-ulf.hansson@linaro.org \
--to=ulf.hansson@linaro.org \
--cc=geert+renesas@glider.be \
--cc=horms@verge.net.au \
--cc=jason@lakedaemon.net \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=niklas.soderlund+renesas@ragnatech.se \
--cc=rjw@rjwysocki.net \
--cc=tglx@linutronix.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).