From: Shawn Guo <shawnguo@kernel.org>
To: Sebastian Reichel <sebastian.reichel@collabora.co.uk>
Cc: Sascha Hauer <kernel@pengutronix.de>, Frank Li <Frank.li@nxp.com>,
Fabio Estevam <fabio.estevam@nxp.com>, Ian Ray <ian.ray@ge.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: dts: imx6q-bx50v3: Enable secure-reg-access
Date: Fri, 2 Feb 2018 15:18:20 +0800 [thread overview]
Message-ID: <20180202071819.GE25699@dragon> (raw)
In-Reply-To: <20180115160722.17206-1-sebastian.reichel@collabora.co.uk>
+ Frank
On Mon, Jan 15, 2018 at 05:07:22PM +0100, Sebastian Reichel wrote:
> From: Peter Senna Tschudin <peter.senna@collabora.com>
>
> Add secure-reg-access on device tree include file for Bx50 devices
> to enable PMU and hardware counters for perf.
>
> Signed-off-by: Peter Senna Tschudin <peter.senna@collabora.com>
> Signed-off-by: Sebastian Reichel <sebastian.reichel@collabora.co.uk>
> ---
> arch/arm/boot/dts/imx6q-bx50v3.dtsi | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/arch/arm/boot/dts/imx6q-bx50v3.dtsi b/arch/arm/boot/dts/imx6q-bx50v3.dtsi
> index 86cfd4481e72..ccaaee83e2fa 100644
> --- a/arch/arm/boot/dts/imx6q-bx50v3.dtsi
> +++ b/arch/arm/boot/dts/imx6q-bx50v3.dtsi
> @@ -43,6 +43,13 @@
> #include "imx6q-ba16.dtsi"
>
> / {
> + soc {
> + pmu {
> + compatible = "arm,cortex-a9-pmu";
> + secure-reg-access;
I'm not sure this could be a board level configuration. Shouldn't this
property just be added into pmu node in imx6qdl.dtsi?
Shawn
> + };
> + };
> +
> clocks {
> mclk: clock@0 {
> compatible = "fixed-clock";
> --
> 2.15.1
>
next prev parent reply other threads:[~2018-02-02 7:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-15 16:07 [PATCH] ARM: dts: imx6q-bx50v3: Enable secure-reg-access Sebastian Reichel
2018-02-02 7:18 ` Shawn Guo [this message]
2018-02-02 11:10 ` Sebastian Reichel
2018-02-05 5:27 ` Shawn Guo
2018-02-05 17:08 ` [PATCHv2] " Sebastian Reichel
[not found] ` <20180205170840.14045-1-sebastian.reichel-ZGY8ohtN/8pPYcu2f3hruQ@public.gmane.org>
2018-02-05 17:17 ` Fabio Estevam
2018-02-08 6:44 ` Shawn Guo
2018-02-02 15:33 ` [PATCH] " Frank Li
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=20180202071819.GE25699@dragon \
--to=shawnguo@kernel.org \
--cc=Frank.li@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=fabio.estevam@nxp.com \
--cc=ian.ray@ge.com \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=sebastian.reichel@collabora.co.uk \
/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).