From: "Michał Barnaś" <barnas@google.com>
To: u-boot@lists.denx.de
Cc: "Michał Barnaś" <barnas@google.com>,
"Dinh Nguyen" <dinguyen@kernel.org>,
"Marcel Ziswiler" <marcel.ziswiler@toradex.com>,
"Marek Vasut" <marex@denx.de>,
"Martyn Welch" <martyn.welch@collabora.com>,
"Paweł Anikiel" <pan@semihalf.com>,
"Simon Glass" <sjg@chromium.org>,
"Simon Goldschmidt" <simon.k.r.goldschmidt@gmail.com>,
"Svyatoslav Ryhel" <clamor95@gmail.com>,
"Tien Fong Chee" <tien.fong.chee@intel.com>,
"Tom Rini" <trini@konsulko.com>
Subject: [PATCH v3 0/2] arm: socfpga: arria10: allow to reprogram FPGA with warm reboot
Date: Tue, 19 Mar 2024 18:18:12 +0000 [thread overview]
Message-ID: <20240319181949.3083508-1-barnas@google.com> (raw)
In-Reply-To: <c0cbfa06-9206-4ca6-ad51-ad7b0e54cf1c@denx.de>
By default, the board requires power cycle (cold boot) to program the
FPGA with bitstream. This change adds Kconfig that allows to enable
reprogramming the FPGA with every boot. This makes the update process
of the bitstream on the filesystem to be applied with simple system
reboot.
Changes in v3:
- Rebase on current master branch
- Drop the TARGET_ prefix in Kconfig
- Remove #ifdefs and use IS_ENABLED
- Update defconfig to use renamed Kconfig
Changes in v2:
- Rebase on current master branch
Michał Barnaś (2):
arm: socfpga: arria10: add option to reprogram the FPGA every reboot
chameleonv3: set in defconfig for FPGA to reprogram every reboot
arch/arm/mach-socfpga/Kconfig | 8 ++++++++
arch/arm/mach-socfpga/spl_a10.c | 8 ++++++--
configs/socfpga_chameleonv3_defconfig | 1 +
3 files changed, 15 insertions(+), 2 deletions(-)
--
2.44.0.291.gc1ea87d7ee-goog
next prev parent reply other threads:[~2024-03-19 18:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-22 15:20 [PATCH 0/2] arm: socfpga: arria10: allow to reprogram FPGA with warm reboot Michał Barnaś
2024-02-22 15:20 ` [PATCH 1/2] arm: socfpga: arria10: add option to reprogram the FPGA every reboot Michał Barnaś
2024-03-01 8:14 ` Chee, Tien Fong
2024-03-03 16:22 ` Dinh Nguyen
2024-03-08 17:12 ` [PATCH v2 0/2] arm: socfpga: arria10: allow to reprogram FPGA with warm reboot Michał Barnaś
2024-03-08 17:12 ` [PATCH v2 1/2] arm: socfpga: arria10: add option to reprogram the FPGA every reboot Michał Barnaś
2024-03-08 18:46 ` Marek Vasut
2024-03-19 18:18 ` Michał Barnaś [this message]
2024-03-19 18:18 ` [PATCH v3 " Michał Barnaś
2024-03-28 6:38 ` Chee, Tien Fong
2024-03-19 18:18 ` [PATCH v3 2/2] chameleonv3: set in defconfig for FPGA to reprogram " Michał Barnaś
2024-03-28 8:00 ` [PATCH v3 2/2] chameleonv3: set in defconfig for FPGA to reprogramevery reboot Chee, Tien Fong
2024-03-19 18:22 ` [PATCH v2 1/2] arm: socfpga: arria10: add option to reprogram the FPGA every reboot Michał Barnaś
2024-03-08 17:12 ` [PATCH v2 2/2] chameleonv3: set in defconfig for FPGA to reprogram " Michał Barnaś
2024-02-22 15:20 ` [PATCH " Michał Barnaś
2024-02-29 13:03 ` [PATCH 0/2] arm: socfpga: arria10: allow to reprogram FPGA with warm reboot Dinh Nguyen
2024-02-29 13:49 ` Michał Barnaś
2024-03-01 8:13 ` Chee, Tien Fong
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=20240319181949.3083508-1-barnas@google.com \
--to=barnas@google.com \
--cc=clamor95@gmail.com \
--cc=dinguyen@kernel.org \
--cc=marcel.ziswiler@toradex.com \
--cc=marex@denx.de \
--cc=martyn.welch@collabora.com \
--cc=pan@semihalf.com \
--cc=simon.k.r.goldschmidt@gmail.com \
--cc=sjg@chromium.org \
--cc=tien.fong.chee@intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox