From: Arnd Bergmann <arnd@arndb.de>
To: Krzysztof Kozlowski <k.kozlowski@samsung.com>
Cc: Olof Johansson <olof@lixom.net>,
Kevin Hilman <khilman@kernel.org>,
arm@kernel.org, Kukjin Kim <kgene@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
myungjoo.ham@samsung.com, cw00.choi@samsung.com,
linux-pm@vger.kernel.org, rjw@rjwysocki.net
Subject: Re: [GIT PULL] ARM: dts: exynos: Devfreq for v4.7
Date: Tue, 10 May 2016 16:18:20 +0200 [thread overview]
Message-ID: <4199175.Sym2be3WAj@wuerfel> (raw)
In-Reply-To: <1462367136-28627-1-git-send-email-k.kozlowski@samsung.com>
On Wednesday 04 May 2016 15:05:36 Krzysztof Kozlowski wrote:
> Topic branch for Device Tree changes adding new generic devfreq driver, for
> v4.7:
> 1. Add bus nodes for Exynos3250, Exynos4x12, Exynos4210 and Exynos542x.
> 2. Split out common PPMU (Performance Monitoring Unit) nodes into separate
> DTSI. The PPMU provides performance data for devfreq.
> 3. Add NoCP (Network on Chip Probe) node for Exynos542x. On this SoC, like PPMU
> on older designs, provides performance data for devfreq.
> 4. Enable DFVS (Dynamic Voltage and Frequency Scaling) on boards:
> - Exynos3250 Rinato,
> - Exynos4412 Odroid-X/X2/U3 and Trats2,
> - Exynos5422 Odroid XU3/XU3-Lite/XU4.
>
>
Merged into next/late now, so we can track the clk dependency more easily.
Thanks,
Arnd
prev parent reply other threads:[~2016-05-10 14:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-04 13:05 [GIT PULL] ARM: dts: exynos: Devfreq for v4.7 Krzysztof Kozlowski
2016-05-10 14:18 ` Arnd Bergmann [this message]
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=4199175.Sym2be3WAj@wuerfel \
--to=arnd@arndb.de \
--cc=arm@kernel.org \
--cc=b.zolnierkie@samsung.com \
--cc=cw00.choi@samsung.com \
--cc=k.kozlowski@samsung.com \
--cc=kgene@kernel.org \
--cc=khilman@kernel.org \
--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=myungjoo.ham@samsung.com \
--cc=olof@lixom.net \
--cc=rjw@rjwysocki.net \
/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).