[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdb9fRTOBwb62=fzcww7HaQZPrfj3SkEockEGU6qw+_0Hg@mail.gmail.com>
Date: Sun, 28 May 2017 16:00:36 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Daniel Lezcano <daniel.lezcano@...aro.org>
Cc: Andrew Jeffery <andrew@...id.au>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Thomas Gleixner <tglx@...utronix.de>,
Joel Stanley <joel@....id.au>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
Ryan Chen <ryan_chen@...eedtech.com>
Subject: Re: [PATCH] clocksource: moxart: Add AST2500 compatible string
On Thu, May 25, 2017 at 10:28 PM, Daniel Lezcano
<daniel.lezcano@...aro.org> wrote:
> Shouldn't the compatible string be:
>
> "aspeed,ast2400-timer", "faraday,fttmr010"
> "aspeed,ast2500-timer", "faraday,fttmr010"
Actually not this time. The Gemini and Moxart timers are compatible with
the pure Faraday fttmr010 IP-block but Aspeed has played around with the
silicon IP so it is not compatible anymore.
Yours,
Linus Walleij
Powered by blists - more mailing lists