From: ezequiel.garcia@free-electrons.com (Ezequiel Garcia)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/4] clocksource: armada-370-xp: Fix clock input in devicetree binding
Date: Mon, 19 Aug 2013 19:47:18 -0300 [thread overview]
Message-ID: <20130819224717.GA2388@localhost> (raw)
In-Reply-To: <5212935E.7030703@wwwdotorg.org>
On Mon, Aug 19, 2013 at 03:51:26PM -0600, Stephen Warren wrote:
> On 08/19/2013 10:28 AM, Ezequiel Garcia wrote:
> > This commit specifies the clock inputs available for the Armada XP
> > timer: namely the 'nbclk' (L2/coherency fabric) and the 'refclk'
> > (25 MHz fixed-clock).
>
> > diff --git a/Documentation/devicetree/bindings/timer/marvell,armada-370-xp-timer.txt b/Documentation/devicetree/bindings/timer/marvell,armada-370-xp-timer.txt
>
> > -- clocks: clock driving the timer hardware, only required for
> > - "marvell,armada-370-timer";
> > +- clocks: clock driving the timer hardware.
>
> The valid (and required?) entries for clock-names need to be documented
> here in the list of properties, not just show up in the example below.
>
Argh, of course... I'll send a new version.
> Didn't I see some other conflicting patch for this file just the other
> day which was doing exactly that? Maybe I'm getting different patches
> confused...
Mmm.. probably the previous patchset (on which this one is based)?
http://comments.gmane.org/gmane.linux.ports.arm.kernel/260179
--
Ezequiel Garc?a, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com
prev parent reply other threads:[~2013-08-19 22:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-19 16:28 [PATCH 4/4] clocksource: armada-370-xp: Fix clock input in devicetree binding Ezequiel Garcia
2013-08-19 21:51 ` Stephen Warren
2013-08-19 22:47 ` Ezequiel Garcia [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=20130819224717.GA2388@localhost \
--to=ezequiel.garcia@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).