linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jiří Prchal" <jiri.prchal@aksignal.cz>
To: Pantelis Antoniou <panto@antoniou-consulting.com>,
	Linus Walleij <linus.walleij@linaro.org>
Cc: Alexandre Courbot <gnurou@gmail.com>,
	"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
	"devicetree-discuss@lists.ozlabs.org"
	<devicetree-discuss@lists.ozlabs.org>,
	Grant Likely <grant.likely@secretlab.ca>
Subject: Re: [PATCH] gpio: add gpio_of_helper
Date: Wed, 29 Oct 2014 08:55:45 +0100	[thread overview]
Message-ID: <54509D81.4070907@aksignal.cz> (raw)
In-Reply-To: <6090A789-9F1B-4787-A9C6-9770A598525D@antoniou-consulting.com>

Hi all,

Dne 28.10.2014 v 18:28 Pantelis Antoniou napsal(a):
> Hi Linus,
>
>> On Oct 28, 2014, at 19:09 , Linus Walleij <linus.walleij@linaro.org> wrote:
>>
>> On Wed, Oct 22, 2014 at 11:58 AM, Pantelis Antoniou
>> <panto@antoniou-consulting.com> wrote:
>>>> On Oct 22, 2014, at 12:41 PM, Alexandre Courbot <gnurou@gmail.com> wrote:
>>
>>>> Pinmux configuration sounds like a job for pinmux more than GPIO, and
>>>> exporting potentially many GPIOs to user-space sounds like a work for
>>>> a proper driver.
>>>
>>> I’m afraid that’s not the case. A great many users (...)
>>
>> How many are many? How long is a piece of string? "Many" may
>> refer to every system on the market or me and my friends.
>> That claim has to be more specific.
>>
>
> On every embedded product board that I have worked on for a customer,
> invariably user-space GPIO was required for some odd pieces of hardware.
>
> I guess that’s in the dozen range for me, and Jiri that originally posted
> seems to be doing something similar too.
Yes.
>
>>> do not require anything
>>> more than setting a pinmux
>>
>> Which can be done (from device tree if need be) using pin control
>> hogs.
>>
>
>>> and the GPIO configuration (input/output).
>>
>> And we have GPIO hogs for that in the pipe.
>>
>
> The original proposal was on January, and there’s a RFC posted just a few days back.
> I will take a look.
>
>>> They can then do low speed I/O using the sysfs interface, without having to
>>> use any complex APIs (shell works just fine).
>>
>> So what is added is export capability, which could be done by supplanting
>> the GPIO hogging mechanism with some linux,export thing.
>>
>
> Yes, that would be nice.
That would be nice for me too, I'll try it later, now I have more urgent work.
>
>>> Think of stuff like controlling a sprinkler valve, or something like a mechanical
>>> door detection open state.
>>
>> OK it's in the department of automatic control, which is arguably the
>> only technical area where userspace GPIO handling actually makes
>> sense.
>>
>
> Err, let’s just say that I completely disagree, but whatever.
>
> If the new GPIO hogging methods make it in mainline along with the export
> mechanism it’d be fine by me.
>
>> Yours,
>> Linus Walleij
>
> Regards
>
> — Pantelis

Yours
Jiri
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-gpio" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
--
To unsubscribe from this list: send the line "unsubscribe linux-gpio" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2014-10-29  7:55 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-22  8:26 [PATCH] gpio: add gpio_of_helper Jiri Prchal
2014-10-22  9:18 ` Alexandre Courbot
2014-10-22  9:24   ` Pantelis Antoniou
2014-10-22  9:41     ` Alexandre Courbot
2014-10-22  9:58       ` Pantelis Antoniou
2014-10-22 11:05         ` Jiří Prchal
2014-10-23  5:08         ` Alexandre Courbot
2014-10-23  6:23           ` Jiří Prchal
2014-10-23  8:53             ` Alexandre Courbot
2014-10-23  9:38               ` Jiří Prchal
2014-10-23 11:23               ` Pantelis Antoniou
2014-10-24  6:23                 ` Alexandre Courbot
2014-10-24  7:31                   ` Jiří Prchal
2014-10-28 17:25                   ` Linus Walleij
2014-10-28 17:09         ` Linus Walleij
2014-10-28 17:28           ` Pantelis Antoniou
2014-10-29  7:55             ` Jiří Prchal [this message]

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=54509D81.4070907@aksignal.cz \
    --to=jiri.prchal@aksignal.cz \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=gnurou@gmail.com \
    --cc=grant.likely@secretlab.ca \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=panto@antoniou-consulting.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).