From: Geert Uytterhoeven <geert+renesas@glider.be>
To: Magnus Damm <magnus.damm@gmail.com>
Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>,
Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>,
linux-renesas-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [PATCH v2 0/3] arm64: dts: renesas: falcon: Add I2C EEPROMs and sub-boards
Date: Thu, 4 Mar 2021 16:32:54 +0100 [thread overview]
Message-ID: <20210304153257.4059277-1-geert+renesas@glider.be> (raw)
Hi all,
This patch series adds the device nodes for all I2C EEPROMs in the
Falcon board stack. As some EEPROMs are located on sub-boards,
it also introduces individual .dtsi files for these sub-boards.
Note that (for now) these sub-boards don't have compatible values or
model strings, as I think this needs more discussion.
This has been tested on the Falcon boards in Magnus' and Kieran's farms.
The EEPROM on the CPU board in Magnus' farm contains some data.
All other EEPROMs are present, but in pristine state (all ones).
Changes compared to v1:
- Move EEPROMs in sub-boards to separate .dtsi files and patches.
To be queued in renesas-devel for v5.13.
Thanks for your comments!
Geert Uytterhoeven (3):
arm64: dts: renesas: falcon: Add I2C EEPROM nodes
arm64: dts: renesas: falcon: Add CSI/DSI sub-board
arm64: dts: renesas: falcon: Add Ethernet sub-board
.../boot/dts/renesas/r8a779a0-falcon-cpu.dtsi | 7 +++++++
.../boot/dts/renesas/r8a779a0-falcon-csi-dsi.dtsi | 15 +++++++++++++++
.../dts/renesas/r8a779a0-falcon-ethernet.dtsi | 15 +++++++++++++++
arch/arm64/boot/dts/renesas/r8a779a0-falcon.dts | 11 +++++++++++
4 files changed, 48 insertions(+)
create mode 100644 arch/arm64/boot/dts/renesas/r8a779a0-falcon-csi-dsi.dtsi
create mode 100644 arch/arm64/boot/dts/renesas/r8a779a0-falcon-ethernet.dtsi
--
2.25.1
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 reply other threads:[~2021-03-04 15:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-04 15:32 Geert Uytterhoeven [this message]
2021-03-04 15:32 ` [PATCH v2 1/3] arm64: dts: renesas: falcon: Add I2C EEPROM nodes Geert Uytterhoeven
2021-03-04 15:32 ` [PATCH v2 2/3] arm64: dts: renesas: falcon: Add CSI/DSI sub-board Geert Uytterhoeven
2021-03-04 15:32 ` [PATCH v2 3/3] arm64: dts: renesas: falcon: Add Ethernet sub-board Geert Uytterhoeven
2021-03-05 14:15 ` [PATCH v2 0/3] arm64: dts: renesas: falcon: Add I2C EEPROMs and sub-boards Wolfram Sang
2021-03-05 14:18 ` Geert Uytterhoeven
2021-03-05 14:19 ` Wolfram Sang
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=20210304153257.4059277-1-geert+renesas@glider.be \
--to=geert+renesas@glider.be \
--cc=devicetree@vger.kernel.org \
--cc=kieran.bingham+renesas@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=wsa+renesas@sang-engineering.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).