All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Simek <monstr@monstr.eu>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: "linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
	Linus Walleij <linus.walleij@linaro.org>
Subject: Re: Getting gpios from user space based on gpio-line-names
Date: Tue, 4 Jul 2017 12:57:29 +0200	[thread overview]
Message-ID: <29fa2aeb-9b5c-746e-66af-e441163c62d9@monstr.eu> (raw)
In-Reply-To: <CAMRc=MdPNMQu27RWGW6D+um4yD+BBnut3Bfy0hC0CUprm99q=Q@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1521 bytes --]

On 3.7.2017 15:06, Bartosz Golaszewski wrote:
> 2017-07-03 15:01 GMT+02:00 Michal Simek <monstr@monstr.eu>:
>> Hi,
>>
>> I am trying to find some docs about how to ask for gpio line
>> based on gpio-line-names in DT. I see line names available via debugfs
>> which is not suitable for production.
>> And also I didn't find a way how to ask for gpio Linux number from user
>> space to start to work with them.
>> This is for gpio mraa integration which depends on Linux gpio line numbers.
>>
>> Thanks,
>> Michal
>>
>> --
>> Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
>> w: www.monstr.eu p: +42-0-721842854
>> Maintainer of Linux kernel - Xilinx Microblaze
>> Maintainer of Linux kernel - Xilinx Zynq ARM and ZynqMP ARM64 SoCs
>> U-Boot custodian - Xilinx Microblaze/Zynq/ZynqMP SoCs
>>
>>
> 
> Hi Michal,
> 
> you can try libgpiod[1] and specifically the gpiofind tool included in
> the repository. Buildroot has this package should you need to build a
> rootfs for some specific target.
> 
> Best regards,
> Bartosz Golaszewski
> 
> [1] https://github.com/brgl/libgpiod
> 

Thanks. That's what I was looking for. I knew that there is new
interface but didn't have this link.

Thanks,
Michal


-- 
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Xilinx Microblaze
Maintainer of Linux kernel - Xilinx Zynq ARM and ZynqMP ARM64 SoCs
U-Boot custodian - Xilinx Microblaze/Zynq/ZynqMP SoCs



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2017-07-04 10:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-03 13:01 Getting gpios from user space based on gpio-line-names Michal Simek
2017-07-03 13:06 ` Bartosz Golaszewski
2017-07-04 10:57   ` Michal Simek [this message]
2017-07-09  7:59 ` Linus Walleij
2017-07-10  6:45   ` Michal Simek

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=29fa2aeb-9b5c-746e-66af-e441163c62d9@monstr.eu \
    --to=monstr@monstr.eu \
    --cc=brgl@bgdev.pl \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@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 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.