[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.02.1402041715220.24986@ionos.tec.linutronix.de>
Date: Tue, 4 Feb 2014 17:24:37 +0100 (CET)
From: Thomas Gleixner <tglx@...utronix.de>
To: Ivan Khoronzhuk <ivan.khoronzhuk@...com>
cc: santosh.shilimkar@...com, rob@...dley.net, linux@....linux.org.uk,
galak@...eaurora.org, robh+dt@...nel.org, pawel.moll@....com,
mark.rutland@....com, ijc+devicetree@...lion.org.uk,
daniel.lezcano@...aro.org, devicetree@...r.kernel.org,
linux-doc@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org, grygorii.strashko@...com
Subject: Re: [PATCH v4 1/3] clocksource: timer-keystone: introduce clocksource
driver for Keystone
On Tue, 4 Feb 2014, Ivan Khoronzhuk wrote:
> + keystone_timer_writel(off, TCR);
> + /* here we have to be sure the timer has been disabled */
> + wmb();
We have explicit writew_relaxed and writew. Why open coding the
barriers?
Thanks,
tglx
--
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