linux-kernel - [PATCH v4 0/6] FPGA Manager Framework

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 9 Dec 2014 14:14:44 -0600
From:	<atull@...nsource.altera.com>
To:	<gregkh@...uxfoundation.org>, <jgunthorpe@...idianresearch.com>,
	<hpa@...or.com>, <monstr@...str.eu>, <michal.simek@...inx.com>,
	<rdunlap@...radead.org>
CC:	<linux-kernel@...r.kernel.org>, <devicetree@...r.kernel.org>,
	<pantelis.antoniou@...sulko.com>, <robh+dt@...nel.org>,
	<grant.likely@...aro.org>, <iws@...o.caltech.edu>,
	<linux-doc@...r.kernel.org>, <pavel@...x.de>, <broonie@...nel.org>,
	<philip@...ister.org>, <rubini@...dd.com>,
	<s.trumtrar@...gutronix.de>, <jason@...edaemon.net>,
	<kyle.teske@...com>, <nico@...aro.org>, <balbi@...com>,
	<m.chehab@...sung.com>, <davidb@...eaurora.org>, <rob@...dley.net>,
	<davem@...emloft.net>, <cesarb@...arb.net>,
	<sameo@...ux.intel.com>, <akpm@...ux-foundation.org>,
	<linus.walleij@...aro.org>, <pawel.moll@....com>,
	<mark.rutland@....com>, <ijc+devicetree@...lion.org.uk>,
	<galak@...eaurora.org>, <delicious.quinoa@...il.com>,
	<dinguyen@...nsource.altera.com>, <yvanderv@...nsource.altera.com>,
	Alan Tull <atull@...nsource.altera.com>
Subject: [PATCH v4 0/6] FPGA Manager Framework

From: Alan Tull <atull@...nsource.altera.com>

Improvements in this v3 and v4:

I've moved the driver to drivers/staging.

I'm including the altera low level driver, defconfig changes, and
DTS changes - everything to make it work on socfpga platform.

Fixed things in the framework that were left over from my original
version (that Michal started with) that was a character driver.
In particular, make the device be present in the fpga_manager struct,
not as a pointer, so container_of will work.

Since not enough of the Device Tree Overlays code is in the main
kernel yet, I'm leaving out the (small) changes to make this accept
notifications when a device tree overlay is accepted.  That can
wait a little until enough of is in that it can build and work.
That is a little disappointing to leave it out for now because
it was very cool and, I think, more Linux-like than this is by
itself.

Alan Tull (6):
  doc: add bindings document for altera fpga manager
  arm: dts: socfpga: add altera fpga manager
  ARM: socfpga: defconfig: enable fpga manager
  fpga manager: add sysfs interface document
  staging: fpga manager: framework core
  staging: fpga manager: add driver for altera socfpga manager

 Documentation/ABI/testing/sysfs-class-fpga-manager |   38 +
 .../devicetree/bindings/fpga/altera-fpga-mgr.txt   |   17 +
 arch/arm/boot/dts/socfpga.dtsi                     |   10 +
 arch/arm/configs/socfpga_defconfig                 |    4 +
 drivers/staging/Kconfig                            |    2 +
 drivers/staging/Makefile                           |    1 +
 drivers/staging/fpga/Kconfig                       |   27 +
 drivers/staging/fpga/Makefile                      |   11 +
 drivers/staging/fpga/altera.c                      |  789 ++++++++++++++++++++
 drivers/staging/fpga/fpga-mgr.c                    |  485 ++++++++++++
 include/linux/fpga-mgr.h                           |  104 +++
 11 files changed, 1488 insertions(+)
 create mode 100644 Documentation/ABI/testing/sysfs-class-fpga-manager
 create mode 100644 Documentation/devicetree/bindings/fpga/altera-fpga-mgr.txt
 create mode 100644 drivers/staging/fpga/Kconfig
 create mode 100644 drivers/staging/fpga/Makefile
 create mode 100644 drivers/staging/fpga/altera.c
 create mode 100644 drivers/staging/fpga/fpga-mgr.c
 create mode 100644 include/linux/fpga-mgr.h

-- 
1.7.9.5

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/