From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 03/22] clocksource/drivers/rockchip: Make the driver more compatible
Date: Mon, 02 Nov 2015 16:33:27 +0100 [thread overview]
Message-ID: <5093304.EN6Bc2EjLr@wuerfel> (raw)
In-Reply-To: <1446469011-22710-3-git-send-email-daniel.lezcano@linaro.org>
On Monday 02 November 2015 13:56:31 Daniel Lezcano wrote:
> static inline void rk_timer_disable(struct clock_event_device *ce)
> {
> writel_relaxed(TIMER_DISABLE, rk_base(ce) + TIMER_CONTROL_REG);
> - dsb();
> + dsb(sy);
> }
>
> static inline void rk_timer_enable(struct clock_event_device *ce, u32 flags)
> {
> writel_relaxed(TIMER_ENABLE | TIMER_INT_UNMASK | flags,
> rk_base(ce) + TIMER_CONTROL_REG);
> - dsb();
> + dsb(sy);
> }
>
>
This will fail the compile test, because dsb() is not available on non-ARM
architectures. Would it be enough to just use the normal writel() accessor
here?
Arnd
next prev parent reply other threads:[~2015-11-02 15:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1446469011-22710-1-git-send-email-daniel.lezcano@linaro.org>
2015-11-02 12:56 ` [PATCH 02/22] clocksource/drivers/mediatek: Add the COMPILE_TEST option Daniel Lezcano
2015-11-02 12:56 ` [PATCH 03/22] clocksource/drivers/rockchip: Make the driver more compatible Daniel Lezcano
2015-11-02 15:33 ` Arnd Bergmann [this message]
2015-11-02 16:32 ` Daniel Lezcano
2015-11-02 21:44 ` Arnd Bergmann
2015-11-02 12:56 ` [PATCH 13/22] clocksource/drivers/vt8500: Remove unneeded header Daniel Lezcano
2015-11-02 12:56 ` [PATCH 19/22] clocksource/drivers/prcmu: Fix Kconfig and add COMPILE_TEST option Daniel Lezcano
2015-11-02 14:40 ` Linus Walleij
2015-11-02 14:57 ` Daniel Lezcano
2015-11-02 12:56 ` [PATCH 20/22] clocksource/drivers/exynos_mct: " Daniel Lezcano
2015-11-03 0:30 ` Krzysztof Kozlowski
2015-11-03 0:59 ` Krzysztof Kozlowski
2015-11-03 8:40 ` Daniel Lezcano
2015-11-03 10:02 ` Arnd Bergmann
2015-11-03 11:08 ` Daniel Lezcano
2015-11-03 12:01 ` Krzysztof Kozlowski
2015-11-03 12:04 ` Daniel Lezcano
2015-11-03 15:18 ` John Stultz
2015-11-03 0:54 ` Chanwoo Choi
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=5093304.EN6Bc2EjLr@wuerfel \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.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).