From: Jagan Teki <jagan@amarulasolutions.com>
To: u-boot@lists.denx.de
Subject: [PATCH v4 0/5] roc-rk3399-pc: Custom SPL init
Date: Thu, 18 Jun 2020 21:09:43 +0530 [thread overview]
Message-ID: <20200618153948.218506-1-jagan@amarulasolutions.com> (raw)
This series supports custom initialization code required for
roc-rk3399-pc board on SPL stage.
Here is the previous v3 this series[1].
Now this series is well mature code handling to add custom
spl_board_init code parts.
roc-rk3399-pc would require custom leds initialization based
on user intervention of the power key. This code handles the
user intervention via SPI environment variable. If someone
or production systems wants this feature then 'pwr_key' has
to be set otherwise it is normal like other rk3399 boards
in Mainline.
Changes for v4:
- enable SPL_BOARD_INIT in all platforms
Changes for v3:
- support leds on SPL
- support env 'pwr_key'
[1] https://patchwork.ozlabs.org/project/uboot/cover/20200608183144.26809-1-jagan at amarulasolutions.com
Any inputs?
Jagan.
Jagan Teki (5):
rockchip: spl: Add spl_board_init
rk3399: spl: Print SPL banner after relocation
roc-rk3399-pc: Move leds setup in SPL
rockchip: Separate the reset cause from display cpuinfo
roc-rk3399-pc: Set LED only during POR and pwr_key=y
arch/arm/Kconfig | 1 +
arch/arm/include/asm/arch-rockchip/cru.h | 2 +
arch/arm/mach-rockchip/Kconfig | 2 -
arch/arm/mach-rockchip/Makefile | 5 +-
arch/arm/mach-rockchip/cpu-info.c | 20 +++---
arch/arm/mach-rockchip/rk3188/rk3188.c | 2 +-
arch/arm/mach-rockchip/rk3399/rk3399.c | 57 -----------------
arch/arm/mach-rockchip/spl.c | 11 ++++
arch/arm/mach-rockchip/tpl.c | 7 ---
board/firefly/firefly-rk3288/firefly-rk3288.c | 2 +-
board/firefly/roc-pc-rk3399/Makefile | 4 ++
board/firefly/roc-pc-rk3399/roc-pc-rk3399.c | 21 -------
board/firefly/roc-pc-rk3399/spl.c | 56 +++++++++++++++++
board/phytec/phycore_rk3288/phycore-rk3288.c | 2 +-
.../puma_rk3399/puma-rk3399.c | 61 +++++++++++++++++++
configs/roc-pc-mezzanine-rk3399_defconfig | 6 +-
configs/roc-pc-rk3399_defconfig | 6 +-
17 files changed, 162 insertions(+), 103 deletions(-)
create mode 100644 board/firefly/roc-pc-rk3399/spl.c
--
2.25.1
next reply other threads:[~2020-06-18 15:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-18 15:39 Jagan Teki [this message]
2020-06-18 15:39 ` [PATCH v4 1/5] rockchip: spl: Add spl_board_init Jagan Teki
2020-06-28 3:06 ` Kever Yang
2020-06-18 15:39 ` [PATCH v4 2/5] rk3399: spl: Print SPL banner after relocation Jagan Teki
2020-06-28 2:56 ` Kever Yang
2020-07-10 10:19 ` Jagan Teki
2020-06-18 15:39 ` [PATCH v4 3/5] roc-rk3399-pc: Move leds setup in SPL Jagan Teki
2020-06-28 2:50 ` Kever Yang
2020-06-18 15:39 ` [PATCH v4 4/5] rockchip: Separate the reset cause from display cpuinfo Jagan Teki
2020-06-28 2:46 ` Kever Yang
2020-07-13 19:57 ` Jagan Teki
2020-06-18 15:39 ` [PATCH v4 5/5] roc-rk3399-pc: Set LED only during POR and pwr_key=y Jagan Teki
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=20200618153948.218506-1-jagan@amarulasolutions.com \
--to=jagan@amarulasolutions.com \
--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