linux-fpga.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: trix@redhat.com
To: russell.h.weight@intel.com, mdf@kernel.org, hao.wu@intel.com,
	michal.simek@xilinx.com
Cc: linux-fpga@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, Tom Rix <trix@redhat.com>
Subject: [PATCH v2 0/5] generalize fpga_mgr_load
Date: Thu, 20 May 2021 11:29:06 -0700	[thread overview]
Message-ID: <20210520182906.2021594-1-trix@redhat.com> (raw)

From: Tom Rix <trix@redhat.com>

A refactor of the fpga-manager to make space for the
functionality of the secure update in this thread.
https://lore.kernel.org/linux-fpga/20210517023200.52707-1-mdf@kernel.org/T/#mf3a1951d429a973c863eee079ed990c55056827c

Splits the reconfig write ops into its own ops structure and
then has an instance for the existing loading (reconfig) and the
secure update (reimage)

fpga_mgr_load uses a new bit, FPGA_MGR_REIMAGE, in fpga_info_info
to use either the reconfig or the reimage ops.

valid write op checking has moved to make the reimage path option.

Since fpga_image_info_alloc zalloc's the fpga_info_struct, the
reimage path will not be taken.

Changes since v1:
- update op names changed from
  partial_update to reconfig
  full_update to reimage
- dropped the cancel() and get_error() ops.
- add FPGA_MGR_REIMAGE bit
- refactor fpga_mgr_load to use either update ops

Tom Rix (5):
  fpga: generalize updating the card
  fpga: add FPGA_MGR_REIMAGE flag
  fpga: pass fpga_manager_update_ops to the fpga_manager_write functions
  fpga: defer checking for update ops until they are used
  fpga: use reimage ops in fpga_mgr_load()

 drivers/fpga/altera-cvp.c        |  8 ++--
 drivers/fpga/altera-pr-ip-core.c |  8 ++--
 drivers/fpga/altera-ps-spi.c     |  8 ++--
 drivers/fpga/dfl-fme-mgr.c       | 10 ++---
 drivers/fpga/fpga-mgr.c          | 72 ++++++++++++++++++++------------
 drivers/fpga/ice40-spi.c         |  8 ++--
 drivers/fpga/machxo2-spi.c       |  8 ++--
 drivers/fpga/socfpga-a10.c       | 10 ++---
 drivers/fpga/socfpga.c           |  8 ++--
 drivers/fpga/stratix10-soc.c     |  8 ++--
 drivers/fpga/ts73xx-fpga.c       |  8 ++--
 drivers/fpga/xilinx-spi.c        |  8 ++--
 drivers/fpga/zynq-fpga.c         | 10 ++---
 drivers/fpga/zynqmp-fpga.c       |  8 ++--
 include/linux/fpga/fpga-mgr.h    | 35 +++++++++++-----
 15 files changed, 125 insertions(+), 92 deletions(-)

--
2.26.3


                 reply	other threads:[~2021-05-20 18:29 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20210520182906.2021594-1-trix@redhat.com \
    --to=trix@redhat.com \
    --cc=hao.wu@intel.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-fpga@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mdf@kernel.org \
    --cc=michal.simek@xilinx.com \
    --cc=russell.h.weight@intel.com \
    /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;
as well as URLs for NNTP newsgroup(s).