From: M P <buserror@gmail.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: michel.pollet@bp.renesas.com, linux-renesas-soc@vger.kernel.org,
Simon Horman <horms@verge.net.au>,
Phil Edworthy <phil.edworthy@renesas.com>,
buserror+upstream@gmail.com, Magnus Damm <magnus.damm@gmail.com>,
robh+dt@kernel.org, mark.rutland@arm.com,
Michael Turquette <mturquette@baylibre.com>,
sboyd@kernel.org, geert+renesas@glider.be,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-clk@vger.kernel.org
Subject: Re: [PATCH v6 4/6] ARM: dts: Renesas RZ/N1 SoC base device tree file
Date: Wed, 23 May 2018 10:20:20 +0100 [thread overview]
Message-ID: <CAMMfpEw=6POaZBU9HduKBb8Wk2mH0oAXhCdQo7c+hQWgxka3vA@mail.gmail.com> (raw)
In-Reply-To: <CAMuHMdXETt75rGyYRsNEK0O5CO3A-bG70g=-f23y6PO_uK6rWg@mail.gmail.com>
Hi Geert,
On Wed, 23 May 2018 at 10:12, Geert Uytterhoeven <geert@linux-m68k.org>
wrote:
> Hi Michel,
> On Tue, May 22, 2018 at 12:01 PM, Michel Pollet
> <michel.pollet@bp.renesas.com> wrote:
> > This adds the Renesas RZ/N1D (Part #R9A06G032) SoC bare
> > bone support.
> >
> > This currently only handles generic parts (gic, architected timer)
> > and a UART.
> > For simplicity sake, this also relies on the bootloader to set the
> > pinctrl and clocks.
> >
> > Signed-off-by: Michel Pollet <michel.pollet@bp.renesas.com>
> Thanks for your patch!
> > + #address-cells = <1>;
> > + #size-cells = <1>;
> > +
> > + cpus {
> > + #address-cells = <1>;
> > + #size-cells = <0>;
> > + clocks = <&clock RZN1_DIV_CA7>;
> I think the clocks property should be moved to the individual CPU nodes.
Ah, I had a look around, and I found some instances that are in the cpu
sub-node, and others that are not -- it seems that having it in the cpu
sub-node would implies it's core specific... here if that clock is changed
both cores would change speed...
Either way, it's not used by the kernel in any way at the moment -- I had
hoped cpufreq or something would claim it, but it's not the case.
Thanks,
Michel
next prev parent reply other threads:[~2018-05-23 9:20 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-22 10:01 [PATCH v6 0/6] arm: Base support for Renesas RZN1D-DB Board Michel Pollet
2018-05-22 10:01 ` [PATCH v6 1/6] dt-bindings: arm: Document the RZN1D-DB board Michel Pollet
2018-05-23 8:57 ` Simon Horman
2018-05-23 9:03 ` Geert Uytterhoeven
2018-05-23 9:20 ` Simon Horman
2018-05-22 10:01 ` [PATCH v6 2/6] dt-bindings: Add the rzn1-clocks.h file Michel Pollet
2018-05-22 16:00 ` Rob Herring
2018-05-22 18:44 ` Geert Uytterhoeven
2018-05-23 6:44 ` M P
2018-05-23 7:26 ` Geert Uytterhoeven
2018-05-23 8:17 ` M P
2018-05-25 9:12 ` Geert Uytterhoeven
2018-05-30 13:30 ` Phil Edworthy
2018-05-30 13:36 ` Geert Uytterhoeven
2018-05-30 13:49 ` Phil Edworthy
2018-05-22 10:01 ` [PATCH v6 3/6] dt-bindings: clock: renesas,rzn1-clocks: document RZ/N1 clock driver Michel Pollet
2018-05-22 16:09 ` Rob Herring
2018-05-23 6:52 ` M P
2018-05-23 15:42 ` Rob Herring
2018-05-22 18:42 ` Geert Uytterhoeven
2018-05-22 10:01 ` [PATCH v6 4/6] ARM: dts: Renesas RZ/N1 SoC base device tree file Michel Pollet
2018-05-23 9:06 ` Simon Horman
2018-05-23 9:12 ` Geert Uytterhoeven
2018-05-23 9:20 ` M P [this message]
2018-05-23 11:18 ` Geert Uytterhoeven
2018-05-23 11:53 ` M P
2018-05-22 10:01 ` [PATCH v6 5/6] ARM: dts: Renesas RZN1D-DB Board base file Michel Pollet
2018-05-23 9:13 ` Geert Uytterhoeven
2018-05-24 0:03 ` kbuild test robot
2018-05-22 10:01 ` [PATCH v6 6/6] clk: renesas: Renesas RZ/N1 clock driver Michel Pollet
2018-05-24 0:17 ` kbuild test robot
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='CAMMfpEw=6POaZBU9HduKBb8Wk2mH0oAXhCdQo7c+hQWgxka3vA@mail.gmail.com' \
--to=buserror@gmail.com \
--cc=buserror+upstream@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=horms@verge.net.au \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mark.rutland@arm.com \
--cc=michel.pollet@bp.renesas.com \
--cc=mturquette@baylibre.com \
--cc=phil.edworthy@renesas.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@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 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).