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,
robh+dt@kernel.org, b.zolnierkie@samsung.com, krzk@kernel.org,
Lukasz Luba <l.luba@partner.samsung.com>,
cw00.choi@samsung.com, kyungmin.park@samsung.com,
kgene@kernel.org, myungjoo.ham@samsung.com,
s.nawrocki@samsung.com, m.szyprowski@samsung.com
Subject: [PATCH v3 0/4] Exynos5 DMC interrupt mode
Date: Wed, 2 Oct 2019 08:04:51 +0200 [thread overview]
Message-ID: <20191002060455.3834-1-l.luba@partner.samsung.com> (raw)
In-Reply-To: CGME20191002060503eucas1p25fb14ebbf05a5599f8faeacbd3a15887@eucas1p2.samsung.com
Hi all,
This is a v3 patch set for the Exynos5 Dynamic Memory Controller
driver which could be found in Krzysztof's for-next branch [1].
It adds interrupt mode which does not relay on devfreq polling.
Instead of checking the device state by the framework, driver uses local
performance event counters which could trigger interrupt when overflow.
Thanks to this approach the driver avoids issues present in devfreq framework,
when default polling check does not occur.
The algorithm calculates 'busy_time' and 'total_time' needed for devfreq
governors (simple_ondemand) based on requests transactions traffic.
Changes:
v3:
- added information in bindings about interrupt names, since the code is
sensitive for it as pointed out by Krzysztof
v2:
changes suggested by Krzysztof
- added interrupt line for the channel 1
- added description for bindings with interrupt lines
- fixed fallback path in probe function
- added comments, blank lines, removed unneeded dev_dbg() in irq handler
Regards,
Lukasz Luba
[1] https://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux.git/log/?h=for-next
Lukasz Luba (4):
dt-bindings: memory-controllers: Add Exynos5422 DMC interrupts
description
ARM: dts: exynos: Add interrupt to DMC controller in Exynos5422
ARM: dts: exynos: map 0x10000 SFR instead of 0x100 in DMC Exynos5422
memory: samsung: exynos5422-dmc: Add support for interrupt from
performance counters
.../memory-controllers/exynos5422-dmc.txt | 11 +
arch/arm/boot/dts/exynos5420.dtsi | 5 +-
drivers/memory/samsung/exynos5422-dmc.c | 345 ++++++++++++++++--
3 files changed, 335 insertions(+), 26 deletions(-)
--
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-10-02 6:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20191002060503eucas1p25fb14ebbf05a5599f8faeacbd3a15887@eucas1p2.samsung.com>
2019-10-02 6:04 ` Lukasz Luba [this message]
[not found] ` <CGME20191002060504eucas1p2f023677bb85a7f6a1efebf891e8d81df@eucas1p2.samsung.com>
2019-10-02 6:04 ` [PATCH v3 1/4] dt-bindings: memory-controllers: Add Exynos5422 DMC interrupts description Lukasz Luba
2019-10-02 17:23 ` Krzysztof Kozlowski
[not found] ` <CGME20191002060505eucas1p2efd80ccde8c728973df8d932580cd58b@eucas1p2.samsung.com>
2019-10-02 6:04 ` [PATCH v3 2/4] ARM: dts: exynos: Add interrupt to DMC controller in Exynos5422 Lukasz Luba
2019-10-02 17:24 ` Krzysztof Kozlowski
[not found] ` <CGME20191002060506eucas1p28c9670128f5adfb628d7e84ce55c6e60@eucas1p2.samsung.com>
2019-10-02 6:04 ` [PATCH v3 3/4] ARM: dts: exynos: map 0x10000 SFR instead of 0x100 in DMC Exynos5422 Lukasz Luba
2019-10-02 17:29 ` Krzysztof Kozlowski
[not found] ` <CGME20191002060507eucas1p169394dec59f010e112eb38d83e3fb8ba@eucas1p1.samsung.com>
2019-10-02 6:04 ` [PATCH v3 4/4] memory: samsung: exynos5422-dmc: Add support for interrupt from performance counters Lukasz Luba
2019-10-02 17:38 ` Krzysztof Kozlowski
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=20191002060455.3834-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).