From: Peter De Schrijver <pdeschrijver@nvidia.com>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Dirk Behme" <dirk.behme@gmail.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Mark Rutland" <mark.rutland@arm.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"Ulf Hansson" <ulf.hansson@linaro.org>,
"Dirk Behme" <dirk.behme@de.bosch.com>,
"Linux PM list" <linux-pm@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
"Michael Turquette" <mturquette@baylibre.com>,
"Stephen Boyd" <sboyd@codeaurora.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
"Geert Uytterhoeven" <geert@linux-m68k.org>,
"Kevin Hilman" <khilman@baylibre.com>,
linux-clk <linux-clk@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: Clocks used by another OS/CPU (was: Re: [RFC PATCH] clk: renesas: cpg-mssr: Add interface for critical core clocks)
Date: Tue, 4 Jul 2017 10:31:37 +0300 [thread overview]
Message-ID: <20170704073137.GG14819@tbergstrom-lnx.Nvidia.com> (raw)
In-Reply-To: <8d255a76-babe-312d-15b3-3474969f2410@arm.com>
On Mon, Jul 03, 2017 at 10:17:22AM +0100, Sudeep Holla wrote:
>
>
> On 01/07/17 19:14, Uwe Kleine-König wrote:
> > Hello,
> >
> > On Sat, Jul 01, 2017 at 07:02:48AM +0200, Dirk Behme wrote:
>
> [...]
>
> >>
> >>
> >> The other problem is security related. If, at all, you have to do it the
> >> other way around, then:
> >>
> >> Make Linux a consumer of the other CPU's (trusted/trustzone/whatever
> >> secured) OS clock driver.
>
> Yes, that's better and is getting common on newer platforms. They have
> separate M-class(or even low A-class e.g. A5/A7) processors to handle
> all the system management.
>
> The new ARM SCMI specification[0][1] is designed to standardize the
> interface. It covers the clocks in clock protocol.
>
Yes, however this doesn't exist on older SoCs which still have multiple CPU's
Peter.
WARNING: multiple messages have this Message-ID (diff)
From: Peter De Schrijver <pdeschrijver@nvidia.com>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Dirk Behme" <dirk.behme@gmail.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Mark Rutland" <mark.rutland@arm.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"Ulf Hansson" <ulf.hansson@linaro.org>,
"Dirk Behme" <dirk.behme@de.bosch.com>,
"Linux PM list" <linux-pm@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
"Michael Turquette" <mturquette@baylibre.com>,
"Stephen Boyd" <sboyd@codeaurora.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
"Geert Uytterhoeven" <geert@linux-m68k.org>,
"Kevin Hilman" <khilman@baylibre.com>,
linux-clk <linux-clk@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: Clocks used by another OS/CPU (was: Re: [RFC PATCH] clk: renesas: cpg-mssr: Add interface for critical core clocks)
Date: Tue, 4 Jul 2017 10:31:37 +0300 [thread overview]
Message-ID: <20170704073137.GG14819@tbergstrom-lnx.Nvidia.com> (raw)
In-Reply-To: <8d255a76-babe-312d-15b3-3474969f2410@arm.com>
On Mon, Jul 03, 2017 at 10:17:22AM +0100, Sudeep Holla wrote:
>
>
> On 01/07/17 19:14, Uwe Kleine-K�nig wrote:
> > Hello,
> >
> > On Sat, Jul 01, 2017 at 07:02:48AM +0200, Dirk Behme wrote:
>
> [...]
>
> >>
> >>
> >> The other problem is security related. If, at all, you have to do it the
> >> other way around, then:
> >>
> >> Make Linux a consumer of the other CPU's (trusted/trustzone/whatever
> >> secured) OS clock driver.
>
> Yes, that's better and is getting common on newer platforms. They have
> separate M-class(or even low A-class e.g. A5/A7) processors to handle
> all the system management.
>
> The new ARM SCMI specification[0][1] is designed to standardize the
> interface. It covers the clocks in clock protocol.
>
Yes, however this doesn't exist on older SoCs which still have multiple CPU's
Peter.
WARNING: multiple messages have this Message-ID (diff)
From: Peter De Schrijver <pdeschrijver@nvidia.com>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Dirk Behme" <dirk.behme@gmail.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Mark Rutland" <mark.rutland@arm.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"Ulf Hansson" <ulf.hansson@linaro.org>,
"Dirk Behme" <dirk.behme@de.bosch.com>,
"Linux PM list" <linux-pm@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
"Michael Turquette" <mturquette@baylibre.com>,
"Stephen Boyd" <sboyd@codeaurora.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
"Geert Uytterhoeven" <geert@linux-m68k.org>,
"Kevin Hilman" <khilman@baylibre.com>,
linux-clk <linux-clk@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: Clocks used by another OS/CPU (was: Re: [RFC PATCH] clk: renesas: cpg-mssr: Add interface for critical core clocks)
Date: Tue, 4 Jul 2017 10:31:37 +0300 [thread overview]
Message-ID: <20170704073137.GG14819@tbergstrom-lnx.Nvidia.com> (raw)
In-Reply-To: <8d255a76-babe-312d-15b3-3474969f2410@arm.com>
On Mon, Jul 03, 2017 at 10:17:22AM +0100, Sudeep Holla wrote:
>=20
>=20
> On 01/07/17 19:14, Uwe Kleine-K=F6nig wrote:
> > Hello,
> >=20
> > On Sat, Jul 01, 2017 at 07:02:48AM +0200, Dirk Behme wrote:
>=20
> [...]
>=20
> >>
> >>
> >> The other problem is security related. If, at all, you have to do it t=
he
> >> other way around, then:
> >>
> >> Make Linux a consumer of the other CPU's (trusted/trustzone/whatever
> >> secured) OS clock driver.
>=20
> Yes, that's better and is getting common on newer platforms. They have
> separate M-class(or even low A-class e.g. A5/A7) processors to handle
> all the system management.
>=20
> The new ARM SCMI specification[0][1] is designed to standardize the
> interface. It covers the clocks in clock protocol.
>=20
Yes, however this doesn't exist on older SoCs which still have multiple CPU=
's
Peter.
WARNING: multiple messages have this Message-ID (diff)
From: pdeschrijver@nvidia.com (Peter De Schrijver)
To: linux-arm-kernel@lists.infradead.org
Subject: Clocks used by another OS/CPU (was: Re: [RFC PATCH] clk: renesas: cpg-mssr: Add interface for critical core clocks)
Date: Tue, 4 Jul 2017 10:31:37 +0300 [thread overview]
Message-ID: <20170704073137.GG14819@tbergstrom-lnx.Nvidia.com> (raw)
In-Reply-To: <8d255a76-babe-312d-15b3-3474969f2410@arm.com>
On Mon, Jul 03, 2017 at 10:17:22AM +0100, Sudeep Holla wrote:
>
>
> On 01/07/17 19:14, Uwe Kleine-K?nig wrote:
> > Hello,
> >
> > On Sat, Jul 01, 2017 at 07:02:48AM +0200, Dirk Behme wrote:
>
> [...]
>
> >>
> >>
> >> The other problem is security related. If, at all, you have to do it the
> >> other way around, then:
> >>
> >> Make Linux a consumer of the other CPU's (trusted/trustzone/whatever
> >> secured) OS clock driver.
>
> Yes, that's better and is getting common on newer platforms. They have
> separate M-class(or even low A-class e.g. A5/A7) processors to handle
> all the system management.
>
> The new ARM SCMI specification[0][1] is designed to standardize the
> interface. It covers the clocks in clock protocol.
>
Yes, however this doesn't exist on older SoCs which still have multiple CPU's
Peter.
next prev parent reply other threads:[~2017-07-04 7:31 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 ` Clocks used by another OS/CPU Dirk Behme
2017-06-29 12:07 ` 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 [this message]
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=20170704073137.GG14819@tbergstrom-lnx.Nvidia.com \
--to=pdeschrijver@nvidia.com \
--cc=devicetree@vger.kernel.org \
--cc=dirk.behme@de.bosch.com \
--cc=dirk.behme@gmail.com \
--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=sudeep.holla@arm.com \
--cc=u.kleine-koenig@pengutronix.de \
--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.