public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: atull <atull@opensource.altera.com>
To: Moritz Fischer <moritz.fischer@ettus.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
	Jason Gunthorpe <jgunthorpe@obsidianresearch.com>,
	<hpa@zytor.com>, Michal Simek <monstr@monstr.eu>,
	Michal Simek <michal.simek@xilinx.com>, <rdunlap@infradead.org>,
	<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
	Pantelis Antoniou <pantelis.antoniou@konsulko.com>,
	<robh+dt@kernel.org>, Grant Likely <grant.likely@linaro.org>,
	<iws@ovro.caltech.edu>, <linux-doc@vger.kernel.org>,
	<pavel@denx.de>, <broonie@kernel.org>,
	"Philip Balister" <philip@balister.org>, <rubini@gnudd.com>,
	<s.trumtrar@pengutronix.de>, <jason@lakedaemon.net>,
	<kyle.teske@ni.com>, Nicolas Pitre <nico@linaro.org>,
	<balbi@ti.com>, <m.chehab@samsung.com>,
	David Brown <davidb@codeaurora.org>,
	Rob Landley <rob@landley.net>, <davem@davemloft.net>,
	<cesarb@cesarb.net>, <sameo@linux.intel.com>,
	<akpm@linux-foundation.org>,
	Linus Walleij <linus.walleij@linaro.org>, <pawel.moll@arm.com>,
	<mark.rutland@arm.com>, <ijc+devicetree@hellion.org.uk>,
	Kumar Gala <galak@codeaurora.org>, <devel@driverdev.osuosl.org>,
	Petr Cvek <petr.cvek@tul.cz>,
	Alan Tull <delicious.quinoa@gmail.com>, <yvanderv@altera.com>,
	<dinguyen@opensource.altera.com>
Subject: Re: [PATCH v10 3/8] add fpga manager core
Date: Fri, 14 Aug 2015 10:46:58 -0500	[thread overview]
Message-ID: <alpine.DEB.2.02.1508141026280.661@linuxheads99> (raw)
In-Reply-To: <alpine.DEB.2.02.1508140925560.1866@linuxheads99>

On Fri, 14 Aug 2015, atull wrote:

> On Fri, 14 Aug 2015, Moritz Fischer wrote:
> 
> > Hi Alan,
> > 
> > I've updated my Zynq driver (it can be found in an older version
> > against your v8 in the Xilinx tree, too)
> > 
> > https://github.com/mfischer/linux/tree/alan-fpga-mgr-v10
> 
> Since we are both already using this and have been for a while now, I hope it
> can go up into the mainstream instead of continuing to exist only in Altera
> and Xilinx's git trees.
> 

Hi Moritz,

I fetched your git tree and took a look at your low level driver.

I had a some feedback.  write_complete() is a blocking call, waiting for the
FPGA to go into operating state and timing out (ETIMEDOUT) if necessary.  The
fpga-mgr.c framework is assuming that when write_complete exits with status 0,
that means that the FPGA is in operating state.  That's why it's proper for us
to add "mgr->state = FPGA_MGR_STATE_OPERATING" after write_complete returns
success as you noted.  My suggestion is that your write_complete() should check
status in this way.  Whatever error codes it returns will get propagated.

Also, I'm wondering how the simple-fpga-bus stuff looks to you now that you've
had it for a little while.

Thank,
Alan

  reply	other threads:[~2015-08-14 15:52 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-13 17:37 [PATCH v10 0/8] FPGA Manager Framework and Simple FPGA Bus atull
2015-08-13 17:37 ` atull
2015-08-13 17:37 ` [PATCH v10 1/8] usage documentation for FPGA manager core atull
2015-08-13 23:04   ` Moritz Fischer
2015-08-14 14:38     ` atull
2015-08-13 17:37 ` [PATCH v10 2/8] fpga manager: add sysfs interface document atull
2015-08-13 17:37 ` [PATCH v10 3/8] add fpga manager core atull
2015-08-14  1:00   ` Moritz Fischer
2015-08-14 14:33     ` atull
2015-08-14 15:46       ` atull [this message]
2015-08-14 18:42         ` Moritz Fischer
2015-08-17 12:02   ` Pavel Machek
2015-08-13 17:37 ` [PATCH v10 4/8] fpga manager: add driver for socfpga fpga manager atull
2015-08-13 20:50   ` Moritz Fischer
2015-08-13 17:37 ` [PATCH v10 5/8] staging: usage documentation for simple fpga bus atull
2015-08-17 12:03   ` Pavel Machek
2015-08-19 18:28     ` atull
2015-08-19 18:45       ` Moritz Fischer
2015-08-13 17:37 ` [PATCH v10 6/8] staging: add bindings document " atull
2015-08-17 11:52   ` Pavel Machek
2015-08-13 17:37 ` [PATCH v10 7/8] staging: simple-fpga-bus: add TODO document atull
2015-08-13 17:37 ` [PATCH v10 8/8] staging: add simple-fpga-bus atull
2015-08-17 11:56   ` Pavel Machek

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=alpine.DEB.2.02.1508141026280.661@linuxheads99 \
    --to=atull@opensource.altera.com \
    --cc=akpm@linux-foundation.org \
    --cc=balbi@ti.com \
    --cc=broonie@kernel.org \
    --cc=cesarb@cesarb.net \
    --cc=davem@davemloft.net \
    --cc=davidb@codeaurora.org \
    --cc=delicious.quinoa@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dinguyen@opensource.altera.com \
    --cc=galak@codeaurora.org \
    --cc=grant.likely@linaro.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hpa@zytor.com \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=iws@ovro.caltech.edu \
    --cc=jason@lakedaemon.net \
    --cc=jgunthorpe@obsidianresearch.com \
    --cc=kyle.teske@ni.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.chehab@samsung.com \
    --cc=mark.rutland@arm.com \
    --cc=michal.simek@xilinx.com \
    --cc=monstr@monstr.eu \
    --cc=moritz.fischer@ettus.com \
    --cc=nico@linaro.org \
    --cc=pantelis.antoniou@konsulko.com \
    --cc=pavel@denx.de \
    --cc=pawel.moll@arm.com \
    --cc=petr.cvek@tul.cz \
    --cc=philip@balister.org \
    --cc=rdunlap@infradead.org \
    --cc=rob@landley.net \
    --cc=robh+dt@kernel.org \
    --cc=rubini@gnudd.com \
    --cc=s.trumtrar@pengutronix.de \
    --cc=sameo@linux.intel.com \
    --cc=yvanderv@altera.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