linux-kernel - RE: How to use an ACPI declared GPIO in a userspace ...

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Fri, 2 Oct 2020 13:29:06 +0000
From:   Flavio Suligoi <f.suligoi@...m.it>
To:     Andy Shevchenko <andy.shevchenko@...il.com>
CC:     Bartosz Golaszewski <brgl@...ev.pl>,
        "linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
        "linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: How to use an ACPI declared GPIO in a userspace ...

HI Andy,

> > So, what about adding the following
> >
> >
> > (Replace '...' with meaningful line names or drop for now, but in any
> > case you need to provide as much names as lines of such GPIO
> > controller)
> 
> I have checked the code, so it allows you to define from 0 up to all
> lines, but no gaps.
> Thus, I have dropped '...' line in above excerpt, added the compiled
> AML to initramfs (initrd method) and voila!
> 
> % gpioinfo gpiochip1
> gpiochip1 - 77 lines:
>        line   0:      "Line0"       unused   input  active-high
>        line   1:      "Line1"       unused   input  active-high
>        line   2:      "Line2"       unused   input  active-high
>        line   3:      unnamed       unused   input  active-high
> 
> 
> % gpiofind Line2
> gpiochip1 2
> 
> Of course you may convert _DSD to be a Method and fill the line names
> dynamically with help of ASL.

Thanks for your help, I try now!

> 
> --
> With Best Regards,
> Andy Shevchenko

Best regards,

Flavio