From: Eugeniu Rosca <erosca@de.adit-jv.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Magnus Damm <magnus.damm@gmail.com>,
Eugeniu Rosca <erosca@de.adit-jv.com>,
<linux-renesas-soc@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>,
Eugeniu Rosca <roscaeugeniu@gmail.com>
Subject: Re: [PATCH v2 0/6] arm64: dts: renesas: r8a77961: Add more device nodes
Date: Tue, 17 Dec 2019 13:01:16 +0100 [thread overview]
Message-ID: <20191217120116.GA11814@vmlxhi-102.adit-jv.com> (raw)
In-Reply-To: <20191216124740.16647-1-geert+renesas@glider.be>
Hi Geert,
On Mon, Dec 16, 2019 at 01:47:34PM +0100, Geert Uytterhoeven wrote:
> Hi all,
>
> This patch series broadens support for the R-Car M3-W+ (aka R-Car M3-W
> ES3.0) Soc (R8A77961), by adding more device nodes to its DT source
> file, up to what can be tested reasonably using remote access.
> For your convenience, it is available in the topic/r8a77961-v2 branch of
> my renesas-drivers git repository at
> git://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-drivers.git.
I only see below r8a77961.dtsi commit on topic/r8a77961-v2:
8e4529f2ac8293 ("arm64: dts: renesas: Add Renesas R8A77961 SoC support")
It looks like the patches are from one of below branches?
- topic/r8a77961-extra-v2
- topic/topic/r8a77961-extra-v1
> Changes compared to v1:
> - Group SYS-DMAC interrupt specifiers.
>
> This has been tested on a Salvator-XS development board.
> More details can be found in the individual patches.
>
> To be queued in renesas-devel for v5.6.
> Thanks!
>
> Geert Uytterhoeven (6):
> arm64: dts: renesas: r8a77961: Add RWDT node
> arm64: dts: renesas: r8a77961: Add GPIO nodes
> arm64: dts: renesas: r8a77961: Add RAVB node
> arm64: dts: renesas: r8a77961: Add SYS-DMAC nodes
> arm64: dts: renesas: r8a77961: Add I2C nodes
> arm64: dts: renesas: r8a77961: Add SDHI nodes
Thanks for your time and for the helpful minimal test-cases, which
can be reused in future bring-ups.
--
Best Regards,
Eugeniu
next prev parent reply other threads:[~2019-12-17 12:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-16 12:47 [PATCH v2 0/6] arm64: dts: renesas: r8a77961: Add more device nodes Geert Uytterhoeven
2019-12-16 12:47 ` [PATCH v2 1/6] arm64: dts: renesas: r8a77961: Add RWDT node Geert Uytterhoeven
2019-12-17 14:10 ` Eugeniu Rosca
2019-12-16 12:47 ` [PATCH v2 2/6] arm64: dts: renesas: r8a77961: Add GPIO nodes Geert Uytterhoeven
2019-12-17 14:19 ` Eugeniu Rosca
2019-12-16 12:47 ` [PATCH v2 3/6] arm64: dts: renesas: r8a77961: Add RAVB node Geert Uytterhoeven
2019-12-17 14:07 ` Eugeniu Rosca
2019-12-16 12:47 ` [PATCH v2 4/6] arm64: dts: renesas: r8a77961: Add SYS-DMAC nodes Geert Uytterhoeven
2019-12-17 16:38 ` Eugeniu Rosca
2019-12-16 12:47 ` [PATCH v2 5/6] arm64: dts: renesas: r8a77961: Add I2C nodes Geert Uytterhoeven
2019-12-17 14:14 ` Eugeniu Rosca
2019-12-16 12:47 ` [PATCH v2 6/6] arm64: dts: renesas: r8a77961: Add SDHI nodes Geert Uytterhoeven
2019-12-17 14:30 ` Eugeniu Rosca
2019-12-17 12:01 ` Eugeniu Rosca [this message]
2019-12-17 12:19 ` [PATCH v2 0/6] arm64: dts: renesas: r8a77961: Add more device nodes Geert Uytterhoeven
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=20191217120116.GA11814@vmlxhi-102.adit-jv.com \
--to=erosca@de.adit-jv.com \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=roscaeugeniu@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 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).