From: Michael Welling <mwelling@ieee.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: "linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
Alexandre Courbot <acourbot@nvidia.com>,
Johan Hovold <johan@kernel.org>,
Markus Pargmann <mpa@pengutronix.de>,
Bamvor Jian Zhang <bamvor.zhangjian@linaro.org>,
Grant Likely <grant.likely@linaro.org>,
Amit Kucheria <amit.kucheria@linaro.org>
Subject: Re: [PATCH v2] gpio: add userspace ABI for GPIO line information
Date: Fri, 19 Feb 2016 03:46:20 -0600 [thread overview]
Message-ID: <20160219094620.GA28750@deathstar> (raw)
In-Reply-To: <CACRpkdYgxJme3V1RSkvmsBL=b5zroNKwPJH70mgDbxMD=XQJtw@mail.gmail.com>
On Fri, Feb 19, 2016 at 09:55:41AM +0100, Linus Walleij wrote:
> On Wed, Feb 17, 2016 at 9:54 PM, Michael Welling <mwelling@ieee.org> wrote:
>
> > After applying the patch from Josh Cartwright:
> > http://www.spinics.net/lists/arm-kernel/msg484070.html
>
> Sorry for screwing up :(
>
> > root@dragonboard-410c:/sys/class/gpio# ~/lsgpio
> > GPIO chip: gpiochip0, "1000000.pinctrl", 122 GPIO lines
> > line 0: unnamed unlabeled
> > (...)
> >
> > Tested-by: Michael Welling <mwelling@ieee.org>
>
> I hope that means you also like where this is going :D
>
I am very happy to see the progress that is being made.
I am looking forward to see how the GPIOs will be modified from userspace.
The fact that single controllers can host hundreds of GPIOs is going to
make it an interesting problem.
Do you have a sketch of how the accesses with be performed?
ioctl, read, write.
Thanks for all of the work so far.
> I merged this to my main branch now.
>
> Yours,
> Linus Walleij
next prev parent reply other threads:[~2016-02-19 9:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-15 13:20 [PATCH v2] gpio: add userspace ABI for GPIO line information Linus Walleij
2016-02-16 18:28 ` Michael Welling
2016-02-17 20:54 ` Michael Welling
2016-02-19 8:55 ` Linus Walleij
2016-02-19 9:46 ` Michael Welling [this message]
2016-02-19 9:47 ` Linus Walleij
2016-02-19 10:26 ` Michael Welling
2016-02-19 11:25 ` Linus Walleij
2016-02-19 11:29 ` Grant Likely
2016-02-19 11:54 ` Linus Walleij
2016-02-19 11:35 ` jic23
2016-02-19 11:51 ` Linus Walleij
2016-02-21 13:13 ` Markus Pargmann
2016-02-21 19:04 ` Linus Walleij
2016-02-22 12:05 ` Markus Pargmann
2016-02-22 12:25 ` Linus Walleij
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=20160219094620.GA28750@deathstar \
--to=mwelling@ieee.org \
--cc=acourbot@nvidia.com \
--cc=amit.kucheria@linaro.org \
--cc=bamvor.zhangjian@linaro.org \
--cc=grant.likely@linaro.org \
--cc=johan@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=mpa@pengutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.