From: Paul Kocialkowski <paulk@sys-base.io>
To: Quentin Schulz <quentin.schulz@cherry.de>
Cc: u-boot@lists.denx.de, Simon Glass <sjg@chromium.org>,
Philipp Tomsich <philipp.tomsich@vrull.eu>,
Kever Yang <kever.yang@rock-chips.com>,
Jonas Karlman <jonas@kwiboo.se>,
Chris Morgan <macromorgan@hotmail.com>,
Tim Lunn <tim@feathertop.org>,
Paul Kocialkowski <contact@paulk.fr>
Subject: Re: [PATCH 1/4] rockchip: rk3399-roc-pc: Hook sysreset gpio to enable full reset
Date: Fri, 27 Sep 2024 11:53:55 +0200 [thread overview]
Message-ID: <ZvaAsxlL3GIGyyVL@collins> (raw)
In-Reply-To: <4304848f-9af5-4991-bfc8-836ccf2abb43@cherry.de>
[-- Attachment #1: Type: text/plain, Size: 1913 bytes --]
Hi Quentin,
Thanks for looking into this!
Le Fri 27 Sep 24, 11:25, Quentin Schulz a écrit :
> I'm not entirely sure on whose side the issue is, but I didn't receive your
> mails, either from the U-Boot mailing list or directly from the Cc field. I
> however could find the patch on lore.kernel.org... and I also received yours
> and Dragan's exchange on patch 4 (but not the patch itself). Any chance you
> received something from my mail server? Does anyone in Cc of this mail
> actually received the mail?
No automatic reply from your mail server and the logs look good on my side,
with a 250 result on all sent patches. Strange indeed...
> > diff --git a/arch/arm/dts/rk3399-roc-pc-u-boot.dtsi b/arch/arm/dts/rk3399-roc-pc-u-boot.dtsi
> > index aecf7dbe383c..883d399a06a3 100644
> > --- a/arch/arm/dts/rk3399-roc-pc-u-boot.dtsi
> > +++ b/arch/arm/dts/rk3399-roc-pc-u-boot.dtsi
> > @@ -7,6 +7,10 @@
> > #include "rk3399-sdram-lpddr4-100.dtsi"
> > / {
> > + config {
> > + sysreset-gpio = <&gpio1 RK_PA6 GPIO_ACTIVE_HIGH>;
>
> I think this is the wrong pin to use.
>
> The routing of GPIO1_A6 is similar on RK3399 Puma and Pine64 RockPro64, but
> it differs massively for the Firefly Roc PC.
>
> However, a similar routing is done for GPIO1_A5 on the Firefly, I believe
> that one is more appropriate. What do you think?
I just double-checked the schematics (ROC_3399_PC), looking at signal OTP_OUT_H
which is definitely connected to GPIO1_A6 (P26).
Also it clearly resets the board when toggled and solves the MMC reset issue
I was having on this exact board, so I'm rather confident that it's the right
one to use :)
Cheers,
Paul
--
Paul Kocialkowski,
Independent contractor - sys-base - https://www.sys-base.io/
Free software developer - https://www.paulk.fr/
Specialist in multimedia, graphics and embedded hardware support with Linux.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-09-27 9:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-26 18:31 [PATCH 1/4] rockchip: rk3399-roc-pc: Hook sysreset gpio to enable full reset Paul Kocialkowski
2024-09-26 18:31 ` [PATCH 2/4] rockchip: rk3399-rockpro64: " Paul Kocialkowski
2024-09-27 9:28 ` Quentin Schulz
2024-11-05 15:38 ` Quentin Schulz
2024-11-05 18:46 ` Paul Kocialkowski
2024-09-26 18:31 ` [PATCH 3/4] rockchip: rk3399-rockpro64: Disable bootstage instrumentation config Paul Kocialkowski
2024-09-30 9:01 ` Peter Robinson
2024-09-30 18:52 ` Simon Glass
2024-09-30 19:07 ` Paul Kocialkowski
2024-10-01 11:19 ` Simon Glass
2024-09-26 18:31 ` [PATCH 4/4] rockchip: Disable DRAM debug by default Paul Kocialkowski
2024-09-26 20:17 ` Dragan Simic
2024-09-26 20:51 ` Paul Kocialkowski
2024-09-26 21:04 ` Dragan Simic
2024-09-26 21:16 ` Paul Kocialkowski
2024-09-26 21:24 ` Dragan Simic
2024-09-26 21:39 ` Paul Kocialkowski
2024-09-26 21:50 ` Dragan Simic
2024-09-27 9:25 ` [PATCH 1/4] rockchip: rk3399-roc-pc: Hook sysreset gpio to enable full reset Quentin Schulz
2024-09-27 9:53 ` Paul Kocialkowski [this message]
2024-09-27 10:07 ` Quentin Schulz
2024-09-27 12:25 ` Paul Kocialkowski
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=ZvaAsxlL3GIGyyVL@collins \
--to=paulk@sys-base.io \
--cc=contact@paulk.fr \
--cc=jonas@kwiboo.se \
--cc=kever.yang@rock-chips.com \
--cc=macromorgan@hotmail.com \
--cc=philipp.tomsich@vrull.eu \
--cc=quentin.schulz@cherry.de \
--cc=sjg@chromium.org \
--cc=tim@feathertop.org \
--cc=u-boot@lists.denx.de \
/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