All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dirk Behme <dirk.behme@de.bosch.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@codeaurora.org>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Ulf Hansson <ulf.hansson@linaro.org>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Kevin Hilman <khilman@baylibre.com>,
	Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
	linux-clk <linux-clk@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	Linux PM list <linux-pm@vger.kernel.org>
Subject: Re: Clocks used by another OS/CPU
Date: Thu, 29 Jun 2017 14:07:38 +0200	[thread overview]
Message-ID: <50911172-8fa1-8341-0ed0-d40f00d9392c@de.bosch.com> (raw)
In-Reply-To: <CAMuHMdWRadUCZUycUW3dKJhS__aRRVbV1tXo0umUQ7KHOYQMoQ@mail.gmail.com>

On 29.06.2017 13:56, Geert Uytterhoeven wrote:
> Hi Dirk,
> 
> On Thu, Jun 29, 2017 at 11:27 AM, Geert Uytterhoeven
> <geert@linux-m68k.org> wrote:
>> CC clock, ARM, DT, PM people
>>
>> TL;DR: Clocks may be in use by another CPU not running Linux, while Linux
>> disables them as being unused.
> 
>> Of course this is not limited to clocks, but also to e.g. PM domains.
> 
> BTW, how do you prevent Linux from powering down the CR7 PM domain,
> which contains the Cortex R7?


The idea is

