From: geert@linux-m68k.org (Geert Uytterhoeven)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/4] arm64: dts: r8a7795: Link ARM GIC to clock and clock domain
Date: Tue, 17 Jan 2017 15:08:21 +0100 [thread overview]
Message-ID: <CAMuHMdUjtwv=iVcfNsA4uB_OdUZQgp8XyonWVgbqsPjqwAtwtQ@mail.gmail.com> (raw)
In-Reply-To: <HK2PR06MB05451777E7151CA9C7EF8990C37C0@HK2PR06MB0545.apcprd06.prod.outlook.com>
Hi Ramesh,
On Tue, Jan 17, 2017 at 3:00 PM, Ramesh Shanmugasundaram
<ramesh.shanmugasundaram@bp.renesas.com> wrote:
>> --- a/arch/arm64/boot/dts/renesas/r8a7795.dtsi
>> +++ b/arch/arm64/boot/dts/renesas/r8a7795.dtsi
>> @@ -166,6 +166,9 @@
>> <0x0 0xf1060000 0 0x20000>;
>> interrupts = <GIC_PPI 9
>> (GIC_CPU_MASK_SIMPLE(4) |
>> IRQ_TYPE_LEVEL_HIGH)>;
>> + clocks = <&cpg CPG_MOD 408>;
>> + clock-names = "clk";
>
> Should the module clock be named "fck"?
Not according to
Documentation/devicetree/bindings/interrupt-controller/arm,gic.txt.
P.S. If you use "git blame", you may think I'm cheating, but naming was
ased on the actual Technical Reference Manuals ;-)
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert at linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2017-01-17 14:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-17 12:49 [PATCH 0/4] ARM/arm64: dts: renesas: Link ARM GIC to clock and clock domain Geert Uytterhoeven
2017-01-17 12:49 ` [PATCH 1/4] ARM: dts: r8a7743: " Geert Uytterhoeven
2017-01-17 12:49 ` [PATCH 2/4] ARM: dts: r8a7745: " Geert Uytterhoeven
2017-01-17 12:49 ` [PATCH 3/4] arm64: dts: r8a7795: " Geert Uytterhoeven
2017-01-17 14:00 ` Ramesh Shanmugasundaram
2017-01-17 14:08 ` Geert Uytterhoeven [this message]
2017-01-17 12:49 ` [PATCH 4/4] arm64: dts: r8a7796: " Geert Uytterhoeven
2017-01-23 9:23 ` [PATCH 0/4] ARM/arm64: dts: renesas: " Simon Horman
2017-01-23 9:26 ` Geert Uytterhoeven
2017-01-23 9:42 ` Simon Horman
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='CAMuHMdUjtwv=iVcfNsA4uB_OdUZQgp8XyonWVgbqsPjqwAtwtQ@mail.gmail.com' \
--to=geert@linux-m68k.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 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).