[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a3213abc-1f1b-003a-3a23-a9d78b5a71fd@linaro.org>
Date: Mon, 29 May 2017 09:45:16 +0200
From: Daniel Lezcano <daniel.lezcano@...aro.org>
To: Andrew Jeffery <andrew@...id.au>
Cc: joel@....id.au, ryan_chen@...eedtech.com, mark.rutland@....com,
linus.walleij@...aro.org, 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 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 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