[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdZXum+bQg1FO+EHhKWpxtPYXfeRhoAKkFXeMQh1Jng3Ww@mail.gmail.com>
Date: Wed, 3 Oct 2018 08:56:53 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: taoren@...com
Cc: Daniel Lezcano <daniel.lezcano@...aro.org>,
Thomas Gleixner <tglx@...utronix.de>,
Joel Stanley <joel@....id.au>,
Andrew Jeffery <andrew@...id.au>,
Yu Lei <mine260309@...il.com>,
OpenBMC Maillist <openbmc@...ts.ozlabs.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
linux-aspeed@...ts.ozlabs.org
Subject: Re: [PATCH] clocksource/drivers/fttmr010: fix invalid interrupt
register access
On Wed, Oct 3, 2018 at 12:08 AM Tao Ren <taoren@...com> wrote:
> 1) adding "is_aspeed" flag. "count_down" is kept because potentially faraday-fttmr could also be configured as count_down timer (although I don't see any reason to do so).
> 2) renaming "count_down" to "is_aspeed". By doing this, we set restriction that faraday-fttmr will always be upward.
> What's your thought? Do you want me to include all the changes in this diff?
My thought is go for (2) and do all changes in one patch :)
Yours,
Linus Walleij
Powered by blists - more mailing lists