All of lore.kernel.org
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert+renesas@glider.be>
To: Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>
Cc: "Rafael J . Wysocki" <rjw@rjwysocki.net>,
	Kevin Hilman <khilman@kernel.org>,
	Ulf Hansson <ulf.hansson@linaro.org>,
	linux-renesas-soc@vger.kernel.org, linux-clk@vger.kernel.org,
	linux-pm@vger.kernel.org,
	Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [PATCH 0/3] clk: renesas: Set GENPD_FLAG_ALWAYS_ON for clock domain
Date: Fri, 16 Aug 2019 14:52:22 +0200	[thread overview]
Message-ID: <20190816125225.16061-1-geert+renesas@glider.be> (raw)

	Hi Mike, Stephen,

The Renesas Clock Domain drivers do not implement the
generic_pm_domain.power_{on,off}() callbacks, as the domains themselves
cannot be powered down.  Hence the domains should be marked as always-on
by setting the GENPD_FLAG_ALWAYS_ON flag.

This patch series that issue for R-Car M1A, RZ/A1, RZ/A2, and
RZ/N1 SoCs.
SH/R-Mobile SoCs are fixed in "[PATCH] soc: renesas: rmobile-sysc: Set
GENPD_FLAG_ALWAYS_ON for always-on domain"
(https://lore.kernel.org/linux-renesas-soc/20190816124106.15383-1-geert+renesas@glider.be/T/#u).
R-Car H1, Gen2, and Gen3 SoCs do not need a fix, as these SoCS use the
R-Car SYSC driver for Clock Domain creation, which already sets the
flag.

To be queued in clk-renesas for v5.4.

Thanks!

Geert Uytterhoeven (3):
  clk: renesas: mstp: Set GENPD_FLAG_ALWAYS_ON for clock domain
  clk: renesas: r9a06g032: Set GENPD_FLAG_ALWAYS_ON for clock domain
  clk: renesas: cpg-mssr: Set GENPD_FLAG_ALWAYS_ON for clock domain

 drivers/clk/renesas/clk-mstp.c         | 3 ++-
 drivers/clk/renesas/r9a06g032-clocks.c | 3 ++-
 drivers/clk/renesas/renesas-cpg-mssr.c | 3 ++-
 3 files changed, 6 insertions(+), 3 deletions(-)

-- 
2.17.1

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds

             reply	other threads:[~2019-08-16 12:52 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-16 12:52 Geert Uytterhoeven [this message]
2019-08-16 12:52 ` [PATCH 1/3] clk: renesas: mstp: Set GENPD_FLAG_ALWAYS_ON for clock domain Geert Uytterhoeven
2019-08-16 15:38   ` Simon Horman
2019-08-16 18:01   ` Stephen Boyd
2019-08-16 19:59     ` Geert Uytterhoeven
2019-08-17  3:48       ` Stephen Boyd
2019-08-18  8:27         ` Geert Uytterhoeven
2019-08-22 14:06           ` Ulf Hansson
2019-08-23  8:59             ` Geert Uytterhoeven
2019-08-16 12:52 ` [PATCH 2/3] clk: renesas: r9a06g032: " Geert Uytterhoeven
2019-08-16 15:39   ` Simon Horman
2019-08-16 12:52 ` [PATCH 3/3] clk: renesas: cpg-mssr: " Geert Uytterhoeven
2019-08-16 15:39   ` Simon Horman
2019-08-22 14:08 ` [PATCH 0/3] clk: renesas: " Ulf Hansson
2019-08-23  9:08   ` 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=20190816125225.16061-1-geert+renesas@glider.be \
    --to=geert+renesas@glider.be \
    --cc=khilman@kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=rjw@rjwysocki.net \
    --cc=sboyd@kernel.org \
    --cc=ulf.hansson@linaro.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.