From: Linus Walleij <linus.walleij@linaro.org>
To: Rob Herring <robh@kernel.org>
Cc: Daniel Lezcano <daniel.lezcano@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/3] clocksource: Augment bindings for Faraday timer
Date: Fri, 7 Apr 2017 23:52:08 +0200 [thread overview]
Message-ID: <CACRpkda+r7f73r1Jfe51Ur5a9ZS0CEEx5HStkpdej+5gBLiX-A@mail.gmail.com> (raw)
In-Reply-To: <CAL_JsqK17_p1YKzSN2soobrKuCr-1gWUjgF6xRiHDWzyao=L6A@mail.gmail.com>
On Fri, Apr 7, 2017 at 4:27 PM, Rob Herring <robh@kernel.org> wrote:
> On Fri, Apr 7, 2017 at 8:41 AM, Daniel Lezcano
> <daniel.lezcano@linaro.org> wrote:
>> On Fri, Mar 24, 2017 at 10:32:33PM +0100, Linus Walleij 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.
>>>
>>> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
>>> ---
>>
>> Rob ? Is this change ok for you?
>
> Send to the DT list please. And use the -M option.
Sorry missed it :(
Resending this patch.
Yours,
Linus Walleij
prev parent reply other threads:[~2017-04-07 21:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-24 21:32 [PATCH 1/3] clocksource: Augment bindings for Faraday timer Linus Walleij
2017-03-24 21:32 ` [PATCH 2/3] clocksource: rename Gemini timer to Faraday Linus Walleij
2017-03-24 21:32 ` [PATCH 3/3] clocksource: fttmr010: refactor to handle clock Linus Walleij
2017-04-07 13:41 ` [PATCH 1/3] clocksource: Augment bindings for Faraday timer Daniel Lezcano
2017-04-07 14:27 ` Rob Herring
2017-04-07 21:52 ` Linus Walleij [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CACRpkda+r7f73r1Jfe51Ur5a9ZS0CEEx5HStkpdej+5gBLiX-A@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).