From: Lukasz Luba <l.luba@partner.samsung.com>
To: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pm@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Cc: b.zolnierkie@samsung.com, krzk@kernel.org, robh+dt@kernel.org,
mark.rutland@arm.com, cw00.choi@samsung.com,
kyungmin.park@samsung.com, m.szyprowski@samsung.com,
s.nawrocki@samsung.com, myungjoo.ham@samsung.com,
kgene@kernel.org, l.luba@partner.samsung.com
Subject: [PATCH 0/3] Exynos Performance Monitoring Counters enhancements
Date: Wed, 17 Apr 2019 09:48:05 +0200 [thread overview]
Message-ID: <1555487288-4777-1-git-send-email-l.luba@partner.samsung.com> (raw)
In-Reply-To: <CGME20190417074829eucas1p234e664f9bf295eca8d2fad6ba953f37c@eucas1p2.samsung.com>
Hi all,
This patch set extends PPMU on Samsung Exynos by choosing type of data
which shell be counter in the PPMU registers.
It is possible to count e.g. read or write requests, read or write data.
A new field has been added in the DT 'event' node called 'event-data-type'.
It is them used during the setup of the counter. In the prevoius
implementation there was always one option used: count read+write data.
Sometimes we need more precised information and this patch set tries to
address it.
Regards,
Lukasz Luba
Lukasz Luba (3):
include: dt-bindings: add Performance Monitoring Unit for Exynos
drivers: devfreq: events: extend events by type of counted data
Documentation: devicetree: add PPMU events description
.../bindings/devfreq/event/exynos-ppmu.txt | 18 ++++++++++
MAINTAINERS | 5 +++
drivers/devfreq/event/exynos-ppmu.c | 38 +++++++++++++++-------
include/dt-bindings/pmu/exynos_ppmu.h | 24 ++++++++++++++
include/linux/devfreq-event.h | 6 ++++
5 files changed, 79 insertions(+), 12 deletions(-)
create mode 100644 include/dt-bindings/pmu/exynos_ppmu.h
--
2.7.4
next parent reply other threads:[~2019-04-17 7:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20190417074829eucas1p234e664f9bf295eca8d2fad6ba953f37c@eucas1p2.samsung.com>
2019-04-17 7:48 ` Lukasz Luba [this message]
[not found] ` <CGME20190417074832eucas1p26eca3ed8bf754787b4860206ba542e1c@eucas1p2.samsung.com>
2019-04-17 7:48 ` [PATCH 1/3] include: dt-bindings: add Performance Monitoring Unit for Exynos Lukasz Luba
2019-04-17 8:10 ` Chanwoo Choi
2019-04-17 10:50 ` Lukasz Luba
[not found] ` <CGME20190417074834eucas1p1faa327cb6394d899a8e107ba61f28fda@eucas1p1.samsung.com>
2019-04-17 7:48 ` [PATCH 2/3] drivers: devfreq: events: extend events by type of counted data Lukasz Luba
2019-04-17 8:22 ` Chanwoo Choi
2019-04-17 11:00 ` Lukasz Luba
[not found] ` <CGME20190417074835eucas1p19319bedd176d55e10b272881b7c68919@eucas1p1.samsung.com>
2019-04-17 7:48 ` [PATCH 3/3] Documentation: devicetree: add PPMU events description Lukasz Luba
2019-04-17 8:26 ` Chanwoo Choi
2019-04-18 9:50 ` Lukasz Luba
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=1555487288-4777-1-git-send-email-l.luba@partner.samsung.com \
--to=l.luba@partner.samsung.com \
--cc=b.zolnierkie@samsung.com \
--cc=cw00.choi@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=kgene@kernel.org \
--cc=krzk@kernel.org \
--cc=kyungmin.park@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=mark.rutland@arm.com \
--cc=myungjoo.ham@samsung.com \
--cc=robh+dt@kernel.org \
--cc=s.nawrocki@samsung.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®