From: Moritz Fischer <mdf@kernel.org>
To: gregkh@linuxfoundation.org
Cc: moritzf@google.com, linux-fpga@vger.kernel.org
Subject: [GIT PULL] FPGA Manager changes for 5.7
Date: Fri, 27 Mar 2020 09:30:01 -0700 [thread overview]
Message-ID: <20200327162944.GA4118@epycbox.lan> (raw)
The following changes since commit bb6d3fb354c5ee8d6bde2d576eb7220ea09862b9:
Linux 5.6-rc1 (2020-02-09 16:08:48 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mdf/linux-fpga.git/ tags/fpga-for-5.7
for you to fetch changes up to 3d5a5417ad064a6ca64a33f0c554d917311c79f4:
fpga: dfl: afu: support debug access to memory-mapped afu regions (2020-03-21 13:14:30 -0700)
----------------------------------------------------------------
FPGA Manager changes for 5.7
Here's the first set of changes for the 5.7-rc1 merge window.
Dominic's change adds support for accessing AFU regions with gdb.
Gustavo's change is a cleanup patch regarding variable lenght arrays.
Richard's changes update dt-bindings and add support for stratix and agilex.
Sergiu's changes update spi transfers with the new delay field.
Xu's change addresses an issue with a wrong return value.
Shubhrajyoti's change makes the Zynq FPGA driver return -EPROBE_DEFER on
check of devm_clk_get failure.
Xu's change for DFL enables multiple opens.
All of these patches have been reviewed, have appropriate Acked-by's and
have been in the last few linux-next releases without issues.
Signed-off-by: Moritz Fischer <mdf@kernel.org>
----------------------------------------------------------------
Dominic Chen (1):
fpga: dfl: afu: support debug access to memory-mapped afu regions
Gustavo A. R. Silva (1):
fpga: dfl.h: Replace zero-length array with flexible-array member
Richard Gong (5):
dt-bindings: fpga: add compatible value to Stratix10 SoC FPGA manager binding
arm64: dts: agilex: correct FPGA manager driver's compatible value
fpga: stratix10-soc: add compatible property value for intel agilex
dt-bindings, firmware: add compatible value Intel Stratix10 service layer binding
arm64: dts: agilex: correct service layer driver's compatible value
Sergiu Cuciurean (2):
fpga: ice40-spi: Use new structure for SPI transfer delays
fpga: machxo2-spi: Use new structure for SPI transfer delays
Shubhrajyoti Datta (1):
fpga: zynq: Remove clk_get error message for probe defer
Xu Yilun (2):
fpga: dfl: support multiple opens on feature device node.
fpga: dfl: pci: fix return value of cci_pci_sriov_configure
.../bindings/firmware/intel,stratix10-svc.txt | 2 +-
.../bindings/fpga/intel-stratix10-soc-fpga-mgr.txt | 3 +-
arch/arm64/boot/dts/intel/socfpga_agilex.dtsi | 4 +--
drivers/fpga/dfl-afu-main.c | 35 +++++++++++++-------
drivers/fpga/dfl-fme-main.c | 19 +++++++----
drivers/fpga/dfl-pci.c | 6 ++--
drivers/fpga/dfl.c | 15 +++++++--
drivers/fpga/dfl.h | 37 ++++++++++++++++------
drivers/fpga/ice40-spi.c | 10 ++++--
drivers/fpga/machxo2-spi.c | 12 ++++---
drivers/fpga/stratix10-soc.c | 3 +-
drivers/fpga/zynq-fpga.c | 3 +-
12 files changed, 106 insertions(+), 43 deletions(-)
next reply other threads:[~2020-03-27 16:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-27 16:30 Moritz Fischer [this message]
2020-03-30 14:15 ` [GIT PULL] FPGA Manager changes for 5.7 Greg KH
2020-03-31 1:28 ` Moritz Fischer
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=20200327162944.GA4118@epycbox.lan \
--to=mdf@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fpga@vger.kernel.org \
--cc=moritzf@google.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