From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Simon Horman <horms+renesas@verge.net.au>
Cc: Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Magnus Damm <magnus.damm@gmail.com>
Subject: Re: [PATCH v2 2/2] arm64: dts: r8a7796: Add OPPs table for cpu devices
Date: Mon, 9 Oct 2017 13:56:17 +0200 [thread overview]
Message-ID: <CAMuHMdWnpx4UUSgWv5oPyqPBb2EHtGH8BpZ_zxtv+BdWwgmNaw@mail.gmail.com> (raw)
In-Reply-To: <1507209984-17123-3-git-send-email-horms+renesas@verge.net.au>
Hi Simon,
On Thu, Oct 5, 2017 at 3:26 PM, Simon Horman <horms+renesas@verge.net.au> wrote:
> From: Dien Pham <dien.pham.ry@rvc.renesas.com>
>
> Current, OPP tables are defined temporary,
> they are being evaluated and adjust in future.
>
> Based in part on work by Hien Dang.
> --- a/arch/arm64/boot/dts/renesas/r8a7796.dtsi
> +++ b/arch/arm64/boot/dts/renesas/r8a7796.dtsi
> @@ -108,6 +116,56 @@
> };
> };
>
> + cluster0_opp: opp_table0 {
> + compatible = "operating-points-v2";
> + opp-shared;
> +
> + opp@500000000 {
As reported before, with "make dtbs W=1":
arch/arm64/boot/dts/renesas/r8a7795-salvator-x.dtb: Warning
(unit_address_vs_reg): Node /opp_table0/opp@500000000 has a unit name,
but no reg property
etc.
opp-500000000
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
WARNING: multiple messages have this Message-ID (diff)
From: geert@linux-m68k.org (Geert Uytterhoeven)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/2] arm64: dts: r8a7796: Add OPPs table for cpu devices
Date: Mon, 9 Oct 2017 13:56:17 +0200 [thread overview]
Message-ID: <CAMuHMdWnpx4UUSgWv5oPyqPBb2EHtGH8BpZ_zxtv+BdWwgmNaw@mail.gmail.com> (raw)
In-Reply-To: <1507209984-17123-3-git-send-email-horms+renesas@verge.net.au>
Hi Simon,
On Thu, Oct 5, 2017 at 3:26 PM, Simon Horman <horms+renesas@verge.net.au> wrote:
> From: Dien Pham <dien.pham.ry@rvc.renesas.com>
>
> Current, OPP tables are defined temporary,
> they are being evaluated and adjust in future.
>
> Based in part on work by Hien Dang.
> --- a/arch/arm64/boot/dts/renesas/r8a7796.dtsi
> +++ b/arch/arm64/boot/dts/renesas/r8a7796.dtsi
> @@ -108,6 +116,56 @@
> };
> };
>
> + cluster0_opp: opp_table0 {
> + compatible = "operating-points-v2";
> + opp-shared;
> +
> + opp at 500000000 {
As reported before, with "make dtbs W=1":
arch/arm64/boot/dts/renesas/r8a7795-salvator-x.dtb: Warning
(unit_address_vs_reg): Node /opp_table0/opp at 500000000 has a unit name,
but no reg property
etc.
opp-500000000
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-10-09 11:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-05 13:26 [PATCH v2 0/2] arm64: dts: r8a779[56]: Add OPPs table for cpu devices Simon Horman
2017-10-05 13:26 ` Simon Horman
2017-10-05 13:26 ` [PATCH v2 1/2] arm64: dts: r8a7795: " Simon Horman
2017-10-05 13:26 ` Simon Horman
2017-10-09 11:58 ` Geert Uytterhoeven
2017-10-09 11:58 ` Geert Uytterhoeven
2017-10-05 13:26 ` [PATCH v2 2/2] arm64: dts: r8a7796: " Simon Horman
2017-10-05 13:26 ` Simon Horman
2017-10-05 15:04 ` Sudeep Holla
2017-10-05 15:04 ` Sudeep Holla
2017-10-09 11:57 ` Geert Uytterhoeven
2017-10-09 11:57 ` Geert Uytterhoeven
2017-10-10 14:33 ` Sudeep Holla
2017-10-10 14:33 ` Sudeep Holla
2017-10-10 14:44 ` Geert Uytterhoeven
2017-10-10 14:44 ` Geert Uytterhoeven
2017-10-10 7:25 ` Simon Horman
2017-10-10 7:25 ` Simon Horman
2017-10-09 11:56 ` Geert Uytterhoeven [this message]
2017-10-09 11:56 ` Geert Uytterhoeven
2017-10-10 7:25 ` Simon Horman
2017-10-10 7:25 ` 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=CAMuHMdWnpx4UUSgWv5oPyqPBb2EHtGH8BpZ_zxtv+BdWwgmNaw@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=horms+renesas@verge.net.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
/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.