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: mark.rutland@arm.com, willy.mh.wolff.ml@gmail.com,
kgene@kernel.org, b.zolnierkie@samsung.com, krzk@kernel.org,
l.luba@partner.samsung.com, cw00.choi@samsung.com,
kyungmin.park@samsung.com, robh+dt@kernel.org,
myungjoo.ham@samsung.com, s.nawrocki@samsung.com,
m.szyprowski@samsung.com
Subject: [PATCH v4 0/5] Exynos Performance Monitoring Counters enhancements
Date: Wed, 5 Jun 2019 11:12:31 +0200 [thread overview]
Message-ID: <20190605091236.24263-1-l.luba@partner.samsung.com> (raw)
In-Reply-To: CGME20190605091301eucas1p278a554a15879a1b6fbc3d2bb5168f8cb@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
or latency.
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.
Changes:
v4:
- changed the way how 'ops' are matched according to Chanwoo's sugestions
in his example code (added his Signed-off-by to patch 2)
- changed documentation description accoriding to Chanwoo's sugestions
(added his Signed-off-by to patch 4)
- collected ACKs for patch 1 from Rob and from Chanwoo for patch 2 and
'Reviewed-by' for patch 1
- patch set is now based on v5.2-rc3 and tested on Odroid u3
v3 [1]:
- fixed wrong interpretation of ret value during DT parsing, which caused
alwasy taking default value.
v2 [2]:
- removed new entry in MAINTAINERS file as suggested by Bartek Zolnierkiewicz
and added new file to existing list for devfreq events
- added in the dt-bindings/pmu/exynos_ppmu.h 2 new entries for RO and WO for
counters in Exynos5433
- changed initialization with default values when data_type is not provided
in DT (as sugessted by Chanwoo)
- added 4th patch which adds 'event-data-type' to 'event' node for Exynos4412
PPMU events (asked by Chanwoo)
Regards,
Lukasz Luba
[1] https://lkml.org/lkml/2019/4/19/158
[2] https://lkml.org/lkml/2019/4/18/453
Lukasz Luba (5):
include: dt-bindings: add Performance Monitoring Unit for Exynos
drivers: devfreq: events: change matching code during probe
drivers: devfreq: events: extend events by type of counted data
Documentation: devicetree: add PPMU events description
DT: arm: exynos4412: add event data type which is monitored
.../bindings/devfreq/event/exynos-ppmu.txt | 26 ++++-
MAINTAINERS | 1 +
arch/arm/boot/dts/exynos4412-ppmu-common.dtsi | 10 ++
drivers/devfreq/event/exynos-ppmu.c | 98 +++++++++++++------
include/dt-bindings/pmu/exynos_ppmu.h | 25 +++++
include/linux/devfreq-event.h | 6 ++
6 files changed, 132 insertions(+), 34 deletions(-)
create mode 100644 include/dt-bindings/pmu/exynos_ppmu.h
--
2.17.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next parent reply other threads:[~2019-06-05 9:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20190605091301eucas1p278a554a15879a1b6fbc3d2bb5168f8cb@eucas1p2.samsung.com>
2019-06-05 9:12 ` Lukasz Luba [this message]
[not found] ` <CGME20190605091301eucas1p2f360a867c8df8ba542942d425289f355@eucas1p2.samsung.com>
2019-06-05 9:12 ` [PATCH v4 1/5] include: dt-bindings: add Performance Monitoring Unit for Exynos Lukasz Luba
[not found] ` <CGME20190605091302eucas1p2b2a959c0889666e95bd727381bceab24@eucas1p2.samsung.com>
2019-06-05 9:12 ` [PATCH v4 2/5] drivers: devfreq: events: change matching code during probe Lukasz Luba
[not found] ` <CGME20190605091303eucas1p27177d349e0f2bd37bf582dbd7266321a@eucas1p2.samsung.com>
2019-06-05 9:12 ` [PATCH v4 3/5] drivers: devfreq: events: extend events by type of counted data Lukasz Luba
2019-07-24 10:15 ` Lukasz Luba
2019-07-24 10:24 ` Chanwoo Choi
2019-07-25 16:23 ` Lukasz Luba
[not found] ` <CGME20190605091304eucas1p21e0717cafa17a14de569f1773cc7abe5@eucas1p2.samsung.com>
2019-06-05 9:12 ` [PATCH v4 4/5] Documentation: devicetree: add PPMU events description Lukasz Luba
[not found] ` <CAGTfZH2kTNWtx=Jp1UJaLN50Qxbq+Q9ThV4vhQ240QbOy1TRMQ@mail.gmail.com>
2019-06-26 13:58 ` Lukasz Luba
2019-06-26 14:03 ` Krzysztof Kozlowski
2019-06-26 14:17 ` Lukasz Luba
2019-06-27 1:11 ` Chanwoo Choi
2019-06-27 10:31 ` Lukasz Luba
[not found] ` <CGME20190605091305eucas1p136332cc3d1a299d90617bddcb365bee0@eucas1p1.samsung.com>
2019-06-05 9:12 ` [PATCH v4 5/5] DT: arm: exynos4412: add event data type which is monitored Lukasz Luba
2019-07-23 17:58 ` Krzysztof Kozlowski
2019-07-24 10:09 ` 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=20190605091236.24263-1-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 \
--cc=willy.mh.wolff.ml@gmail.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;
as well as URLs for NNTP newsgroup(s).