All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Morgan <macroalpha82@gmail.com>
To: u-boot@lists.denx.de
Cc: jonas@kwiboo.se, trini@konsulko.com, kever.yang@rock-chips.com,
	philipp.tomsich@vrull.eu, sjg@chromium.org,
	Chris Morgan <macromorgan@hotmail.com>
Subject: [PATCH 0/2 V2] RGXX3: Set boot order for mmc0 first
Date: Tue, 21 May 2024 10:45:47 -0500	[thread overview]
Message-ID: <20240521154549.255607-1-macroalpha82@gmail.com> (raw)

From: Chris Morgan <macromorgan@hotmail.com>

Set the rgxx3 device to boot from mmc0 first. This serves as a fallback
to allow us to recover from a bad U-Boot (or later) stage in a worst
case scenario. The code for an ADC button appears to have broke some
board revisions; this solution is much simpler and allows users to
continue to program the adc button as they see fit.

Changes from V1:
 - Removed sdmmc1, as long as we have sdmmc0 we should be safe.
 - Clarified that the expectation is that we can prevent a bad
   U-Boot stage with a valid FIT signature by looking at removable
   storage first.

Chris Morgan (2):
  Revert "board: rockchip: Add early ADC button detect for RGxx3"
  board: rockchip: rgxx3: Use sdmmc0 as first device

 .../arm/dts/rk3566-anbernic-rgxx3-u-boot.dtsi |  2 +-
 board/anbernic/rgxx3_rk3566/rgxx3-rk3566.c    | 64 -------------------
 2 files changed, 1 insertion(+), 65 deletions(-)

-- 
2.34.1


             reply	other threads:[~2024-05-21 15:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-21 15:45 Chris Morgan [this message]
2024-05-21 15:45 ` [PATCH 1/2 V2] Revert "board: rockchip: Add early ADC button detect for RGxx3" Chris Morgan
2024-05-23  3:46   ` Kever Yang
2024-05-23  3:47   ` Kever Yang
2024-05-23 20:53     ` Chris Morgan
2024-05-21 15:45 ` [PATCH 2/2 V2] board: rockchip: rgxx3: Use sdmmc0 as first device Chris Morgan
2024-05-23  3:46   ` Kever Yang

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=20240521154549.255607-1-macroalpha82@gmail.com \
    --to=macroalpha82@gmail.com \
    --cc=jonas@kwiboo.se \
    --cc=kever.yang@rock-chips.com \
    --cc=macromorgan@hotmail.com \
    --cc=philipp.tomsich@vrull.eu \
    --cc=sjg@chromium.org \
    --cc=trini@konsulko.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.