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: Mon, 7 Jul 2014 18:23:09 +0300	[thread overview]
Message-ID: <20140707152309.GH4939@tarshish> (raw)
In-Reply-To: <CACRpkdb1M3-hrSKLKWz21LCJ1sMvsq5E-aqkpmVhy0NwOS5HhA@mail.gmail.com>

Hi Linux,

On Mon, Jul 07, 2014 at 04:51:56PM +0200, Linus Walleij wrote:
> On Wed, Jun 18, 2014 at 5:36 PM, S?ren Brinkmann <soren.brinkmann@xilinx.com> wrote:
> > The first is, how is userspace supposed to find the correct offset for a
> > GPIO pin.
> 
> The sysfs interface to GPIO is *NOT* *GOOD* this is universally
> agreed upon.
> 
> This needs someone to step in and provide a replacement, my preferred
> mechanism would be a /dev/gpiochip0/... hierarchy using char devices.

I really like the ability to control GPIOs from shell, both interactively and 
scripted. I find it useful for quick hardware level debugging, and for boot 
time scripting (mainly in initramfs). Do you intend to preserve this 
capability in the future? Will I need a special utility (or Busybox applet) to 
do this with char device ioctl?

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-07 15:23 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 [this message]
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
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=20140707152309.GH4939@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).