On Thu, 23 Oct 2014, atull@xxxxxxxxxxxxxxxxxxxxx wrote: > From: Alan Tull <atull@xxxxxxxxxxxxxxxxxxxxx> > > Followup to bridge framework that was posted on 2013/10/3 > > This is a driver for enabling/disabling the fpga bridges under control > of a sys entry. It has a common framework and individual drivers for > the various bridges. > > This framework uses the reset driver where appropriate. > > Alan > Forgot to mention: This patchset needs Dinh Nguyen's "reset: add reset_control_status helper function" patches https://lkml.org/lkml/2014/10/10/256 Alan > > Alan Tull (3): > add sysfs document for fpga bridges > ARM: dts: socfpga: fpga bridges bindings docs > fpga bridge driver > > Documentation/ABI/testing/sysfs-class-fpga-bridge | 5 + > .../bindings/fpga/altera-fpga2sdram-bridge.txt | 57 +++++ > .../bindings/fpga/altera-hps2fpga-bridge.txt | 53 +++++ > drivers/misc/Kconfig | 3 +- > drivers/misc/Makefile | 1 + > drivers/misc/fpga-bridge/Kconfig | 20 ++ > drivers/misc/fpga-bridge/Makefile | 6 + > drivers/misc/fpga-bridge/altera-fpga2sdram.c | 236 ++++++++++++++++++++ > drivers/misc/fpga-bridge/altera-hps2fpga.c | 220 ++++++++++++++++++ > drivers/misc/fpga-bridge/fpga-bridge.c | 230 +++++++++++++++++++ > drivers/misc/fpga-bridge/fpga-bridge.h | 51 +++++ > 11 files changed, 881 insertions(+), 1 deletion(-) > create mode 100644 Documentation/ABI/testing/sysfs-class-fpga-bridge > create mode 100644 Documentation/devicetree/bindings/fpga/altera-fpga2sdram-bridge.txt > create mode 100644 Documentation/devicetree/bindings/fpga/altera-hps2fpga-bridge.txt > create mode 100644 drivers/misc/fpga-bridge/Kconfig > create mode 100644 drivers/misc/fpga-bridge/Makefile > create mode 100644 drivers/misc/fpga-bridge/altera-fpga2sdram.c > create mode 100644 drivers/misc/fpga-bridge/altera-hps2fpga.c > create mode 100644 drivers/misc/fpga-bridge/fpga-bridge.c > create mode 100644 drivers/misc/fpga-bridge/fpga-bridge.h > > -- > 1.7.9.5 > > -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
