From: Arnd Bergmann <arnd@arndb.de>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Olof Johansson <olof@lixom.net>,
Kevin Hilman <khilman@kernel.org>,
arm@kernel.org, Krzysztof Kozlowski <k.kozlowski@samsung.com>,
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>,
Javier Martinez Canillas <javier@osg.samsung.com>,
Daniel Lezcano <daniel.lezcano@linaro.org>
Subject: Re: [GIT PULL 1/3] ARM: soc: exynos: Drivers for v4.9
Date: Mon, 19 Sep 2016 17:02:40 +0200 [thread overview]
Message-ID: <2663426.T8oUku18qe@wuerfel> (raw)
In-Reply-To: <1474216788-17282-2-git-send-email-krzk@kernel.org>
On Sunday, September 18, 2016 6:39:46 PM CEST Krzysztof Kozlowski wrote:
> Samsung drivers/soc update for v4.9:
> 1. Allow compile testing of exynos-mct clocksource driver on ARM64.
> 2. Document Exynos5433 PMU compatible (already used by clkout driver and more
> will be coming soon).
Pulled into next/drivers, thanks
Just for my understanding: why do we need the exynos-mct driver on ARM64
but not the delay-timer portion of it?
Is there an advantage in using MCT over the architected timer on these
chips? If so, should we also have a way to use it as the delay timer?
Arnd
next prev parent reply other threads:[~2016-09-19 15:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-18 16:39 [GIT PULL 0/3] ARM: exynos: Second round of stuff for v4.9 Krzysztof Kozlowski
2016-09-18 16:39 ` [GIT PULL 1/3] ARM: soc: exynos: Drivers " Krzysztof Kozlowski
2016-09-19 15:02 ` Arnd Bergmann [this message]
2016-09-19 15:53 ` Krzysztof Kozlowski
2016-10-03 0:25 ` Olof Johansson
2016-10-03 7:48 ` Krzysztof Kozlowski
2016-10-03 12:19 ` Kukjin Kim
2016-10-11 0:46 ` Kukjin Kim
2016-10-11 0:58 ` Kukjin Kim
2016-09-18 16:39 ` [GIT PULL 2/3] ARM: dts: exynos: DT for v4.9, second round Krzysztof Kozlowski
2016-09-19 15:46 ` Arnd Bergmann
2016-09-18 16:39 ` [GIT PULL 3/3] ARM: dts: exynos: pinctrl cleanup for v4.9 Krzysztof Kozlowski
2016-09-19 15:48 ` Arnd Bergmann
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=2663426.T8oUku18qe@wuerfel \
--to=arnd@arndb.de \
--cc=arm@kernel.org \
--cc=b.zolnierkie@samsung.com \
--cc=daniel.lezcano@linaro.org \
--cc=javier@osg.samsung.com \
--cc=k.kozlowski@samsung.com \
--cc=kgene@kernel.org \
--cc=khilman@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=olof@lixom.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).