All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Reichel <sebastian.reichel@collabora.co.uk>
To: Shawn Guo <shawnguo@kernel.org>,
	Sascha Hauer <kernel@pengutronix.de>,
	Fabio Estevam <fabio.estevam@nxp.com>,
	Will Deacon <will.deacon@arm.com>,
	Mark Rutland <mark.rutland@arm.com>
Cc: Russell King <linux@armlinux.org.uk>, Ian Ray <ian.ray@ge.com>,
	Nandor Han <nandor.han@ge.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, kernel@collabora.com
Subject: [PATCHv4 0/2] Improved perf support for imx53/ppd
Date: Mon, 12 Feb 2018 13:39:43 +0100	[thread overview]
Message-ID: <20180212123945.15732-1-sebastian.reichel@collabora.co.uk> (raw)

Hi,

This improves perf on imx53 by adding support for enabling the Secure
Debug Enable Register (SDER) SUNIDEN bit. This unlocks new
functionality:

ppd before patchset# perf stat -e cycles,instructions sleep 1 2>&1 | grep instructions
                 0      instructions              #    0.00  insn per cycle

ppd  after patchset# perf stat -e cycles,instructions sleep 1 2>&1 | grep instructions
            177864      instructions              #    0.05  insn per cycle

Changes since PATCHV3:
 * Use readl_relaxed instead of __raw_readl (and the same for writel)
 * Drop final return in void function
 * Add Reviewed-by from Fabio to 2nd patch
Changes since PATCHv2:
 * Always enable GPC_DBG_EN when kernel configuration allows using perf
   to allow cleanup of the arm-pmu driver.
Changes since PATCHv1:
 * Update DTS patch to reference imx53.dtsi's pmu node
 * Remove a superfluous newline in first patch

-- Sebastian

Sebastian Reichel (2):
  ARM: imx53: add secure-reg-access support for PMU
  ARM: dts: imx53: PPD: Enable secure-reg-access

 arch/arm/boot/dts/imx53-ppd.dts |  4 ++++
 arch/arm/boot/dts/imx53.dtsi    |  2 +-
 arch/arm/mach-imx/mach-imx53.c  | 39 ++++++++++++++++++++++++++++++++++++++-
 3 files changed, 43 insertions(+), 2 deletions(-)

-- 
2.15.1

WARNING: multiple messages have this Message-ID (diff)
From: sebastian.reichel@collabora.co.uk (Sebastian Reichel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv4 0/2] Improved perf support for imx53/ppd
Date: Mon, 12 Feb 2018 13:39:43 +0100	[thread overview]
Message-ID: <20180212123945.15732-1-sebastian.reichel@collabora.co.uk> (raw)

Hi,

This improves perf on imx53 by adding support for enabling the Secure
Debug Enable Register (SDER) SUNIDEN bit. This unlocks new
functionality:

ppd before patchset# perf stat -e cycles,instructions sleep 1 2>&1 | grep instructions
                 0      instructions              #    0.00  insn per cycle

ppd  after patchset# perf stat -e cycles,instructions sleep 1 2>&1 | grep instructions
            177864      instructions              #    0.05  insn per cycle

Changes since PATCHV3:
 * Use readl_relaxed instead of __raw_readl (and the same for writel)
 * Drop final return in void function
 * Add Reviewed-by from Fabio to 2nd patch
Changes since PATCHv2:
 * Always enable GPC_DBG_EN when kernel configuration allows using perf
   to allow cleanup of the arm-pmu driver.
Changes since PATCHv1:
 * Update DTS patch to reference imx53.dtsi's pmu node
 * Remove a superfluous newline in first patch

-- Sebastian

Sebastian Reichel (2):
  ARM: imx53: add secure-reg-access support for PMU
  ARM: dts: imx53: PPD: Enable secure-reg-access

 arch/arm/boot/dts/imx53-ppd.dts |  4 ++++
 arch/arm/boot/dts/imx53.dtsi    |  2 +-
 arch/arm/mach-imx/mach-imx53.c  | 39 ++++++++++++++++++++++++++++++++++++++-
 3 files changed, 43 insertions(+), 2 deletions(-)

-- 
2.15.1

             reply	other threads:[~2018-02-12 12:39 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-12 12:39 Sebastian Reichel [this message]
2018-02-12 12:39 ` [PATCHv4 0/2] Improved perf support for imx53/ppd Sebastian Reichel
2018-02-12 12:39 ` [PATCHv4 1/2] ARM: imx53: add secure-reg-access support for PMU Sebastian Reichel
2018-02-12 12:39   ` Sebastian Reichel
2018-02-12 12:48   ` Fabio Estevam
2018-02-12 12:48     ` Fabio Estevam
2018-02-24  7:45   ` Shawn Guo
2018-02-24  7:45     ` Shawn Guo
2018-02-26 13:47     ` Sebastian Reichel
2018-02-26 13:47       ` Sebastian Reichel
2018-02-27  1:10       ` Shawn Guo
2018-02-27  1:10         ` Shawn Guo
2018-02-27 10:17         ` Sebastian Reichel
2018-02-27 10:17           ` Sebastian Reichel
2018-05-25 15:45           ` Sebastian Reichel
2018-05-25 15:45             ` Sebastian Reichel
2018-05-28  2:26           ` Shawn Guo
2018-05-28  2:26             ` Shawn Guo
2018-05-28  6:41             ` Sebastian Reichel
2018-05-28  6:41               ` Sebastian Reichel
2018-05-28  7:20               ` Shawn Guo
2018-05-28  7:20                 ` Shawn Guo
2018-05-28 15:50                 ` Sebastian Reichel
2018-05-28 15:50                   ` Sebastian Reichel
2018-06-18  4:00       ` Fabio Estevam
2018-06-18  4:00         ` Fabio Estevam
2018-02-12 12:39 ` [PATCHv4 2/2] ARM: dts: imx53: PPD: Enable secure-reg-access Sebastian Reichel
2018-02-12 12:39   ` Sebastian Reichel

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=20180212123945.15732-1-sebastian.reichel@collabora.co.uk \
    --to=sebastian.reichel@collabora.co.uk \
    --cc=fabio.estevam@nxp.com \
    --cc=ian.ray@ge.com \
    --cc=kernel@collabora.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=mark.rutland@arm.com \
    --cc=nandor.han@ge.com \
    --cc=shawnguo@kernel.org \
    --cc=will.deacon@arm.com \
    /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.