All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alper Nebi Yasak <alpernebiyasak@gmail.com>
To: u-boot@lists.denx.de
Cc: Artem Lapkin <email2tema@gmail.com>,
	Christian Hewitt <christianshewitt@gmail.com>,
	Fabio Estevam <festevam@denx.de>,
	Jagan Teki <jagan@amarulasolutions.com>,
	Lokesh Vutla <lokeshvutla@ti.com>,
	"Marty E . Plummer" <hanetzer@startmail.com>,
	Heiko Schocher <hs@denx.de>, Simon Glass <sjg@chromium.org>,
	Andre Przywara <andre.przywara@arm.com>,
	Neil Armstrong <narmstrong@baylibre.com>,
	Tim Harvey <tharvey@gateworks.com>,
	Johan Jonker <jbx6244@gmail.com>,
	Kever Yang <kever.yang@rock-chips.com>,
	Alexandre Vicenzi <alexandre.vicenzi@suse.com>,
	Peter Robinson <pbrobinson@gmail.com>,
	Philipp Tomsich <philipp.tomsich@vrull.eu>,
	Alper Nebi Yasak <alpernebiyasak@gmail.com>
Subject: [PATCH v2 0/4] rockchip: Improve support for Bob chromebook and add support for Kevin
Date: Tue, 14 Dec 2021 01:15:23 +0300	[thread overview]
Message-ID: <20211213221528.43102-1-alpernebiyasak@gmail.com> (raw)

I have recently started testing booting U-Boot from SPI on my gru-kevin
(as opposed to chainloading it from vendor coreboot + depthcharge) and
brought it to a better working state based on an initial support patch
from Marty [1][2] and some follow-up work by Simon [3].

I tried to keep them as the git author when I took things from their
work, but squashing other changes into those and rewriting commit
messages makes things a bit weird in my opinion, especially for keeping
their signoff. Do tell me if there is a better way to that.

As the Kevin and Bob boards are very similar, I assumed the config and
devicetree changes will be appropriate for Bob as well, and applied them
to it first. I do not have a Bob, so could not test on one myself, but
Simon did test an earlier version of this and it appears to work [4].

Other useful things for these boards:
- Patch to fix a hang when usb controllers exit [5] (or [6])
- Series to support HS400ES mode as HS400 training fails [7]
- Hack to skip eMMC reinitialization so it keeps working [8]

[1] https://patchwork.ozlabs.org/patch/1053386/
[2] https://patchwork.ozlabs.org/comment/2488899/
[3] https://github.com/sjg20/u-boot/commits/kevin
[4] https://patchwork.ozlabs.org/comment/2799106/
[5] https://patchwork.ozlabs.org/project/uboot/patch/20210406151059.1187379-1-icenowy@aosc.io/
[6] https://patchwork.ozlabs.org/project/uboot/patch/20211210200124.19226-1-alpernebiyasak@gmail.com/
[7] https://patchwork.ozlabs.org/project/uboot/list/?series=269768
[8] https://patchwork.ozlabs.org/comment/2779784/

Changes in v2:
- Drop unnecessary ifdef.
- Clarify commit message regarding 'values set in coreboot'.
- Rebase on u-boot/next, fixing conflict in board_debug_uart_init()

v1: https://patchwork.ozlabs.org/project/uboot/list/?series=273848

Alper Nebi Yasak (2):
  rockchip: gru: Set up SoC IO domain registers
  rockchip: bob: Enable more configs

Marty E. Plummer (1):
  rockchip: rk3399: Add support for chromebook_kevin

Simon Glass (1):
  rockchip: gru: Add more devicetree settings

 arch/arm/dts/Makefile                         |   1 +
 arch/arm/dts/rk3399-gru-kevin-u-boot.dtsi     |  11 ++
 arch/arm/dts/rk3399-gru-u-boot.dtsi           |  55 +++++++++
 arch/arm/mach-rockchip/rk3399/Kconfig         |  11 ++
 arch/arm/mach-rockchip/rk3399/rk3399.c        |   3 +-
 arch/arm/mach-rockchip/spl.c                  |   3 +-
 board/google/gru/Kconfig                      |  16 +++
 board/google/gru/MAINTAINERS                  |   8 ++
 board/google/gru/gru.c                        |  54 +++++++-
 configs/chromebook_bob_defconfig              |  27 +++-
 configs/chromebook_kevin_defconfig            | 116 ++++++++++++++++++
 doc/board/rockchip/rockchip.rst               |   1 +
 include/configs/gru.h                         |   3 +
 include/dt-bindings/input/linux-event-codes.h |   3 +-
 14 files changed, 307 insertions(+), 5 deletions(-)
 create mode 100644 arch/arm/dts/rk3399-gru-kevin-u-boot.dtsi
 create mode 100644 configs/chromebook_kevin_defconfig

-- 
2.34.1


             reply	other threads:[~2021-12-13 22:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-13 22:15 Alper Nebi Yasak [this message]
2021-12-13 22:15 ` [PATCH v2 1/4] rockchip: gru: Set up SoC IO domain registers Alper Nebi Yasak
2021-12-24  6:59   ` Kever Yang
2021-12-13 22:15 ` [PATCH v2 2/4] rockchip: gru: Add more devicetree settings Alper Nebi Yasak
2021-12-24  7:00   ` Kever Yang
2021-12-13 22:15 ` [PATCH v2 3/4] rockchip: bob: Enable more configs Alper Nebi Yasak
2021-12-24  7:00   ` Kever Yang
2021-12-13 22:15 ` [PATCH v2 4/4] rockchip: rk3399: Add support for chromebook_kevin Alper Nebi Yasak
2021-12-24  7:01   ` Kever Yang
2021-12-19 17:14 ` [PATCH v2 0/4] rockchip: Improve support for Bob chromebook and add support for Kevin Simon Glass
2021-12-20 15:09   ` Alper Nebi Yasak

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=20211213221528.43102-1-alpernebiyasak@gmail.com \
    --to=alpernebiyasak@gmail.com \
    --cc=alexandre.vicenzi@suse.com \
    --cc=andre.przywara@arm.com \
    --cc=christianshewitt@gmail.com \
    --cc=email2tema@gmail.com \
    --cc=festevam@denx.de \
    --cc=hanetzer@startmail.com \
    --cc=hs@denx.de \
    --cc=jagan@amarulasolutions.com \
    --cc=jbx6244@gmail.com \
    --cc=kever.yang@rock-chips.com \
    --cc=lokeshvutla@ti.com \
    --cc=narmstrong@baylibre.com \
    --cc=pbrobinson@gmail.com \
    --cc=philipp.tomsich@vrull.eu \
    --cc=sjg@chromium.org \
    --cc=tharvey@gateworks.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.