From: Geert Uytterhoeven <geert@linux-m68k.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH v8 04/07] arm64: renesas: r8a7795 dtsi: Add all SCIF nodes
Date: Thu, 03 Sep 2015 08:23:22 +0000 [thread overview]
Message-ID: <CAMuHMdXy-7NtDFn7vZ5NvcVPxi48FXhQk3aefRKj2d-oh0RC2A@mail.gmail.com> (raw)
In-Reply-To: <20150831062952.24004.17072.sendpatchset@little-apple>
Hi Magnus,
On Thu, Sep 3, 2015 at 10:06 AM, Magnus Damm <magnus.damm@gmail.com> wrote:
>> Practically, I need a simple way to identify the clock used by the GIC.
>> Using the "intc-sys"/"intc-ap" name looked like a good idea.
>> While it's always MSTP408, MSTP408 is used for other purposes on some SoCs.
>>
>> Let's give DT scanning a try...
>
> Uhm, sounds a bit overly complicated to me. This has probably been
> discussed wildly before, but please remind me:
>
> What is wrong again with being standard and adding "clocks" and
> "clock-names" to the GIC node?
That needs to be done anyway (still have to dive into GIC architecture
and come up with bindings the ARM people like).
But it's not sufficient as:
- The GIC driver is not PM Runtime aware. It doesn't even use a platform
device,
- The GIC is instantiated from IRQCHIP_DECLARE(), which is way before
clocks are ready.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@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:[~2015-09-03 8:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-31 6:29 [PATCH v8 04/07] arm64: renesas: r8a7795 dtsi: Add all SCIF nodes Magnus Damm
2015-08-31 10:40 ` Laurent Pinchart
2015-08-31 12:47 ` Geert Uytterhoeven
2015-08-31 12:59 ` Magnus Damm
2015-08-31 13:08 ` Geert Uytterhoeven
2015-09-03 7:41 ` Magnus Damm
2015-09-03 7:54 ` Geert Uytterhoeven
2015-09-03 8:06 ` Magnus Damm
2015-09-03 8:23 ` Geert Uytterhoeven [this message]
2015-09-03 8:28 ` Magnus Damm
2015-09-03 11:48 ` Laurent Pinchart
2015-09-03 19:03 ` Geert Uytterhoeven
2015-09-07 19:43 ` Laurent Pinchart
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=CAMuHMdXy-7NtDFn7vZ5NvcVPxi48FXhQk3aefRKj2d-oh0RC2A@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=linux-sh@vger.kernel.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.