From: Sean Anderson <sean.anderson@linux.dev>
To: Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>,
linux-arm-kernel@lists.infradead.org
Cc: linux-renesas-soc@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>,
Rob Herring <robh@kernel.org>,
devicetree@vger.kernel.org, Magnus Damm <magnus.damm@gmail.com>,
linux-kernel@vger.kernel.org,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Adam Ford <aford173@gmail.com>,
Sean Anderson <sean.anderson@linux.dev>
Subject: [PATCH 0/3] arm64: dts: renesas: Add SD/OE pin properties (part B)
Date: Fri, 27 Sep 2024 16:13:10 -0400 [thread overview]
Message-ID: <20240927201313.624762-1-sean.anderson@linux.dev> (raw)
Linux can configure almost every part of this clock generator without
relying on the OTP settings. However, the correct configuration for the
SD/OE pin cannot be determined automatically. Therefore, add the
appropriate properties to configure this pin.
Thanks to everyone who replied to part A with board info!
Sean Anderson (3):
arm64: dts: renesas: salvator-x: Add SD/OE pin properties
arm64: dts: renesas: hihope: Add SD/OE pin properties
arm64: dts: renesas: beacon: Add SD/OE pin properties
arch/arm64/boot/dts/renesas/beacon-renesom-baseboard.dtsi | 2 ++
arch/arm64/boot/dts/renesas/beacon-renesom-som.dtsi | 2 ++
arch/arm64/boot/dts/renesas/hihope-common.dtsi | 2 ++
arch/arm64/boot/dts/renesas/salvator-x.dtsi | 2 ++
4 files changed, 8 insertions(+)
--
2.35.1.1320.gc452695387.dirty
next reply other threads:[~2024-09-27 20:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-27 20:13 Sean Anderson [this message]
2024-09-27 20:13 ` [PATCH 1/3] arm64: dts: renesas: salvator-x: Add SD/OE pin properties Sean Anderson
2024-10-07 12:11 ` Geert Uytterhoeven
2024-09-27 20:13 ` [PATCH 2/3] arm64: dts: renesas: hihope: " Sean Anderson
2024-10-07 12:11 ` Geert Uytterhoeven
2024-09-27 20:13 ` [PATCH 3/3] arm64: dts: renesas: beacon: " Sean Anderson
2024-10-07 12:12 ` 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=20240927201313.624762-1-sean.anderson@linux.dev \
--to=sean.anderson@linux.dev \
--cc=aford173@gmail.com \
--cc=arnd@arndb.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=olof@lixom.net \
--cc=robh@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).