From: Tomeu Vizoso <tomeu.vizoso-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org>
To: linux-pm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: Javier Martinez Canillas
<javier.martinez-ZGY8ohtN/8pPYcu2f3hruQ@public.gmane.org>,
Tomeu Vizoso
<tomeu.vizoso-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org>,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PATCH v2 0/3] Add support for Tegra Activity Monitor
Date: Mon, 24 Nov 2014 13:28:15 +0100 [thread overview]
Message-ID: <1416832111-367-1-git-send-email-tomeu.vizoso@collabora.com> (raw)
Hello,
in this v2 I have made the driver use devfreq. It works just as fine as the
previous revision, but it's almost 200 lines more of code for not that much
gain.
Though I don't see much point in using devfreq, I think it's probably better
than an ad-hoc driver because in the future I hope that devfreq will gain
functionality that will be of use (PM_QOS_MEMORY_BANDWIDTH support, for
example).
These patches implement support for setting the rate of the EMC clock based on
stats collected from the ACTMON, a piece of hw in the Tegra124 that counts
memory accesses (among others).
It depends on the following in-flight patches:
* EMC driver: http://thread.gmane.org/gmane.linux.drivers.devicetree/99304
* CPUFreq driver: http://thread.gmane.org/gmane.linux.kernel/1812962
I have pushed a branch here for testing:
http://cgit.collabora.com/git/user/tomeu/linux.git/log/?h=actmon-v2
Regards,
Tomeu
Tomeu Vizoso (3):
of: Add binding for NVIDIA Tegra ACTMON node
PM / devfreq: tegra: add devfreq driver for Tegra Activity Monitor
ARM: tegra: Add Tegra124 ACTMON support
.../devicetree/bindings/arm/tegra/actmon.txt | 38 ++
arch/arm/boot/dts/tegra124.dtsi | 23 +
drivers/devfreq/Kconfig | 10 +
drivers/devfreq/Makefile | 1 +
drivers/devfreq/tegra-devfreq.c | 718 +++++++++++++++++++++
5 files changed, 790 insertions(+)
create mode 100644 Documentation/devicetree/bindings/arm/tegra/actmon.txt
create mode 100644 drivers/devfreq/tegra-devfreq.c
--
1.9.3
next reply other threads:[~2014-11-24 12:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-24 12:28 Tomeu Vizoso [this message]
[not found] ` <1416832111-367-1-git-send-email-tomeu.vizoso-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org>
2014-11-24 12:28 ` [PATCH v2 1/3] of: Add binding for NVIDIA Tegra ACTMON node Tomeu Vizoso
2014-11-24 12:28 ` [PATCH v2 2/3] PM / devfreq: tegra: add devfreq driver for Tegra Activity Monitor Tomeu Vizoso
2014-11-26 10:02 ` Alexandre Courbot
2014-12-02 14:49 ` Tomeu Vizoso
2014-12-02 11:15 ` Thierry Reding
2014-12-03 15:09 ` Tomeu Vizoso
2014-11-24 12:28 ` [PATCH v2 3/3] ARM: tegra: Add Tegra124 ACTMON support Tomeu Vizoso
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=1416832111-367-1-git-send-email-tomeu.vizoso@collabora.com \
--to=tomeu.vizoso-zgy8ohtn/8qb+jhodadfcq@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=javier.martinez-ZGY8ohtN/8pPYcu2f3hruQ@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-pm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/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).