linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michal Simek <monstr@monstr.eu>
To: Dinh Nguyen <dinguyen@altera.com>
Cc: Michal Simek <michal.simek@xilinx.com>,
	linux-kernel@vger.kernel.org, Alan Tull <atull@altera.com>,
	Pavel Machek <pavel@ucw.cz>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Philip Balister <philip@balister.org>,
	Alessandro Rubini <rubini@gnudd.com>,
	Mauro Carvalho Chehab <m.chehab@samsung.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Cesar Eduardo Barros <cesarb@cesarb.net>,
	Joe Perches <joe@perches.com>,
	"David S. Miller" <davem@davemloft.net>,
	Stephen Warren <swarren@nvidia.com>,
	Arnd Bergmann <arnd@arndb.de>,
	David Brown <davidb@codeaurora.org>,
	Dom Cobley <popcornmix@gmail.com>,
	delicious.quinoa@gmail.com, rocket.yvanderv@gmail.com
Subject: Re: [RFC PATCH] fpga: Introduce new fpga subsystem
Date: Thu, 19 Sep 2013 13:53:48 +0200	[thread overview]
Message-ID: <523AE5CC.4000909@monstr.eu> (raw)
In-Reply-To: <1379530957.23877.11.camel@linux-builds1>

[-- Attachment #1: Type: text/plain, Size: 4247 bytes --]

On 09/18/2013 09:02 PM, Dinh Nguyen wrote:
> Hi Michal,
> 
> On Wed, 2013-09-18 at 17:56 +0200, Michal Simek wrote:
>> This new subsystem should unify all fpga drivers which
>> do the same things. Load configuration data to fpga
>> or another programmable logic through common interface.
>> It doesn't matter if it is MMIO device, gpio bitbanging,
>> etc. connection. The point is to have the same
>> inteface for these drivers.
>>
>> Signed-off-by: Michal Simek <michal.simek@xilinx.com>
> 
> [CC] Alan Tull <delicious.quinoa@gmail.com>
> [CC] Yves Vandervennet <rocket.yvanderv@gmail.com>
> 
> Thanks for doing this. Myself and Alan Tull had plans to send this
> upstream, but we wanted to make sure that this framework would also work
> on the Xilinx platform as well. Have you had a chance to test this on a
> SOCFGPA platform? If not, we can go do that.

Sorry. No. I don't have any socfpga platform to be able to test it.
I believe Alan will test it.

>>
>> ---
>>  MAINTAINERS             |   7 +
>>  drivers/Kconfig         |   2 +
>>  drivers/Makefile        |   1 +
>>  drivers/fpga/Kconfig    |  18 ++
>>  drivers/fpga/Makefile   |   5 +
>>  drivers/fpga/fpga-mgr.c | 433 ++++++++++++++++++++++++++++++++++++++++++++++++
>>  include/linux/fpga.h    | 105 ++++++++++++
>>  7 files changed, 571 insertions(+)
>>  create mode 100644 drivers/fpga/Kconfig
>>  create mode 100644 drivers/fpga/Makefile
>>  create mode 100644 drivers/fpga/fpga-mgr.c
>>  create mode 100644 include/linux/fpga.h
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index e61c2e8..5c7597b 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -3427,6 +3427,13 @@ F:	include/linux/fmc*.h
>>  F:	include/linux/ipmi-fru.h
>>  K:	fmc_d.*register
>>
>> +FPGA SUBSYSTEM
>> +M:	Michal Simek <michal.simek@xilinx.com>
> 
> Since the basic framework of this driver was done by Alan Tull and
> myself, can you please add Alan and myself as the maintainer here?

If we end up with any reasonable solution which will suitable
for all of us I have no problem to add you here because every change
in this subsystem should be validated by all parties.
You should be definitely in a CC for all these emails which will
be ensured by adding your names here.

But still there will be just one repo which will store patches
for this subsystem.

>> +T:	git git://git.xilinx.com/linux-xlnx.git
>> +S:	Supported
>> +F:	drivers/fpga/
>> +F:	include/linux/fpga.h
>> +
>>  FPU EMULATOR
>>  M:	Bill Metzenthen <billm@melbpc.org.au>
>>  W:	http://floatingpoint.sourceforge.net/emulator/index.html
>> diff --git a/drivers/Kconfig b/drivers/Kconfig
>> index aa43b91..17f3caa 100644
>> --- a/drivers/Kconfig
>> +++ b/drivers/Kconfig
>> @@ -166,4 +166,6 @@ source "drivers/reset/Kconfig"
>>
>>  source "drivers/fmc/Kconfig"
>>
>> +source "drivers/fpga/Kconfig"
>> +
>>  endmenu
>> diff --git a/drivers/Makefile b/drivers/Makefile
>> index ab93de8..2b5e73b 100644
>> --- a/drivers/Makefile
>> +++ b/drivers/Makefile
>> @@ -152,3 +152,4 @@ obj-$(CONFIG_VME_BUS)		+= vme/
>>  obj-$(CONFIG_IPACK_BUS)		+= ipack/
>>  obj-$(CONFIG_NTB)		+= ntb/
>>  obj-$(CONFIG_FMC)		+= fmc/
>> +obj-$(CONFIG_FPGA)		+= fpga/
>> diff --git a/drivers/fpga/Kconfig b/drivers/fpga/Kconfig
>> new file mode 100644
>> index 0000000..5357645
>> --- /dev/null
>> +++ b/drivers/fpga/Kconfig
>> @@ -0,0 +1,18 @@
>> +#
>> +# FPGA framework configuration
>> +#
>> +
>> +menu "FPGA devices"
>> +
>> +config FPGA
>> +	tristate "FPGA Framework"
>> +	help
>> +	  Say Y here if you want support for configuring FPGAs from the
>> +	  kernel.  The FPGA framework adds a FPGA manager class and FPGA
>> +	  manager drivers.
>> +
>> +if FPGA
> 
> Not sure what this is for?

It is just for adding fpga end driver here. I have here
zynq devcfg driver.
It is just preparation for others end driver.

Thanks,
Michal

-- 
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Microblaze cpu - http://www.monstr.eu/fdt/
Maintainer of Linux kernel - Xilinx Zynq ARM architecture
Microblaze U-BOOT custodian and responsible for u-boot arm zynq platform



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]

  reply	other threads:[~2013-09-19 11:53 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-18 15:56 [RFC PATCH 0/1] FPGA subsystem core Michal Simek
2013-09-18 15:56 ` [RFC PATCH] fpga: Introduce new fpga subsystem Michal Simek
2013-09-18 16:11   ` Joe Perches
2013-09-19 10:01     ` Michal Simek
2013-09-19 16:26       ` Alan Tull
2013-09-18 19:02   ` Dinh Nguyen
2013-09-19 11:53     ` Michal Simek [this message]
2013-09-18 19:15   ` Jason Cooper
2013-09-18 20:32     ` Jason Gunthorpe
2013-09-18 21:17       ` Alan Tull
2013-09-19 10:08         ` Pavel Machek
2013-09-19 11:02           ` Michal Simek
2013-09-20 20:55             ` Alan Tull
2013-09-24 15:55               ` Alan Tull
2013-09-24 15:58                 ` Michal Simek
2013-09-24 16:22                   ` Alan Tull
2013-09-24 22:18                     ` Greg Kroah-Hartman
2013-09-25 13:55                       ` Yves Vandervennet
2013-09-25 14:51                         ` Michal Simek
2013-09-25 18:50                       ` Alan Tull
2013-09-24 22:54           ` H. Peter Anvin
2013-09-25 10:41             ` Michal Simek
2013-09-25 12:00             ` Pavel Machek
2013-09-25 14:27               ` Philip Balister
2013-09-25 14:43                 ` Michal Simek
2013-09-25 19:21                   ` Alan Tull
2013-09-19 10:55         ` Michal Simek
2013-09-19 11:17           ` Pavel Machek
2013-09-19 11:22             ` Michal Simek
2013-09-19 12:52               ` /sys rules " Pavel Machek
2013-09-19 14:06                 ` Greg KH
2013-09-19 14:10                   ` Michal Simek
2013-09-19 14:18                     ` Greg KH
2013-09-19 15:14                       ` Alan Tull
2013-09-19 14:20                     ` Jason Cooper
2013-09-19 14:37                       ` Greg KH
2013-09-19 22:48                         ` Pavel Machek
     [not found]           ` <CADuitaA3PLaOgmqXzfMdMDaXg7G6bT-DufjcuhtWfvaoWRj__Q@mail.gmail.com>
2013-09-19 15:14             ` Michal Simek
2013-09-19 15:18           ` Yves Vandervennet
2013-09-19 17:28             ` Jason Gunthorpe
2013-09-23 13:10               ` Michal Simek
2013-09-23 17:10                 ` Jason Gunthorpe
2013-09-25 10:48                   ` Michal Simek
2013-09-23 13:02             ` Michal Simek
2013-09-19 10:03       ` Pavel Machek
2013-09-19 10:45       ` Michal Simek
2013-09-27 13:31       ` Michal Simek
2013-09-30 17:12         ` Jason Gunthorpe
2013-10-01 15:59           ` Michal Simek
2013-09-18 23:45   ` Ryan Mallon
2013-09-19 11:37     ` Michal Simek

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=523AE5CC.4000909@monstr.eu \
    --to=monstr@monstr.eu \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=atull@altera.com \
    --cc=cesarb@cesarb.net \
    --cc=davem@davemloft.net \
    --cc=davidb@codeaurora.org \
    --cc=delicious.quinoa@gmail.com \
    --cc=dinguyen@altera.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.chehab@samsung.com \
    --cc=michal.simek@xilinx.com \
    --cc=pavel@ucw.cz \
    --cc=philip@balister.org \
    --cc=popcornmix@gmail.com \
    --cc=rocket.yvanderv@gmail.com \
    --cc=rubini@gnudd.com \
    --cc=swarren@nvidia.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).