From: Richard Gong <richard.gong@linux.intel.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RESEND PATCHv1 0/5] support remote system update on Intel Stratix10 SoC
Date: Mon, 28 Oct 2019 11:00:46 -0500 [thread overview]
Message-ID: <cdfeca8d-00c3-90ae-83da-4dcc58de8909@linux.intel.com> (raw)
In-Reply-To: <CAAh8qswQPKUJ9zb+YopOR6By8S6s+PiV4ZjsA2+FH-HfxcXp2Q@mail.gmail.com>
Hi Simon,
On 10/28/19 9:05 AM, Simon Goldschmidt wrote:
>
>
> Richard Gong <richard.gong@linux.intel.com
> <mailto:richard.gong@linux.intel.com>> schrieb am Mo., 28. Okt. 2019, 14:58:
>
> Hi Simon,
>
> Thanks for your comment.
>
> I will move files to driver/firmware.
>
>
> Would moving to uclass mailbox fit for these kind of things?
>
Don't fit, since they are not mailbox like.
The Intel Remote System Update (RSU) provides a way for user to update
the QSPI configuration bitsterams on Intel Stratix10/Agilex SoC device
with significantly reduced risk of corrupting the bitstream storage and
bricking the system.
RSU allows suer to perform a complete set of operations:
1. provides support for creating the initial flash images for a system
to support RSU.
2. allows several production image to be tried in a specific order until
one of them is successful.
3. loads a factory image if no production image is available, or all
production image failed.
4. provides user with the ability to add or remove production images.
5. provides user with the ability to change the order in which
production images are loaded.
6. provides user with the ability to load a specific image from flash,
The image is a production or factory image.
7. provides user the information on which image is currently running,
and what errors were encountered if have.
Regards,
Richard
> Regards,
> Simon
>
>
> Regards,
> Richard
>
> On 10/24/19 10:00 AM, Simon Goldschmidt wrote:
> > On Thu, Oct 24, 2019 at 4:35 PM <richard.gong@linux.intel.com
> <mailto:richard.gong@linux.intel.com>> wrote:
> >>
> >> From: Richard Gong <richard.gong@intel.com
> <mailto:richard.gong@intel.com>>
> >>
> >> The Intel Remote System Update (RSU) provides a way for users to
> update
> >> the QSPI configuration bitstream of a Intel Stratix10 SoC device
> with
> >> significantly reduced risk of corrupting the bitstream storage and
> >> bricking the system.
> >>
> >> The patchset adds RSU support which allows user to perform a
> complete set
> >> of RSU operations via provided console commands.
> >>
> >> The patches have reviewed by other colleagues at Intel.
> >>
> >> Richard Gong (5):
> >> arm: socfpga: stratix10: add RSU mailbox support
> >> arm: socfpga: stratix10: add RSU support for Stratix10 SoC
> >> arm: socfpga: stratix10: add environment variables for RSU
> support
> >> arm: socfpga: stratix10: add console commands for RSU support
> >> arm: socfpga: enable RSU build
> >>
> >> arch/arm/mach-socfpga/Makefile | 6 +
> >> arch/arm/mach-socfpga/include/mach/mailbox_s10.h | 36 +-
> >> arch/arm/mach-socfpga/include/mach/rsu.h | 244 +++++
> >> arch/arm/mach-socfpga/include/mach/rsu_ll.h | 71 ++
> >> arch/arm/mach-socfpga/include/mach/rsu_misc.h | 46 +
> >> arch/arm/mach-socfpga/include/mach/rsu_s10.h | 46 +
> >> arch/arm/mach-socfpga/mailbox_s10.c | 45 +
> >> arch/arm/mach-socfpga/misc_s10.c | 9 +
> >> arch/arm/mach-socfpga/rsu.c | 569
> ++++++++++++
> >> arch/arm/mach-socfpga/rsu_ll_qspi.c | 1033
> ++++++++++++++++++++++
> >> arch/arm/mach-socfpga/rsu_misc.c | 527
> +++++++++++
> >> arch/arm/mach-socfpga/rsu_s10.c | 817
> +++++++++++++++++
> >> 12 files changed, 3439 insertions(+), 10 deletions(-)
> >> create mode 100644 arch/arm/mach-socfpga/include/mach/rsu.h
> >> create mode 100644 arch/arm/mach-socfpga/include/mach/rsu_ll.h
> >> create mode 100644 arch/arm/mach-socfpga/include/mach/rsu_misc.h
> >> create mode 100644 arch/arm/mach-socfpga/include/mach/rsu_s10.h
> >> create mode 100644 arch/arm/mach-socfpga/rsu.c
> >> create mode 100644 arch/arm/mach-socfpga/rsu_ll_qspi.c
> >> create mode 100644 arch/arm/mach-socfpga/rsu_misc.c
> >> create mode 100644 arch/arm/mach-socfpga/rsu_s10.c
> >
> > We're trying to move files from arch/arm/mach-socfpga to drivers.
> > This goes in the opposite direction.
> >
> > Regards,
> > Simon
> >
> >>
> >> --
> >> 2.7.4
> >>
>
prev parent reply other threads:[~2019-10-28 16:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-24 14:48 [U-Boot] [RESEND PATCHv1 0/5] support remote system update on Intel Stratix10 SoC richard.gong at linux.intel.com
2019-10-24 14:48 ` [U-Boot] [RESEND PATCHv1 1/5] arm: socfpga: stratix10: add RSU mailbox support richard.gong at linux.intel.com
2019-10-24 14:48 ` [U-Boot] [RESEND PATCHv1 2/5] arm: socfpga: stratix10: add RSU support for Stratix10 SoC richard.gong at linux.intel.com
2019-10-24 14:48 ` [U-Boot] [RESEND PATCHv1 3/5] arm: socfpga: stratix10: add environment variables for RSU support richard.gong at linux.intel.com
2019-10-24 14:48 ` [U-Boot] [RESEND PATCHv1 4/5] arm: socfpga: stratix10: add console commands " richard.gong at linux.intel.com
2019-10-24 14:48 ` [U-Boot] [RESEND PATCHv1 5/5] arm: socfpga: enable RSU build richard.gong at linux.intel.com
2019-10-24 15:00 ` [U-Boot] [RESEND PATCHv1 0/5] support remote system update on Intel Stratix10 SoC Simon Goldschmidt
2019-10-28 14:12 ` Richard Gong
2019-10-28 14:05 ` Simon Goldschmidt
2019-10-28 16:00 ` Richard Gong [this message]
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=cdfeca8d-00c3-90ae-83da-4dcc58de8909@linux.intel.com \
--to=richard.gong@linux.intel.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