From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCHv3 2/6] arm: Add device trees for TI-Nspire
Date: Wed, 15 May 2013 16:10:22 +0200 [thread overview]
Message-ID: <201305151610.23145.arnd@arndb.de> (raw)
In-Reply-To: <1368332581-94691-3-git-send-email-dt.tangr@gmail.com>
On Sunday 12 May 2013, Daniel Tang wrote:
> +
> + timer0: timer at 900C0000 {
> + reg = <0x900C0000 0x1000>;
> +
> + clocks = <&timer_clk>;
> + clock-names = "timer_clk";
> + };
> +
> + timer1: timer at 900D0000 {
> + reg = <0x900D0000 0x1000>;
> + interrupts = <19>;
> +
> + clocks = <&timer_clk>;
> + clock-names = "timer_clk";
> + };
> + clocks = <&apb_pclk>;
> + clock-names = "apb_pclk";
> + };
Why do you provide "clock-names" here? Do those devices have multiple
clock inputs? It's normally easier to just use the default clock
input.
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: Daniel Tang <dt.tangr@gmail.com>
Cc: linux-arm-kernel@lists.infradead.org, linux@arm.linux.org.uk,
Linus Walleij <linus.walleij@linaro.org>,
"fabian@ritter-vogt.de Vogt" <fabian@ritter-vogt.de>,
Lionel Debroux <lionel_debroux@yahoo.fr>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCHv3 2/6] arm: Add device trees for TI-Nspire
Date: Wed, 15 May 2013 16:10:22 +0200 [thread overview]
Message-ID: <201305151610.23145.arnd@arndb.de> (raw)
In-Reply-To: <1368332581-94691-3-git-send-email-dt.tangr@gmail.com>
On Sunday 12 May 2013, Daniel Tang wrote:
> +
> + timer0: timer@900C0000 {
> + reg = <0x900C0000 0x1000>;
> +
> + clocks = <&timer_clk>;
> + clock-names = "timer_clk";
> + };
> +
> + timer1: timer@900D0000 {
> + reg = <0x900D0000 0x1000>;
> + interrupts = <19>;
> +
> + clocks = <&timer_clk>;
> + clock-names = "timer_clk";
> + };
> + clocks = <&apb_pclk>;
> + clock-names = "apb_pclk";
> + };
Why do you provide "clock-names" here? Do those devices have multiple
clock inputs? It's normally easier to just use the default clock
input.
Arnd
next prev parent reply other threads:[~2013-05-15 14:10 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-12 4:22 [RFC PATCHv3 0/6] arm: Initial TI-Nspire support Daniel Tang
2013-05-12 4:22 ` Daniel Tang
2013-05-12 4:22 ` [RFC PATCHv3 1/6] " Daniel Tang
2013-05-12 4:22 ` Daniel Tang
2013-05-12 9:06 ` Russell King - ARM Linux
2013-05-12 9:06 ` Russell King - ARM Linux
2013-05-12 9:22 ` Daniel Tang
2013-05-12 9:22 ` Daniel Tang
2013-05-12 4:22 ` [RFC PATCHv3 2/6] arm: Add device trees for TI-Nspire Daniel Tang
2013-05-12 4:22 ` Daniel Tang
2013-05-15 14:10 ` Arnd Bergmann [this message]
2013-05-15 14:10 ` Arnd Bergmann
2013-05-12 4:22 ` [RFC PATCHv3 3/6] clk: Add TI-Nspire clock drivers Daniel Tang
2013-05-12 4:22 ` Daniel Tang
2013-05-15 14:07 ` Arnd Bergmann
2013-05-15 14:07 ` Arnd Bergmann
2013-05-16 8:31 ` Daniel Tang
2013-05-16 8:31 ` Daniel Tang
2013-05-16 12:17 ` Arnd Bergmann
2013-05-16 12:17 ` Arnd Bergmann
2013-05-19 11:09 ` Daniel Tang
2013-05-19 11:09 ` Daniel Tang
2013-05-19 19:48 ` Arnd Bergmann
2013-05-19 19:48 ` Arnd Bergmann
2013-05-20 11:19 ` Daniel Tang
2013-05-20 11:19 ` Daniel Tang
2013-05-20 12:26 ` Arnd Bergmann
2013-05-20 12:26 ` Arnd Bergmann
2013-05-12 4:22 ` [RFC PATCHv3 4/6] clocksource: Add TI-Nspire timer drivers Daniel Tang
2013-05-12 4:22 ` Daniel Tang
2013-05-14 8:03 ` Linus Walleij
2013-05-14 8:03 ` Linus Walleij
2013-05-14 11:51 ` Daniel Tang
2013-05-14 11:51 ` Daniel Tang
2013-05-17 13:17 ` Linus Walleij
2013-05-17 13:17 ` Linus Walleij
2013-05-18 6:40 ` Daniel Tang
2013-05-18 6:40 ` Daniel Tang
2013-05-20 12:49 ` Linus Walleij
2013-05-20 12:49 ` Linus Walleij
2013-05-12 4:23 ` [RFC PATCHv3 5/6] input: Add TI-Nspire keypad driver Daniel Tang
2013-05-12 4:23 ` Daniel Tang
2013-05-12 4:23 ` [RFC PATCHv3 6/6] irqchip: Add TI-Nspire irqchip Daniel Tang
2013-05-12 4:23 ` Daniel Tang
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=201305151610.23145.arnd@arndb.de \
--to=arnd@arndb.de \
--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.