--- a/drivers/soc/renesas/r8a7795-sysc.c
+++ b/drivers/soc/renesas/r8a7795-sysc.c
@@ -38,7 +38,8 @@ static const struct rcar_sysc_area r8a7795_areas[] 
__initconst = {
  	{ "ca53-cpu3",	0x200, 3, R8A7795_PD_CA53_CPU3,	R8A7795_PD_CA53_SCU,
  	  PD_CPU_NOCR },
  	{ "a3vp",	0x340, 0, R8A7795_PD_A3VP,	R8A7795_PD_ALWAYS_ON },
-	{ "cr7",	0x240, 0, R8A7795_PD_CR7,	R8A7795_PD_ALWAYS_ON },
+	{ "cr7",	0x240, 0, R8A7795_PD_CR7,	R8A7795_PD_ALWAYS_ON,
+	  PD_CPU_NOCR },
  	{ "a3vc",	0x380, 0, R8A7795_PD_A3VC,	R8A7795_PD_ALWAYS_ON },
  	{ "a2vc0",	0x3c0, 0, R8A7795_PD_A2VC0,	R8A7795_PD_A3VC },
  	{ "a2vc1",	0x3c0, 1, R8A7795_PD_A2VC1,	R8A7795_PD_A3VC },


Not finally tested, though.

Best regards

Dirk

WARNING: multiple messages have this Message-ID (diff)
From: dirk.behme@de.bosch.com (Dirk Behme)
To: linux-arm-kernel@lists.infradead.org
Subject: Clocks used by another OS/CPU
Date: Thu, 29 Jun 2017 14:07:38 +0200	[thread overview]
Message-ID: <50911172-8fa1-8341-0ed0-d40f00d9392c@de.bosch.com> (raw)
In-Reply-To: <CAMuHMdWRadUCZUycUW3dKJhS__aRRVbV1tXo0umUQ7KHOYQMoQ@mail.gmail.com>

On 29.06.2017 13:56, Geert Uytterhoeven wrote:
> Hi Dirk,
> 
> On Thu, Jun 29, 2017 at 11:27 AM, Geert Uytterhoeven
> <geert@linux-m68k.org> wrote:
>> CC clock, ARM, DT, PM people
>>
>> TL;DR: Clocks may be in use by another CPU not running Linux, while Linux
>> disables them as being unused.
> 
>> Of course this is not limited to clocks, but also to e.g. PM domains.
> 
> BTW, how do you prevent Linux from powering down the CR7 PM domain,
> which contains the Cortex R7?


The idea is

--- a/drivers/soc/renesas/r8a7795-sysc.c
+++ b/drivers/soc/renesas/r8a7795-sysc.c
@@ -38,7 +38,8 @@ static const struct rcar_sysc_area r8a7795_areas[] 
__initconst = {
  	{ "ca53-cpu3",	0x200, 3, R8A7795_PD_CA53_CPU3,	R8A7795_PD_CA53_SCU,
  	  PD_CPU_NOCR },
  	{ "a3vp",	0x340, 0, R8A7795_PD_A3VP,	R8A7795_PD_ALWAYS_ON },
-	{ "cr7",	0x240, 0, R8A7795_PD_CR7,	R8A7795_PD_ALWAYS_ON },
+	{ "cr7",	0x240, 0, R8A7795_PD_CR7,	R8A7795_PD_ALWAYS_ON,
+	  PD_CPU_NOCR },
  	{ "a3vc",	0x380, 0, R8A7795_PD_A3VC,	R8A7795_PD_ALWAYS_ON },
  	{ "a2vc0",	0x3c0, 0, R8A7795_PD_A2VC0,	R8A7795_PD_A3VC },
  	{ "a2vc1",	0x3c0, 1, R8A7795_PD_A2VC1,	R8A7795_PD_A3VC },


Not finally tested, though.

Best regards

Dirk

  reply	other threads:[~2017-06-29 12:07 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-29  9:27 Clocks used by another OS/CPU (was: Re: [RFC PATCH] clk: renesas: cpg-mssr: Add interface for critical core clocks) Geert Uytterhoeven
2017-06-29  9:27 ` Geert Uytterhoeven
2017-06-29 10:28 ` Dirk Behme
2017-06-29 10:28   ` Dirk Behme
2017-06-29 11:18   ` Geert Uytterhoeven
2017-06-29 11:18     ` Geert Uytterhoeven
2017-06-29 13:18     ` Clocks used by another OS/CPU Dirk Behme
2017-06-29 13:18       ` Dirk Behme
2017-06-29 13:22       ` Geert Uytterhoeven
2017-06-29 13:22         ` Geert Uytterhoeven
     [not found] ` <CAMuHMdW9+CNTTOVO4SRRUxuz3ajLbY2j1uG8b_RpHX52NPwXrQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-06-29 11:56   ` Clocks used by another OS/CPU (was: Re: [RFC PATCH] clk: renesas: cpg-mssr: Add interface for critical core clocks) Geert Uytterhoeven
2017-06-29 11:56     ` Geert Uytterhoeven
2017-06-29 11:56     ` Geert Uytterhoeven
2017-06-29 12:07     ` Dirk Behme [this message]
2017-06-29 12:07       ` Clocks used by another OS/CPU Dirk Behme
2017-06-29 12:45       ` Geert Uytterhoeven
2017-06-29 12:45         ` Geert Uytterhoeven
2017-06-29 12:55         ` Dirk Behme
2017-06-29 12:55           ` Dirk Behme
2017-06-30  8:02 ` Clocks used by another OS/CPU (was: Re: [RFC PATCH] clk: renesas: cpg-mssr: Add interface for critical core clocks) Peter De Schrijver
2017-06-30  8:02   ` Peter De Schrijver
2017-06-30 15:58 ` Rob Herring
2017-06-30 15:58   ` Rob Herring
2017-06-30 20:24   ` Uwe Kleine-König
2017-06-30 20:24     ` Uwe Kleine-König
2017-06-30 20:24     ` Uwe Kleine-König
     [not found]     ` <20170630202453.eh6vaehkap3as4np-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2017-07-01  5:02       ` Dirk Behme
2017-07-01  5:02         ` Dirk Behme
2017-07-01  5:02         ` Dirk Behme
2017-07-01 18:14         ` Uwe Kleine-König
2017-07-01 18:14           ` Uwe Kleine-König
2017-07-01 18:14           ` Uwe Kleine-König
2017-07-02  5:48           ` Dirk Behme
2017-07-02  5:48             ` Dirk Behme
     [not found]             ` <6098d579-f206-5a23-bbfc-ac13e0448479-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-07-02  9:23               ` Uwe Kleine-König
2017-07-02  9:23                 ` Uwe Kleine-König
2017-07-02  9:23                 ` Uwe Kleine-König
2017-07-02  9:23                 ` Uwe Kleine-König
2017-07-03  7:40                 ` Geert Uytterhoeven
2017-07-03  7:40                   ` Geert Uytterhoeven
2017-07-03  7:40                   ` Geert Uytterhoeven
     [not found]           ` <20170701181408.yuocymwtj5dgt74d-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2017-07-03  9:17             ` Sudeep Holla
2017-07-03  9:17               ` Sudeep Holla
2017-07-03  9:17               ` Sudeep Holla
2017-07-04  7:31               ` Peter De Schrijver
2017-07-04  7:31                 ` Peter De Schrijver
2017-07-04  7:31                 ` Peter De Schrijver
2017-07-04  7:31                 ` Peter De Schrijver
2017-07-04  8:49                 ` Sudeep Holla
2017-07-04  8:49                   ` Sudeep Holla
2017-07-05  7:25                   ` Peter De Schrijver
2017-07-05  7:25                     ` Peter De Schrijver
2017-07-05  7:25                     ` Peter De Schrijver
2017-07-05  7:25                     ` Peter De Schrijver

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=50911172-8fa1-8341-0ed0-d40f00d9392c@de.bosch.com \
    --to=dirk.behme@de.bosch.com \
    --cc=devicetree@vger.kernel.org \
    --cc=geert@linux-m68k.org \
    --cc=khilman@baylibre.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mturquette@baylibre.com \
    --cc=rjw@rjwysocki.net \
    --cc=robh+dt@kernel.org \
    --cc=sboyd@codeaurora.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.