[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BC1ADE3F-F31F-4E1E-A6EE-3BD83C5F2634@fb.com>
Date: Mon, 5 Nov 2018 18:43:43 +0000
From: Tao Ren <taoren@...com>
To: Daniel Lezcano <daniel.lezcano@...aro.org>,
Thomas Gleixner <tglx@...utronix.de>
CC: Joel Stanley <joel@....id.au>, Andrew Jeffery <andrew@...id.au>,
Yu Lei <mine260309@...il.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-aspeed@...ts.ozlabs.org" <linux-aspeed@...ts.ozlabs.org>,
OpenBMC Maillist <openbmc@...ts.ozlabs.org>,
Linus Walleij <linus.walleij@...aro.org>
Subject: Re: [PATCH v2] clocksource/drivers/fttmr010: fix invalid interrupt
register access
On 10/7/18, 2:03 PM, "Linus Walleij" <linus.walleij@...aro.org> wrote:
>
> On Wed, Oct 3, 2018 at 11:54 PM Tao Ren <taoren@...com> wrote:
>
>> TIMER_INTR_MASK register (Base Address of Timer + 0x38) is not designed
>> for masking interrupts on ast2500 chips, and it's not even listed in
>> ast2400 datasheet, so it's not safe to access TIMER_INTR_MASK on aspeed
>> chips.
>>
>> Similarly, TIMER_INTR_STATE register (Base Address of Timer + 0x34) is
>> not interrupt status register on ast2400 and ast2500 chips. Although
>> there is no side effect to reset the register in fttmr010_common_init(),
>> it's just misleading to do so.
>>
>> Besides, "count_down" is renamed to "is_aspeed" in "fttmr010" structure,
>> and more comments are added so the code is more readble.
>>
>> Signed-off-by: Tao Ren <taoren@...com>
>> ---
>> Changes in v2:
>> - "count_down" is renamed to "is_aspeed" in "fttmr010" structure.
>> - more comments are added to make the code more readable.
>
> Reviewed-by: Linus Walleij <linus.walleij@...aro.org>
Hi Daniel / Thomas,
Any further comments on the patch? Or is there anything needed from my side?
Thanks,
Tao Ren
Powered by blists - more mailing lists