All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: Jonas Jensen <jonas.jensen@gmail.com>
Cc: openwrt-devel@openwrt.org, Alexandre Courbot <gnurou@gmail.com>,
	Paulius Zaleckas <paulius.zaleckas@gmail.com>,
	"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
	Janos Laube <janos.dev@gmail.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 4/6] gpio: gemini: rename to match Faraday IP
Date: Thu, 23 Mar 2017 13:47:20 +0100	[thread overview]
Message-ID: <CACRpkdY0Nj19KgYXfs5GZQrbxSJ-6zZkdo+bYo7Ss_Qo7EgP_Q@mail.gmail.com> (raw)
In-Reply-To: <CACmBeS23APp1=+0Cypyx9OujhekUTF7w5QbwE_9zt_go3GdUPw@mail.gmail.com>

On Wed, Mar 22, 2017 at 11:21 AM, Jonas Jensen <jonas.jensen@gmail.com> wrote:
> On 22 March 2017 at 09:42, Linus Walleij <linus.walleij@linaro.org> wrote:

>> Nice! Have you tested my new GPIO character device tools from
>> tools/gpio/* in the kernel tree?
>
> I had not and thanks for pointing that out, lsgpio lists all available
> gpios (though most of them are unnamed), and gpio-hammer successfully
> toggled buzzer on/off.

Nice.

> GPIO chip: gpiochip0, "FTGPIO010", 32 GPIO lines
>         line  0: unnamed unused [output]
>         line  1: unnamed unused [output]
>         line  2: unnamed unused [output]
>         line  3: unnamed unused [output]

BTW you can name all the "unnamed" lines by using
gpio-line-names in the gpio node of the device tree, c.f.
commit 3a1689ea752436917c5ce4487527ed6c444630ee

>         line 24: unnamed unused [output]
>         line 25: unnamed unused
>         line 26: unnamed unused
>         line 27: unnamed "ready-led" [kernel output active-low]
(...)
>
> ./gpio-hammer -n gpiochip0 -o 24
> Hammer lines [24] on gpiochip0, initial states: [0]
> [|] [24: 1]
>
> ./gpio-hammer -n gpiochip0 -o 27
> Failed to issue GET LINEHANDLE IOCTL (-16)

So finally when the kernel is using a GPIO line you can't use it
from userspace at the same time. -16 is -EBUSY.

Yours,
Linus Walleij
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

WARNING: multiple messages have this Message-ID (diff)
From: linus.walleij@linaro.org (Linus Walleij)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/6] gpio: gemini: rename to match Faraday IP
Date: Thu, 23 Mar 2017 13:47:20 +0100	[thread overview]
Message-ID: <CACRpkdY0Nj19KgYXfs5GZQrbxSJ-6zZkdo+bYo7Ss_Qo7EgP_Q@mail.gmail.com> (raw)
In-Reply-To: <CACmBeS23APp1=+0Cypyx9OujhekUTF7w5QbwE_9zt_go3GdUPw@mail.gmail.com>

On Wed, Mar 22, 2017 at 11:21 AM, Jonas Jensen <jonas.jensen@gmail.com> wrote:
> On 22 March 2017 at 09:42, Linus Walleij <linus.walleij@linaro.org> wrote:

>> Nice! Have you tested my new GPIO character device tools from
>> tools/gpio/* in the kernel tree?
>
> I had not and thanks for pointing that out, lsgpio lists all available
> gpios (though most of them are unnamed), and gpio-hammer successfully
> toggled buzzer on/off.

Nice.

> GPIO chip: gpiochip0, "FTGPIO010", 32 GPIO lines
>         line  0: unnamed unused [output]
>         line  1: unnamed unused [output]
>         line  2: unnamed unused [output]
>         line  3: unnamed unused [output]

BTW you can name all the "unnamed" lines by using
gpio-line-names in the gpio node of the device tree, c.f.
commit 3a1689ea752436917c5ce4487527ed6c444630ee

>         line 24: unnamed unused [output]
>         line 25: unnamed unused
>         line 26: unnamed unused
>         line 27: unnamed "ready-led" [kernel output active-low]
(...)
>
> ./gpio-hammer -n gpiochip0 -o 24
> Hammer lines [24] on gpiochip0, initial states: [0]
> [|] [24: 1]
>
> ./gpio-hammer -n gpiochip0 -o 27
> Failed to issue GET LINEHANDLE IOCTL (-16)

So finally when the kernel is using a GPIO line you can't use it
from userspace at the same time. -16 is -EBUSY.

Yours,
Linus Walleij

  reply	other threads:[~2017-03-23 12:47 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-12 23:28 [PATCH 1/6] gpio: gemini: augment DT bindings Linus Walleij
2017-03-12 23:28 ` Linus Walleij
2017-03-12 23:28 ` [PATCH 2/6] ARM: dts: augment Gemini GPIO nodes Linus Walleij
2017-03-12 23:28   ` Linus Walleij
2017-03-12 23:28 ` [PATCH 3/6] ARM: dts: augment Moxa ART GPIO node Linus Walleij
2017-03-12 23:28   ` Linus Walleij
2017-03-12 23:28 ` [PATCH 4/6] gpio: gemini: rename to match Faraday IP Linus Walleij
2017-03-12 23:28   ` Linus Walleij
2017-03-21 10:59   ` Jonas Jensen
2017-03-21 10:59     ` Jonas Jensen
2017-03-22  8:42     ` Linus Walleij
2017-03-22  8:42       ` Linus Walleij
2017-03-22 10:21       ` Jonas Jensen
2017-03-22 10:21         ` Jonas Jensen
2017-03-23 12:47         ` Linus Walleij [this message]
2017-03-23 12:47           ` Linus Walleij
2017-03-12 23:28 ` [PATCH 5/6] gpio: moxart: Switch to using the FTGPIO010 driver Linus Walleij
2017-03-12 23:28   ` Linus Walleij
2017-03-12 23:28 ` [PATCH 6/6] ARM: gemini: select the right GPIO block Linus Walleij
2017-03-12 23:28   ` Linus Walleij
2017-03-20 17:16 ` [PATCH 1/6] gpio: gemini: augment DT bindings Rob Herring
2017-03-20 17:16   ` Rob Herring

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=CACRpkdY0Nj19KgYXfs5GZQrbxSJ-6zZkdo+bYo7Ss_Qo7EgP_Q@mail.gmail.com \
    --to=linus.walleij@linaro.org \
    --cc=gnurou@gmail.com \
    --cc=janos.dev@gmail.com \
    --cc=jonas.jensen@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=openwrt-devel@openwrt.org \
    --cc=paulius.zaleckas@gmail.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 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.