devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Baruch Siach <baruch@tkos.co.il>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: "Sören Brinkmann" <soren.brinkmann@xilinx.com>,
	"Mark Rutland" <mark.rutland@arm.com>,
	"Alexandre Courbot" <gnurou@gmail.com>,
	"Harini Katakam" <harinik@xilinx.com>,
	"Pawel Moll" <pawel.moll@arm.com>,
	"ijc+devicetree@hellion.org.uk" <ijc+devicetree@hellion.org.uk>,
	"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
	"Michal Simek" <michal.simek@xilinx.com>,
	"Harini Katakam" <harinikatakamlinux@gmail.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"Rob Herring" <robh+dt@kernel.org>,
	"Rob Landley" <rob@landley.net>,
	"Kumar Gala" <galak@codeaurora.org>,
	"Grant Likely" <grant.likely@linaro.org>,
	"Harini Katakam" <harini.katakam@xilinx.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2 1/2] gpio: Add driver for Zynq GPIO controller
Date: Fri, 11 Jul 2014 09:28:11 +0300	[thread overview]
Message-ID: <20140711062811.GC3003@tarshish> (raw)
In-Reply-To: <CACRpkdY+3hy5iw=uRdmu665NWsoGacTMgjUq97219kEcfn7Dqw@mail.gmail.com>

Hi Linus,

On Tue, Jul 08, 2014 at 11:27:57AM +0200, Linus Walleij wrote:
> On Mon, Jul 7, 2014 at 5:23 PM, Baruch Siach <baruch@tkos.co.il> wrote:
> > On Mon, Jul 07, 2014 at 04:51:56PM +0200, Linus Walleij wrote:
> 
> >> 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,
> 
> I would be happy to carry it in the unstable-ABI debugfs for sure.
> It's the supported ABI that bothers me.
> 
> > and for boot
> > time scripting (mainly in initramfs).
> 
> 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.

baruch

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

  reply	other threads:[~2014-07-11  6:28 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
     [not found] ` <1403091577-10232-1-git-send-email-harinik-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org>
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 [this message]
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=20140711062811.GC3003@tarshish \
    --to=baruch@tkos.co.il \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=gnurou@gmail.com \
    --cc=grant.likely@linaro.org \
    --cc=harini.katakam@xilinx.com \
    --cc=harinik@xilinx.com \
    --cc=harinikatakamlinux@gmail.com \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=michal.simek@xilinx.com \
    --cc=pawel.moll@arm.com \
    --cc=rob@landley.net \
    --cc=robh+dt@kernel.org \
    --cc=soren.brinkmann@xilinx.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).