From: Flavio Suligoi <f.suligoi@asem.it>
To: Bartosz Golaszewski <brgl@bgdev.pl>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: "linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: How to use an ACPI declared GPIO in a userspace ...
Date: Tue, 29 Sep 2020 16:10:52 +0000 [thread overview]
Message-ID: <43a2499484c2435eae63fe372f9b7b17@asem.it> (raw)
In-Reply-To: <CAMRc=McnsSkg-7UMp7pKaGX2wSqsZC2jQZV2zRepxm9UxGg=YA@mail.gmail.com>
Hi Bartosz,
> > I need to expose to the userspace a GPIO, physically connected to a
> board
> > push-button. This GPIO must expose a pre-defined name, such as
> > "user-push-button", so that the userspace applications can use it
> without
> > know any physical GPIO details.
> >
> > I can customize the board BIOS and so my goal is to add an ACPI table
> with
> > a content like this:
> >
> > ...
> > Scope (\_SB.GPO1)
> > {
> > Device (BTNS)
> > {
> > Name (_HID, "PRP0001")
> > Name (_DDN, "GPIO buttons device")
> >
> > Name (_CRS, ResourceTemplate ()
> > {
> > GpioIo (
> > Exclusive, // Not shared
> > PullNone, // No need for
> pulls
> > 0, // Debounce
> timeout
> > 0, // Drive
> strength
> > IoRestrictionInputOnly, // Only used as
> input
> > "\\_SB.GPO1", // GPIO
> controller
> > 0, ResourceConsumer, , ) // Must be 0
> > {
> > 25, // GPIO number
> > }
> > ...
> >
> > I know that this GPIO can be used from other drivers.
> > For example I successfully tested it using the "gpio-keys" device
> driver,
> > giving to my GPIO a key-code and emulating in this way a keyboard key.
> > This could be a possible solution.
> >
> > But I prefer to expose my GPIO as a classic GPIO, not as a keyboard key.
> >
> > I was wondering if there is a generic GPIO driver that I can use to
> expose
> > this GPIO with its pre-defined name (caming from the ACPI table
> declaration),
> > to the userspace...
> >
> > Best regards,
> >
> > Flavio
>
> Adding Andy who knows ACPI GPIO well.
>
> In general, the "gpio-line-names" property is used for that and it's
> supported both for device tree as well as ACPI, although I have only
> ever used the former.
>
> Bartosz
Thanks! I'll try!!!
Flavio
prev parent reply other threads:[~2020-09-29 16:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-29 15:37 How to use an ACPI declared GPIO in a userspace Flavio Suligoi
2020-09-29 15:47 ` Bartosz Golaszewski
2020-09-29 16:10 ` Andy Shevchenko
2020-09-29 16:21 ` Flavio Suligoi
2020-09-29 16:27 ` Andy Shevchenko
2020-09-30 12:04 ` Flavio Suligoi
2020-09-30 13:01 ` Andy Shevchenko
2020-09-30 15:39 ` Flavio Suligoi
2020-09-30 15:54 ` Andy Shevchenko
2020-09-30 16:10 ` Andy Shevchenko
2020-10-02 10:02 ` Flavio Suligoi
2020-10-02 12:48 ` Andy Shevchenko
2020-10-02 13:23 ` Andy Shevchenko
2020-10-02 13:29 ` Flavio Suligoi
2020-10-02 10:26 ` Flavio Suligoi
2020-10-02 12:40 ` Andy Shevchenko
2020-09-29 16:10 ` Flavio Suligoi [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=43a2499484c2435eae63fe372f9b7b17@asem.it \
--to=f.suligoi@asem.it \
--cc=andriy.shevchenko@linux.intel.com \
--cc=brgl@bgdev.pl \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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