All of lore.kernel.org
 help / color / mirror / Atom feed
From: Moritz Fischer <mdf@kernel.org>
To: gregkh@linux-foundation.org
Cc: linux-fpga.vger@kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, atull@kernel.org,
	robh+dt@kernel.org, Moritz Fischer <mdf@kernel.org>
Subject: [PATCH 0/3] FPGA Manager Patches for 4.18
Date: Mon, 16 Apr 2018 20:43:34 -0700	[thread overview]
Message-ID: <20180417034337.8855-1-mdf@kernel.org> (raw)

Hi Greg,

Please queue the following patches for v4.18.

Alan's Patch clarifies the locking in the fpga-region code.

Paolo's patches add a new driver with corresponding bindings for a
Lattice FPGA part.

Thanks,

Moritz

Alan Tull (1):
  fpga: fpga-region: comment on fpga_region_program_fpga locking

Paolo Pisati (2):
  dt: bindings: fpga: add lattice machxo2 slave spi binding description
  fpga: lattice machxo2: Add Lattice MachXO2 support

 .../bindings/fpga/lattice-machxo2-spi.txt     |  29 ++
 drivers/fpga/Kconfig                          |   7 +
 drivers/fpga/Makefile                         |   1 +
 drivers/fpga/fpga-region.c                    |   5 +
 drivers/fpga/machxo2-spi.c                    | 403 ++++++++++++++++++
 5 files changed, 445 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/fpga/lattice-machxo2-spi.txt
 create mode 100644 drivers/fpga/machxo2-spi.c

-- 
2.17.0

             reply	other threads:[~2018-04-17  3:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-17  3:43 Moritz Fischer [this message]
2018-04-17  3:43 ` [PATCH 1/3] dt: bindings: fpga: add lattice machxo2 slave spi binding description Moritz Fischer
2018-04-17  3:43 ` [PATCH 2/3] fpga: lattice machxo2: Add Lattice MachXO2 support Moritz Fischer
2018-04-17  3:43 ` [PATCH 3/3] fpga: fpga-region: comment on fpga_region_program_fpga locking Moritz Fischer
  -- strict thread matches above, loose matches on Subject: below --
2018-04-17  4:17 [PATCH 0/3] FPGA Manager Patches for 4.18 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=20180417034337.8855-1-mdf@kernel.org \
    --to=mdf@kernel.org \
    --cc=atull@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linux-foundation.org \
    --cc=linux-fpga.vger@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.