From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 5/5] clocksource: armada-370-xp: Add detailed clock requirements in devicetree binding
Date: Tue, 20 Aug 2013 14:32:10 -0600 [thread overview]
Message-ID: <5213D24A.50908@wwwdotorg.org> (raw)
In-Reply-To: <1377013554-23389-6-git-send-email-ezequiel.garcia@free-electrons.com>
On 08/20/2013 09:45 AM, Ezequiel Garcia wrote:
> Specifies the required clock inputs for each supported compatible.
> Armada 370 requires a single clock phandle, and Armada XP requires
> two clock phandles with clock-names "nbclk" and "fixed".
This patch,
Acked-by: Stephen Warren <swarren@nvidia.com>
(although the requirement for Armada XP to have entries in
clocks/clock-names isn't backwards-compatible...)
next prev parent reply other threads:[~2013-08-20 20:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-20 15:45 [PATCH v3 0/5] Armada XP clocks for timer Ezequiel Garcia
2013-08-20 15:45 ` [PATCH v3 1/5] ARM: mvebu: Add the reference 25 MHz fixed-clock to Armada XP Ezequiel Garcia
2013-08-20 19:25 ` Mike Turquette
2013-08-20 15:45 ` [PATCH v3 2/5] ARM: mvebu: Add clock properties to Armada XP timer node Ezequiel Garcia
2013-08-20 19:26 ` Mike Turquette
2013-08-20 15:45 ` [PATCH v3 3/5] clocksource: armada-370-xp: Replace WARN_ON with BUG_ON Ezequiel Garcia
2013-08-20 15:45 ` [PATCH v3 4/5] clocksource: armada-370-xp: Get reference fixed-clock by name Ezequiel Garcia
2013-08-20 15:45 ` [PATCH v3 5/5] clocksource: armada-370-xp: Add detailed clock requirements in devicetree binding Ezequiel Garcia
2013-08-20 20:32 ` Stephen Warren [this message]
2013-08-20 20:50 ` Ezequiel Garcia
2013-08-22 8:07 ` [PATCH v3 0/5] Armada XP clocks for timer Gregory CLEMENT
2013-08-27 8:52 ` Ezequiel Garcia
2013-08-27 14:49 ` Jason Cooper
2013-09-02 14:26 ` Ezequiel Garcia
2013-09-03 12:46 ` Jason Cooper
2013-09-03 12:51 ` Ezequiel Garcia
2013-09-03 19:26 ` Jason Cooper
2013-09-04 8:21 ` Daniel Lezcano
2013-09-11 18:00 ` Ezequiel Garcia
2013-08-27 14:53 ` Jason Cooper
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=5213D24A.50908@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.