linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: baruch@tkos.co.il (Baruch Siach)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/2] gpio: Add driver for Zynq GPIO controller
Date: Fri, 11 Jul 2014 15:27:44 +0300	[thread overview]
Message-ID: <20140711122744.GE3003@tarshish> (raw)
In-Reply-To: <CACRpkdYi_xbixsgvF0NMVdRmxbAgDVOnq-vzYVpDkLHTL8-12A@mail.gmail.com>

Hi Linus,

On Fri, Jul 11, 2014 at 02:06:29PM +0200, Linus Walleij wrote:
> On Fri, Jul 11, 2014 at 8:28 AM, Baruch Siach <baruch@tkos.co.il> wrote:
> > On Tue, Jul 08, 2014 at 11:27:57AM +0200, Linus Walleij wrote:
> 
> >> What is the usecase here?
> >
> > During boot I need to know, for example, when an FPGA is ready to be
> > programmed, and when said FPGA has finished its initialization. I also read
> > the sate of on-board DIP switches to determine the desired boot method. I find
> > the current sysfs interface quite convenient for these and similar tasks.
> 
> So given that an FPGA is a piece of hardware, it should have its firmware
> loaded from the kernel and a kernel driver communicating with it I guess?
> 
> I feel the smell of a huge bundle of userspace drivers for something that
> should be handled by the kernel.

The FPGA can be loaded using simple SPI bit-banging, for which I used the 
userspace SPI interface. Nothing fancy, just a few hundred LoC. Kernel driver 
along with a userspace interface to be maintained forever for this task seems 
an overkill to me.

baruch

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -

  reply	other threads:[~2014-07-11 12:27 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-18 11:39 [PATCH v2 1/2] gpio: Add driver for Zynq GPIO controller Harini Katakam
2014-06-18 11:39 ` [PATCH v2 2/2] devicetree: Add Zynq GPIO devicetree bindings documentation Harini Katakam
2014-07-07 14:53   ` Linus Walleij
2014-07-07 17:35     ` Sören Brinkmann
2014-06-18 15:36 ` [PATCH v2 1/2] gpio: Add driver for Zynq GPIO controller Sören Brinkmann
2014-07-07 14:51   ` Linus Walleij
2014-07-07 15:23     ` Baruch Siach
2014-07-08  9:27       ` Linus Walleij
2014-07-11  6:28         ` Baruch Siach
2014-07-11 12:06           ` Linus Walleij
2014-07-11 12:27             ` Baruch Siach [this message]
2014-07-11 12:38               ` Linus Walleij
2014-07-07 16:08     ` Sören Brinkmann
2014-07-08  9:34       ` Linus Walleij
2014-07-08 15:55         ` Sören Brinkmann
2014-07-10  8:57           ` Linus Walleij
2014-07-07 14:45 ` Linus Walleij
2014-07-07 17:33   ` Sören Brinkmann

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=20140711122744.GE3003@tarshish \
    --to=baruch@tkos.co.il \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).