[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1FF23F53-E94E-44F1-A198-BD49ACB2DCA7@konsulko.com>
Date: Tue, 5 Aug 2014 21:18:46 +0300
From: Pantelis Antoniou <pantelis.antoniou@...sulko.com>
To: <atull@...nsource.altera.com>
Cc: <gregkh@...uxfoundation.org>, <jgunthorpe@...idianresearch.com>,
<hpa@...or.com>, <monstr@...str.eu>, <michal.simek@...inx.com>,
<linux-kernel@...r.kernel.org>, <devicetree@...r.kernel.org>,
<robh+dt@...nel.org>, <grant.likely@...aro.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>, <delicious.quinoa@...il.com>,
<dinguyen@...nsource.altera.com>, <yvanderv@...nsource.altera.com>
Subject: Re: [PATCH 0/3] Yet another stab at a fpga framework
Hi Alan,
On Aug 2, 2014, at 1:28 AM, <atull@...nsource.altera.com> wrote:
> From: Alan Tull <atull@...nsource.altera.com>
>
> [resend with fixed email settings]
>
> The idea of the framework is to provide consistent ways of
> programming raw images into FPGA's.
>
> Programming from device tree overlays is supported.
>
> The core (fpga-mgr.c) does not include a userspace interface
> and just exports kernel functions.
>
> This approach separates the core from the interfaces.
>
> Each interface can be enabled or disabled in the defconfig.
> In some production contexts, interfaces that might be used
> during development can be disabled.
>
> The core exports kernel functions to:
> * write the fpga from a buffer or using the firmware layer
> * get fpga status
> * find a particular fpga manager from a device tree phandle
> * register/unregister lower level fpga drivers.
>
> The bus allows us to:
> * program fpga from a device tree overlay using firmware.
> * automatically reload firmware and reprogram fpga during resume.
>
> The sysfs interface:
> * read only, get the name and status of fpga manager.
>
> I have a configfs interface patch which I haven't included,
> adds configfs as a separate file.
>
> TODO:
> * Enable bridges after fpga programming, disable during suspend
>
> Alan Tull (3):
> fpga manager framework core
> fpga bus driver
> fpga sysfs interface
>
> drivers/Kconfig | 2 +
> drivers/Makefile | 1 +
> drivers/fpga/Kconfig | 27 +++
> drivers/fpga/Makefile | 12 ++
> drivers/fpga/bus.c | 145 ++++++++++++++++
> drivers/fpga/fpga-mgr.c | 431 ++++++++++++++++++++++++++++++++++++++++++++++
> drivers/fpga/sysfs.c | 69 ++++++++
> include/linux/fpga-mgr.h | 137 +++++++++++++++
> 8 files changed, 824 insertions(+)
> create mode 100644 drivers/fpga/Kconfig
> create mode 100644 drivers/fpga/Makefile
> create mode 100644 drivers/fpga/bus.c
> create mode 100644 drivers/fpga/fpga-mgr.c
> create mode 100644 drivers/fpga/sysfs.c
> create mode 100644 include/linux/fpga-mgr.h
>
Looks very sane and useful. Please let me know if you come across any problems
with the overlays code, especially the removal path.
Regards
-- Pantelis
--
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/
Powered by blists - more mailing lists