From: Geert Uytterhoeven <geert+renesas@glider.be>
To: arm-soc <arm@kernel.org>, soc <soc@kernel.org>
Cc: Magnus Damm <magnus.damm@gmail.com>,
linux-arm-kernel@lists.infradead.org,
linux-renesas-soc@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [GIT PULL 1/2] Renesas ARM DT updates for v5.15 (take two)
Date: Fri, 13 Aug 2021 12:22:35 +0200 [thread overview]
Message-ID: <cover.1628849623.git.geert+renesas@glider.be> (raw)
Message-ID: <20210813102235.qWErulSAXgm0LFXZ6pSa40F3ShYkWhF4fDq4HjIdAzU@z> (raw)
In-Reply-To: <cover.1628849621.git.geert+renesas@glider.be>
The following changes since commit 651f8cffade8615bb4fce1ecb3a929892c5e60d7:
arm64: dts: renesas: r8a77961: Add iommus to ipmmu_ds[01] related nodes (2021-07-30 15:07:25 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-devel.git tags/renesas-arm-dt-for-v5.15-tag2
for you to fetch changes up to 13bf92e6dec0e2be1ef0c7dd483f2d8b34eaa905:
dt-bindings: i2c: renesas,riic: Make interrupt-names required (2021-08-12 12:43:41 +0200)
----------------------------------------------------------------
Renesas ARM DT updates for v5.15 (take two)
- Pin control, ADC, and CANFD support for the RZ/G2L SoC,
- Add interrupt-names properties to the Renesas RZ/A and RZ/G2L I2C
Bus Interface.
----------------------------------------------------------------
Geert Uytterhoeven (5):
Merge tag 'renesas-r9a07g044-dt-binding-defs-tag2' into HEAD
dt-bindings: i2c: renesas,riic: Add interrupt-names
ARM: dts: rza: Add I2C interrupt-names
arm64: dts: renesas: r9a07g044: Add I2C interrupt-names
dt-bindings: i2c: renesas,riic: Make interrupt-names required
Lad Prabhakar (4):
dt-bindings: clock: r9a07g044-cpg: Add entry for P0_DIV2 core clock
arm64: dts: renesas: r9a07g044: Add pinctrl node
arm64: dts: renesas: r9a07g044: Add ADC node
arm64: dts: renesas: r9a07g044: Add CANFD node
.../devicetree/bindings/i2c/renesas,riic.yaml | 30 ++++--
arch/arm/boot/dts/r7s72100.dtsi | 8 ++
arch/arm/boot/dts/r7s9210.dtsi | 8 ++
arch/arm64/boot/dts/renesas/r9a07g044.dtsi | 104 +++++++++++++++++++++
include/dt-bindings/clock/r9a07g044-cpg.h | 1 +
5 files changed, 143 insertions(+), 8 deletions(-)
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-08-13 10:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-13 10:22 [GIT PULL 0/2] Renesas SoC updates for v5.15 (take two) Geert Uytterhoeven
2021-08-13 10:22 ` Geert Uytterhoeven
2021-08-13 10:22 ` Geert Uytterhoeven [this message]
2021-08-13 10:22 ` [GIT PULL 1/2] Renesas ARM DT " Geert Uytterhoeven
[not found] ` <20210816212048.n3fSHVCuVwZTheK8lN7LDryA96x8-mSsbm_GpgprQ0Y@z>
2021-08-16 21:20 ` Arnd Bergmann
2021-08-13 10:22 ` [GIT PULL 2/2] Renesas driver " Geert Uytterhoeven
2021-08-13 10:22 ` Geert Uytterhoeven
[not found] ` <20210818133437.FK5f4rqsOSGBN5rvns9NqtVuMj6BOlIakVeNeaoMIJc@z>
2021-08-18 13:34 ` Arnd Bergmann
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=cover.1628849623.git.geert+renesas@glider.be \
--to=geert+renesas@glider.be \
--cc=arm@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=soc@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).