[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAL_JsqJ6HWRiU2iQtJapRLwuWdUM6KCgYfseJzMtie-xG_UKxw@mail.gmail.com>
Date: Fri, 7 Apr 2017 17:01:53 -0500
From: Rob Herring <robh+dt@...nel.org>
To: Linus Walleij <linus.walleij@...aro.org>
Cc: Daniel Lezcano <daniel.lezcano@...aro.org>,
Thomas Gleixner <tglx@...utronix.de>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/3 RESEND] clocksource: Augment bindings for Faraday timer
On Fri, Apr 7, 2017 at 4:55 PM, Linus Walleij <linus.walleij@...aro.org> wrote:
> It turns out that the Cortina Gemini timer block is just a
> standard IP block from Faraday Technology named FTTMR010.
>
> In order to make things clear and understandable, we rename the
> bindings with a Faraday compatible as primary and the Cortina
> gemini as a more specific case.
>
> For the plain Faraday timer we require two clock references,
> while the Gemini can keep it's syscon lookup pattern.
>
> Cc: devicetree@...r.kernel.org
> Signed-off-by: Linus Walleij <linus.walleij@...aro.org>
> ---
> .../bindings/timer/cortina,gemini-timer.txt | 22 ---------------
> .../devicetree/bindings/timer/faraday,fttmr010.txt | 33 ++++++++++++++++++++++
> 2 files changed, 33 insertions(+), 22 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/timer/cortina,gemini-timer.txt
> create mode 100644 Documentation/devicetree/bindings/timer/faraday,fttmr010.txt
Does the -M option not work here?
In any case,
Acked-by: Rob Herring <robh@...nel.org>
Powered by blists - more mailing lists