[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <70167479.zcs3JF0luJ@diego>
Date: Fri, 20 Jun 2014 12:43:31 +0200
From: Heiko Stübner <heiko@...ech.de>
To: Daniel Lezcano <daniel.lezcano@...aro.org>,
Thomas Gleixner <tglx@...utronix.de>,
Rob Herring <robh+dt@...nel.org>,
Pawel Moll <pawel.moll@....com>,
Mark Rutland <mark.rutland@....com>,
Ian Campbell <ijc+devicetree@...lion.org.uk>,
Kumar Gala <galak@...eaurora.org>
Cc: devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
Arnd Bergmann <arnd@...db.de>,
Matthias Brugger <matthias.bgg@...il.com>
Subject: [PATCH 0/2] clocksource: add rockchip rk3288 specific armv7-timer
The architected timer on Rockchip's RK3288 SoCs needs a bit of special handling
to start.
This seems to be similar to a recent discussion about the Exynos arch-timer
that also seems to need similar special handling (and mct timer running).
And, the arch-timer on recent Mediatek SoCs also uses this pattern of a
supplying timer below the arch-timer.
Therefore follow a suggestion from Arnd Bergmann and implement a separate
clocksource for it that does the setup and then initializes the arch-timer.
This series uses "of: Provide function to request and map memory" from
Matthias Brugger.
Heiko Stuebner (2):
clocksource: arm_arch_timer: remove static from arch_timer_init
clocksource: add rockchip-specific armv7-timer setup
.../bindings/arm/rockchip/armv7-timer.txt | 22 +++++++++
drivers/clocksource/Makefile | 1 +
drivers/clocksource/arm_arch_timer.c | 2 +-
drivers/clocksource/arm_arch_timer.h | 7 +++
drivers/clocksource/rockchip_timer.c | 57 ++++++++++++++++++++++
5 files changed, 88 insertions(+), 1 deletion(-)
create mode 100644 Documentation/devicetree/bindings/arm/rockchip/armv7-timer.txt
create mode 100644 drivers/clocksource/arm_arch_timer.h
create mode 100644 drivers/clocksource/rockchip_timer.c
--
1.9.0
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists