[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACPK8XfCR37FuwZ8yp8z+aWaN=6B36tkXHEEKWorkE66TSXXJQ@mail.gmail.com>
Date: Tue, 30 May 2017 14:05:07 +0930
From: Joel Stanley <joel@....id.au>
To: Daniel Lezcano <daniel.lezcano@...aro.org>
Cc: Andrew Jeffery <andrew@...id.au>,
Ryan Chen <ryan_chen@...eedtech.com>,
Mark Rutland <mark.rutland@....com>,
Linus Walleij <linus.walleij@...aro.org>,
Jonas Jensen <jonas.jensen@...il.com>,
Thomas Gleixner <tglx@...utronix.de>,
"open list:CLOCKSOURCE, CLOCKEVENT DRIVERS"
<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] clocksource/drivers/fttmr010: Fix aspeed-2500 initialization
On Mon, May 29, 2017 at 5:15 PM, Daniel Lezcano
<daniel.lezcano@...aro.org> wrote:
> On 29/05/2017 08:05, Andrew Jeffery wrote:
>> On Fri, 2017-05-26 at 10:48 +0200, Daniel Lezcano wrote:
>>> The recent changes made the fttmr010 to be more generic and support different
>>> timers with a very few differences like moxart or aspeed.
>>>
>>> The aspeed timer uses a countdown and there is a test against the aspeed2400
>>> compatible string to set a flag.
>>>
>>> With the previous patch, we added the aspeed2500 compatible string but without
>>> taking care of setting the countdown flag.
>>>
>>> Fix this by specifiying a init function and pass the aspeed flag to a common
>>> init function.
>>>
>>> Signed-off-by: Daniel Lezcano <daniel.lezcano@...aro.org>
>>
>> Tested-by: Andrew Jeffery <andrew@...id.au>
>> Reviewed-by: Andrew Jeffery <andrew@...id.au>
Thanks everyone.
Acked-by: Joel Stanley <joel@....id.au>
Andrew, I think you had to fix up the clock device tree entries in the
Aspeed device tree. Can you please send me a patch for that?
Cheers,
Joel
>>
>
> Thanks for testing.
>
> -- Daniel
>
>
> --
> <http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
>
> Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
> <http://twitter.com/#!/linaroorg> Twitter |
> <http://www.linaro.org/linaro-blog/> Blog
>
Powered by blists - more mailing lists