[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20240926180903.479895-1-sean.anderson@linux.dev>
Date: Thu, 26 Sep 2024 14:09:01 -0400
From: Sean Anderson <sean.anderson@...ux.dev>
To: Arnd Bergmann <arnd@...db.de>,
Olof Johansson <olof@...om.net>,
linux-arm-kernel@...ts.infradead.org
Cc: Krzysztof Kozlowski <krzk+dt@...nel.org>,
Rob Herring <robh@...nel.org>,
linux-renesas-soc@...r.kernel.org,
linux-kernel@...r.kernel.org,
devicetree@...r.kernel.org,
Conor Dooley <conor+dt@...nel.org>,
Magnus Damm <magnus.damm@...il.com>,
Geert Uytterhoeven <geert+renesas@...der.be>,
Sean Anderson <sean.anderson@...ux.dev>
Subject: [PATCH 0/2] arm64: dts: renesas: Add SD/OE pin properties
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.
I have CC'd some people who appear to have access to the following
boards which use the versaclock5:
- Salvator-X
- HiHope RZ/G2[MN] Main Board
- Beacon Embedded Works RZ/G2N Development Kit
as I could not find schematics for these boards. You can help me out by
(pick one):
- Run the following command and send me the output:
$ grep 10: /sys/kernel/debug/regmap/*-006a/registers
- Measure the voltage on the SD/OE pin on a functioning board.
- Inspect (or send me) the schematic to determine the state of the SD/OE
pin during normal operation.
My suspicion is that all of these boards use the same configuration
(SD/OE pin tied high) owing to their common design heritage. Thanks in
advance.
Sean Anderson (2):
arm64: dts: renesas: salvator-xs: Add SD/OE pin properties
arm64: dts: renesas: ulcb: Add SD/OE pin properties
arch/arm64/boot/dts/renesas/salvator-xs.dtsi | 2 ++
arch/arm64/boot/dts/renesas/ulcb.dtsi | 2 ++
2 files changed, 4 insertions(+)
--
2.35.1.1320.gc452695387.dirty
Powered by blists - more mailing lists