From: Sean Anderson <sean.anderson@linux.dev>
To: linux-arm-kernel@lists.infradead.org,
Adam Ford <aford173@gmail.com>,
Marian-Cristian Rotariu
<marian-cristian.rotariu.rb@bp.renesas.com>,
Biju Das <biju.das@bp.renesas.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Krzysztof Kozlowski <krzk+dt@kernel.org>,
Rob Herring <robh@kernel.org>,
linux-renesas-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, Conor Dooley <conor+dt@kernel.org>,
Magnus Damm <magnus.damm@gmail.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Olof Johansson <olof@lixom.net>, Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH 0/2] arm64: dts: renesas: Add SD/OE pin properties
Date: Thu, 26 Sep 2024 14:24:12 -0400 [thread overview]
Message-ID: <cb716925-f6c0-4a00-8cfd-b30aed132fd1@linux.dev> (raw)
In-Reply-To: <20240926180903.479895-1-sean.anderson@linux.dev>
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
next prev parent reply other threads:[~2024-09-26 18:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-26 18:09 [PATCH 0/2] arm64: dts: renesas: Add SD/OE pin properties Sean Anderson
2024-09-26 18:09 ` [PATCH 1/2] arm64: dts: renesas: salvator-xs: " Sean Anderson
2024-09-27 10:34 ` Geert Uytterhoeven
2024-10-07 12:12 ` Geert Uytterhoeven
2024-09-26 18:09 ` [PATCH 2/2] arm64: dts: renesas: ulcb: " Sean Anderson
2024-09-27 10:34 ` Geert Uytterhoeven
2024-10-07 12:14 ` Geert Uytterhoeven
2024-09-26 18:24 ` Sean Anderson [this message]
2024-09-27 10:07 ` [PATCH 0/2] arm64: dts: renesas: " Geert Uytterhoeven
2024-09-27 12:19 ` Adam Ford
2024-09-27 12:38 ` Geert Uytterhoeven
2024-09-27 12:51 ` Adam Ford
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=cb716925-f6c0-4a00-8cfd-b30aed132fd1@linux.dev \
--to=sean.anderson@linux.dev \
--cc=aford173@gmail.com \
--cc=arnd@arndb.de \
--cc=biju.das@bp.renesas.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=krzk+dt@kernel.org \
--cc=laurent.pinchart@ideasonboard.com \
--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=marian-cristian.rotariu.rb@bp.renesas.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).