From: John Clark <inindev@gmail.com>
To: Kever Yang <kever.yang@rock-chips.com>
Cc: John Clark <inindev@gmail.com>,
Chris Morgan <macromorgan@hotmail.com>,
Eugen Hristev <eugen.hristev@collabora.com>,
Jagan Teki <jagan@edgeble.ai>, Johan Jonker <jbx6244@gmail.com>,
Jonas Karlman <jonas@kwiboo.se>,
Massimo Pegorer <massimo.pegorer+oss@gmail.com>,
Michal Simek <michal.simek@amd.com>,
Nicolas Frattaroli <frattaroli.nicolas@gmail.com>,
Simon Glass <sjg@chromium.org>,
u-boot@lists.denx.de
Subject: [PATCH v4 0/1] Empirical testing suggests that the rk3588 variants require additional spi detection handling based on iomux settings.
Date: Fri, 13 Oct 2023 01:19:21 +0000 [thread overview]
Message-ID: <20231013012025.11694-1-inindev@gmail.com> (raw)
Jonas Karlman is currently investigating a more comprehensive spi flash detection solution to support all rk3588 iomux variations.
This v4 patch suppresses spi flash support which will be supplied as a subsequent patch.
Changes in v4:
- removed SPI support as Jonas Karlman will be providing a comprehensive solution to support all rk3588 iomux variations.
Changes in v3:
- The vendor device tree uses "FriendlyElec NanoPC-T6" therefore, use FriendlyElec over FriendlyARM.
- Bug: use IS_ENABLED(CONFIG_TARGET_NANOPCT6_RK3588) rather than CONFIG_IS_ENABLED(TARGET_NANOPCT6_RK3588)
Changes in v2:
- resync dt from linux next
- config changes:
-CONFIG_PCI_INIT_R=y
-CONFIG_SYS_SPI_U_BOOT_OFFS=0x100000
+CONFIG_SYS_SPI_U_BOOT_OFFS=0x60000
-CONFIG_REGULATOR_PWM=y
-# CONFIG_USB_XHCI_DWC3_OF_SIMPLE is not set
-CONFIG_SPL_USB_DWC3_GENERIC=y
- added board files:
Kconfig, MAINTAINERS, Makefile, nanopct6-rk3588.c, nanopct6-rk3588.h
- improved BROM_LAST_BOOTSOURCE handling for SPI NOR
John Clark (1):
board: rockchip: add FriendlyElec NanoPC-T6 rk3588 board
arch/arm/dts/Makefile | 1 +
arch/arm/dts/rk3588-nanopc-t6-u-boot.dtsi | 36 +
arch/arm/dts/rk3588-nanopc-t6.dts | 916 ++++++++++++++++++
arch/arm/mach-rockchip/rk3588/Kconfig | 46 +
board/friendlyelec/nanopc-t6-rk3588/Kconfig | 15 +
.../friendlyelec/nanopc-t6-rk3588/MAINTAINERS | 9 +
board/friendlyelec/nanopc-t6-rk3588/Makefile | 6 +
.../nanopc-t6-rk3588/nanopc-t6-rk3588.c | 39 +
configs/nanopc-t6-rk3588_defconfig | 108 +++
doc/board/rockchip/rockchip.rst | 1 +
include/configs/nanopc-t6-rk3588.h | 15 +
11 files changed, 1192 insertions(+)
create mode 100644 arch/arm/dts/rk3588-nanopc-t6-u-boot.dtsi
create mode 100644 arch/arm/dts/rk3588-nanopc-t6.dts
create mode 100644 board/friendlyelec/nanopc-t6-rk3588/Kconfig
create mode 100644 board/friendlyelec/nanopc-t6-rk3588/MAINTAINERS
create mode 100644 board/friendlyelec/nanopc-t6-rk3588/Makefile
create mode 100644 board/friendlyelec/nanopc-t6-rk3588/nanopc-t6-rk3588.c
create mode 100644 configs/nanopc-t6-rk3588_defconfig
create mode 100644 include/configs/nanopc-t6-rk3588.h
--
2.42.0
next reply other threads:[~2023-10-13 2:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-13 1:19 John Clark [this message]
2023-10-13 1:19 ` [PATCH v4 1/1] board: rockchip: add FriendlyElec NanoPC-T6 rk3588 board John Clark
2023-10-13 7:16 ` Kever Yang
2023-10-17 20:26 ` Jonas Karlman
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=20231013012025.11694-1-inindev@gmail.com \
--to=inindev@gmail.com \
--cc=eugen.hristev@collabora.com \
--cc=frattaroli.nicolas@gmail.com \
--cc=jagan@edgeble.ai \
--cc=jbx6244@gmail.com \
--cc=jonas@kwiboo.se \
--cc=kever.yang@rock-chips.com \
--cc=macromorgan@hotmail.com \
--cc=massimo.pegorer+oss@gmail.com \
--cc=michal.simek@amd.com \
--cc=sjg@chromium.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