From: Jesse Taube <mr.bossman075@gmail.com>
To: u-boot@lists.denx.de
Cc: jagan@amarulasolutions.com, andre.przywara@arm.com,
hdegoede@redhat.com, sjg@chromium.org, icenowy@aosc.io,
marek.behun@nic.cz, festevam@denx.de, narmstrong@baylibre.com,
tharvey@gateworks.com, christianshewitt@gmail.com,
pbrobinson@gmail.com, jernej.skrabec@gmail.com, hs@denx.de,
samuel@sholland.org, arnaud.ferraris@gmail.com,
giulio.benetti@benettiengineering.com, Mr.Bossman075@gmail.com,
thirtythreeforty@gmail.com
Subject: [PATCH v2 0/3] Add SPI boot to SPL on SUNIV/F1C100s
Date: Fri, 11 Feb 2022 19:32:32 -0500 [thread overview]
Message-ID: <20220212003235.2162334-1-Mr.Bossman075@gmail.com> (raw)
This patch adds the ability to detect the BROM's boot source,
as well as the ability to boot from SPI.
Jesse Taube (3):
mach-sunxi: Add boot device detection for SUNIV/F1C100s
mach-sunxi: Add SPL SPI boot for SUNIV
mach-sunxi: Enable SPI boot for SUNIV and licheepi nano
arch/arm/include/asm/arch-sunxi/gpio.h | 1 +
arch/arm/include/asm/arch-sunxi/spl.h | 10 +++++
arch/arm/mach-sunxi/Kconfig | 2 +-
arch/arm/mach-sunxi/board.c | 57 +++++++++++++-------------
arch/arm/mach-sunxi/spl_spi_sunxi.c | 24 +++++++----
configs/licheepi_nano_defconfig | 1 +
6 files changed, 58 insertions(+), 37 deletions(-)
--
2.34.1
next reply other threads:[~2022-02-12 0:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-12 0:32 Jesse Taube [this message]
2022-02-12 0:32 ` [PATCH v2 1/3] mach-sunxi: Add boot device detection for SUNIV/F1C100s Jesse Taube
2022-02-12 0:36 ` Jesse Taube
2022-02-12 0:32 ` [PATCH v2 2/3] mach-sunxi: Add SPL SPI boot for SUNIV Jesse Taube
2022-02-12 0:32 ` [PATCH v2 3/3] mach-sunxi: Enable SPI boot for SUNIV and licheepi nano Jesse Taube
2022-03-01 4:42 ` [PATCH v2 0/3] Add SPI boot to SPL on SUNIV/F1C100s Jesse Taube
2022-03-01 13:39 ` Andre Przywara
2022-03-03 1:53 ` Andre Przywara
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=20220212003235.2162334-1-Mr.Bossman075@gmail.com \
--to=mr.bossman075@gmail.com \
--cc=andre.przywara@arm.com \
--cc=arnaud.ferraris@gmail.com \
--cc=christianshewitt@gmail.com \
--cc=festevam@denx.de \
--cc=giulio.benetti@benettiengineering.com \
--cc=hdegoede@redhat.com \
--cc=hs@denx.de \
--cc=icenowy@aosc.io \
--cc=jagan@amarulasolutions.com \
--cc=jernej.skrabec@gmail.com \
--cc=marek.behun@nic.cz \
--cc=narmstrong@baylibre.com \
--cc=pbrobinson@gmail.com \
--cc=samuel@sholland.org \
--cc=sjg@chromium.org \
--cc=tharvey@gateworks.com \
--cc=thirtythreeforty@gmail.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