[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160317180949.GE2831@piout.net>
Date: Thu, 17 Mar 2016 19:09:49 +0100
From: Alexandre Belloni <alexandre.belloni@...e-electrons.com>
To: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
Cc: Thomas Gleixner <tglx@...utronix.de>,
Boris Brezillon <boris.brezillon@...e-electrons.com>,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-rt-users@...r.kernel.org,
Nicolas Ferre <nicolas.ferre@...el.com>
Subject: Re: arm: at91: do not disable/enable clocks in a row
On 09/03/2016 at 10:58:24 +0100, Sebastian Andrzej Siewior wrote :
> * Alexandre Belloni | 2016-03-08 19:39:10 [+0100]:
>
> >Hi,
> Hi,
>
> >Both are things to work on. In the mean time, I'm using the following
> >patch:
> >https://github.com/alexandrebelloni/linux/commit/3a2eae463fce18ae815b887a5c9ca1a657b180ac
> >
> >I understood from
> >http://lkml.iu.edu/hypermail/linux/kernel/1601.2/00941.html that this
> >was not your preferred course of action.
>
> That was one thing. What about this:
>
> ---
>
> Currently the driver will disable the clock and enable it one line later
> if it is switching from periodic mode into one shot.
> This can be avoided and causes a needless warning on -RT.
>
> Signed-off-by: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
I'm fine with that if you don't want to rely on the clock event state
machine.
Can you submit it to the mainline with:
Tested-by: Alexandre Belloni <alexandre.belloni@...e-electrons.com>
Acked-by: Alexandre Belloni <alexandre.belloni@...e-electrons.com>
--
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
Powered by blists - more mailing lists