From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Julien Massot <julien.massot@iot.bzh>
Cc: "Björn Andersson" <bjorn.andersson@linaro.org>,
"Mathieu Poirier" <mathieu.poirier@linaro.org>,
"Rob Herring" <robh+dt@kernel.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
"open list:REMOTE PROCESSOR (REMOTEPROC) SUBSYSTEM"
<linux-remoteproc@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>
Subject: Re: [PATCH v1 2/3] arm64: dts: renesas: r8a77951: Add CR7 realtime processor
Date: Mon, 10 Jan 2022 14:00:05 +0100 [thread overview]
Message-ID: <CAMuHMdVR6EZa44GJCecWgN+6GNESCyNCsenaEPW7qa-W8-_evA@mail.gmail.com> (raw)
In-Reply-To: <20211115135032.129227-3-julien.massot@iot.bzh>
Hi Julien,
On Mon, Nov 15, 2021 at 2:50 PM Julien Massot <julien.massot@iot.bzh> wrote:
> r8a77951 as some other members of rcar gen3 soc series
> has a Cortex R7 processor.
> This processor shares the same mapped devices and memory mapping.
>
> Choose 0x40040000 area to store the Cortex-R7 firmware.
>
> Signed-off-by: Julien Massot <julien.massot@iot.bzh>
Thanks for your patch!
> No change since RFC, Geert most likely it sounds better
> to drop this patch in v2 ?
Indeed, cfr. my comments below.
> --- a/arch/arm64/boot/dts/renesas/r8a77951-ulcb.dts
> +++ b/arch/arm64/boot/dts/renesas/r8a77951-ulcb.dts
> @@ -34,6 +34,16 @@ memory@700000000 {
> device_type = "memory";
> reg = <0x7 0x00000000 0x0 0x40000000>;
> };
> +
> + reserved-memory {
> + #address-cells = <2>;
> + #size-cells = <2>;
> +
> + cr7_ram: cr7_ram@40040000 {
> + no-map;
> + reg = <0x0 0x40040000 0x0 0x1fc0000>;
> + };
> + };
Tgis depends on a specific configuration, and is thus not suitable for
upstream.
> };
>
> &du {
> @@ -48,3 +58,8 @@ &du {
> clock-names = "du.0", "du.1", "du.2", "du.3",
> "dclkin.0", "dclkin.1", "dclkin.2", "dclkin.3";
> };
> +
> +&cr7_rproc {
> + memory-region = <&cr7_ram>;
> + status = "okay";
> +};
> diff --git a/arch/arm64/boot/dts/renesas/r8a77951.dtsi b/arch/arm64/boot/dts/renesas/r8a77951.dtsi
> index 1768a3e6bb8d..3ee247fc5aec 100644
> --- a/arch/arm64/boot/dts/renesas/r8a77951.dtsi
> +++ b/arch/arm64/boot/dts/renesas/r8a77951.dtsi
> @@ -366,6 +366,13 @@ soc: soc {
> #size-cells = <2>;
> ranges;
>
> + cr7_rproc: cr7 {
> + compatible = "renesas,rcar-cr7";
> + power-domains = <&sysc R8A7795_PD_CR7>;
> + resets = <&cpg 222>;
> + status = "disabled";
> + };
> +
This part is generic, but I think the cr7 node should be moved outside
the soc node (like the PMUs and the ARMv8 timer), as it does not have
a unit address.
> rwdt: watchdog@e6020000 {
> compatible = "renesas,r8a7795-wdt", "renesas,rcar-gen3-wdt";
> reg = <0 0xe6020000 0 0x0c>;
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:[~2022-01-10 13:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-15 13:50 [PATCH v1 0/3] Initial Renesas R-Car remoteproc support Julien Massot
2021-11-15 13:50 ` [PATCH v1 1/3] dt-bindings: remoteproc: Add Renesas R-Car Julien Massot
2021-11-29 22:01 ` Rob Herring
2021-11-30 8:51 ` Julien Massot
2021-11-15 13:50 ` [PATCH v1 2/3] arm64: dts: renesas: r8a77951: Add CR7 realtime processor Julien Massot
2022-01-10 13:00 ` Geert Uytterhoeven [this message]
2021-11-15 13:50 ` [PATCH v1 3/3] remoteproc: Add Renesas rcar driver Julien Massot
2021-11-15 14:12 ` Biju Das
2021-11-15 14:41 ` Julien Massot
2021-11-15 15:17 ` Biju Das
2021-11-22 18:37 ` Mathieu Poirier
2021-11-24 11:07 ` Julien Massot
2021-11-24 17:35 ` Mathieu Poirier
2021-11-15 18:10 ` [PATCH v1 0/3] Initial Renesas R-Car remoteproc support Mathieu Poirier
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=CAMuHMdVR6EZa44GJCecWgN+6GNESCyNCsenaEPW7qa-W8-_evA@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=julien.massot@iot.bzh \
--cc=linux-remoteproc@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=robh+dt@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).