From: "Marty E. Plummer" <hanetzer@startmail.com>
To: U-Boot Mailing List <u-boot@lists.denx.de>
Cc: Simon Glass <sjg@chromium.org>,
Kever Yang <kever.yang@rock-chips.com>,
Philipp Tomsich <philipp.tomsich@theobroma-systems.com>,
"Marty E. Plummer" <hanetzer@startmail.com>,
Artem Lapkin <email2tema@gmail.com>,
Johan Jonker <jbx6244@gmail.com>,
Philipp Tomsich <philipp.tomsich@vrull.eu>,
Quentin Schulz <quentin.schulz@theobroma-systems.com>,
Xavier Drudis Ferran <xdrudis@tinet.cat>,
linux-rockchip@lists.infradead.org
Subject: [RFC PATCH 0/4] Alternative debug outputs for rockchip devices
Date: Thu, 22 Sep 2022 01:46:59 -0500 [thread overview]
Message-ID: <20220922064704.1740759-1-hanetzer@startmail.com> (raw)
I don't intend for the last change to be included in mainline, I just
need some form of serial output to see why archlinuxarm, alpine linux,
and Fedora workstation all fail to boot on this hardware (rk3399-gru-kevin).
Or at least, I think its failing. At the point of booting the kernel the
bottom inch or so of the screen corrupts a bit and then nothing. It
could be working, but without output on screen or uart2dbga I have no
idea what is going wrong.
I *would* use the uart-to-usb functionality of the rk3399, but as far as
I know this only works with the 2.0, and I'm not sure if those are
available on the rk3399-gru-kevin's type c ports. Do correct me if I'm
wrong.
In addition, the GRF_SOC_CON7:grf_uart_dbg_sel is, as far as I know,
undocumented, outside of the GRF_UART_DBG_SEL_C enum in grf_rk3399,
so the other two options (A and B) are just based on my assumptions.
If someone who *actually knows* could elaborate on it and correct me if
needed I'd greatly appreciate it.
Marty E. Plummer (4):
rockchip: rk3288: enable u-boot.rom for speedy
rockchip: rk3288: enable uart2->usb redirection
rockchip: rk3399: fix typo in grf file
rockchip: rk3399: attempt to redirect uart2dbga to sdcard
arch/arm/dts/rk3399-gru.dtsi | 7 +---
arch/arm/dts/rk3399.dtsi | 4 +-
.../include/asm/arch-rockchip/grf_rk3288.h | 41 +++++++++++++++++++
.../include/asm/arch-rockchip/grf_rk3399.h | 5 ++-
arch/arm/mach-rockchip/rk3288/Kconfig | 2 +
arch/arm/mach-rockchip/rk3288/rk3288.c | 20 +++++++++
arch/arm/mach-rockchip/rk3399/rk3399.c | 18 ++++----
7 files changed, 80 insertions(+), 17 deletions(-)
--
2.37.3
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next reply other threads:[~2022-09-22 6:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 6:46 Marty E. Plummer [this message]
2022-09-22 6:47 ` [RFC PATCH 1/4] rockchip: rk3288: enable u-boot.rom for speedy Marty E. Plummer
2022-09-28 10:20 ` Simon Glass
2022-09-22 6:47 ` [RFC PATCH 2/4] rockchip: rk3288: enable uart2->usb redirection Marty E. Plummer
2022-09-28 10:20 ` Simon Glass
2022-09-22 6:47 ` [RFC PATCH 3/4] rockchip: rk3399: fix typo in grf file Marty E. Plummer
2022-09-28 10:20 ` Simon Glass
2022-09-22 6:47 ` [RFC PATCH 4/4] rockchip: rk3399: attempt to redirect uart2dbga to sdcard Marty E. Plummer
2022-09-28 10:20 ` Simon Glass
2022-09-29 3:24 ` Marty E. Plummer
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=20220922064704.1740759-1-hanetzer@startmail.com \
--to=hanetzer@startmail.com \
--cc=email2tema@gmail.com \
--cc=jbx6244@gmail.com \
--cc=kever.yang@rock-chips.com \
--cc=linux-rockchip@lists.infradead.org \
--cc=philipp.tomsich@theobroma-systems.com \
--cc=philipp.tomsich@vrull.eu \
--cc=quentin.schulz@theobroma-systems.com \
--cc=sjg@chromium.org \
--cc=u-boot@lists.denx.de \
--cc=xdrudis@tinet.cat \
/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