[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <cb716925-f6c0-4a00-8cfd-b30aed132fd1@linux.dev>
Date: Thu, 26 Sep 2024 14:24:12 -0400
From: Sean Anderson <sean.anderson@...ux.dev>
To: linux-arm-kernel@...ts.infradead.org, Adam Ford <aford173@...il.com>,
Marian-Cristian Rotariu <marian-cristian.rotariu.rb@...renesas.com>,
Biju Das <biju.das@...renesas.com>,
Laurent Pinchart <laurent.pinchart@...asonboard.com>
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>, Olof Johansson
<olof@...om.net>, Arnd Bergmann <arnd@...db.de>
Subject: Re: [PATCH 0/2] arm64: dts: renesas: Add SD/OE pin properties
On 9/26/24 14:09, Sean Anderson wrote:
> 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.
+CC the people I meant to CC in the first place
Powered by blists - more mailing lists