linux-fpga.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Moritz Fischer <mdf@kernel.org>
To: gregkh@linuxfoundation.org
Cc: linux-fpga@vger.kernel.org, moritzf@google.com
Subject: [GIT PULL] FPGA Manager changes for 5.10
Date: Sun, 13 Sep 2020 15:55:26 -0700	[thread overview]
Message-ID: <20200913225526.GA52103@epycbox.lan> (raw)

The following changes since commit 9123e3a74ec7b934a4a099e98af6a61c2f80bbf5:

  Linux 5.9-rc1 (2020-08-16 13:04:57 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/mdf/linux-fpga.git tags/fpga-for-5.10

for you to fetch changes up to 9ba3a0aa09fe505540a3bdd11f0da3b8e9d73055:

  fpga: dfl: create a dfl bus type to support DFL devices (2020-09-09 20:28:16 -0700)

----------------------------------------------------------------
Here is the first set of changes for the 5.10-rc1 merge window.

Xilinx:
- Luca's changes clean up the xilinx-spi driver and add better
  diagnostics on errors.

Core:
- I cleaned up a stray comment.
- Richard's change marks FPGA manager tasks un-interruptible.
- Tom has agreed to help out as Reviewer in the FPGA Manager subsystem.

DFL:
- Xu's changes  add a new bus that is the first part of a series to support
  adding devices via DFL (the other parts are still under review)

All patches have been reviewed on the mailing list, and have been in the
last few linux-next releases (as part of my for-next branch) without issues.

Signed-off-by: Moritz Fischer <mdf@kernel.org>

----------------------------------------------------------------
Luca Ceresoli (5):
      fpga manager: xilinx-spi: remove stray comment
      fpga manager: xilinx-spi: remove final dot from dev_err() strings
      fpga manager: xilinx-spi: fix write_complete timeout handling
      fpga manager: xilinx-spi: add error checking after gpiod_get_value()
      fpga manager: xilinx-spi: provide better diagnostics on programming failure

Moritz Fischer (1):
      fpga: fpga-region: Cleanup an outdated comment

Richard Gong (1):
      fpga: stratix10-soc: make FPGA task un-interruptible

Tom Rix (1):
      MAINTAINERS: Add Tom Rix as fpga reviewer

Xu Yilun (3):
      fpga: dfl: change data type of feature id to u16
      fpga: dfl: map feature mmio resources in their own feature drivers
      fpga: dfl: create a dfl bus type to support DFL devices

 Documentation/ABI/testing/sysfs-bus-dfl |  15 +
 MAINTAINERS                             |   3 +
 drivers/fpga/dfl-fme-perf.c             |   2 +-
 drivers/fpga/dfl-pci.c                  |  24 +-
 drivers/fpga/dfl.c                      | 477 ++++++++++++++++++++++++++------
 drivers/fpga/dfl.h                      | 103 ++++++-
 drivers/fpga/fpga-region.c              |   2 +-
 drivers/fpga/stratix10-soc.c            |  23 +-
 drivers/fpga/xilinx-spi.c               |  77 ++++--
 9 files changed, 583 insertions(+), 143 deletions(-)
 create mode 100644 Documentation/ABI/testing/sysfs-bus-dfl

             reply	other threads:[~2020-09-13 22:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-13 22:55 Moritz Fischer [this message]
2020-09-14  8:28 ` [GIT PULL] FPGA Manager changes for 5.10 Greg KH

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=20200913225526.GA52103@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;
as well as URLs for NNTP newsgroup(s).