From: Kent Gibson <warthog618@gmail.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Hans Kurscheidt <lve0200@gmail.com>,
Bartosz Golaszewski <brgl@bgdev.pl>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>
Subject: Re: gpiod: Set pullup for Input Line
Date: Tue, 22 Mar 2022 08:59:11 +0800 [thread overview]
Message-ID: <20220322005911.GA6650@sol> (raw)
In-Reply-To: <CAHp75VcOHCE13oA4m43yAp5e2w=e6uOQhRNneonja6F+XhXmbA@mail.gmail.com>
On Mon, Mar 21, 2022 at 07:33:28PM +0200, Andy Shevchenko wrote:
> On Mon, Mar 21, 2022 at 7:27 PM Hans Kurscheidt <lve0200@gmail.com> wrote:
> >
> > Hi thanks, that makes hope.
>
> First of all, please do not top-post.
>
> > Unfortunately apt-get gpiod on my OrangePi Armbian board gives me
> > version 1.2, while the dev is already at 1.6. I probably have to build
> > it from source.
> >
> > Keeping fingers crossed .
>
> I don't remember the details of old versions of libgpiod (Bart? Kent?)
> I think it was available even there.
>
Bias support was added in libgpiod v1.5.
It wasn't even exposed in the uAPI prior to that - it wasn't added until
kernel v5.5.
In this case building the latest stable, 1.6.3, is the way to go.
Cheers,
Kent.
> > Am 21.03.2022 um 17:26 schrieb Andy Shevchenko:
> > > On Mon, Mar 21, 2022 at 1:30 PM Hans Kurscheidt <lve0200@gmail.com> wrote:
> > >> Despite deep searching, I cannot find any information, if gpiod allow
> > >> specifying pull-ups to input lines and how to do/handle it.
> > > Have you followed this code from libgpiod?
> > > https://git.kernel.org/pub/scm/libs/libgpiod/libgpiod.git/tree/tools/gpioset.c#n44
>
>
> --
> With Best Regards,
> Andy Shevchenko
next prev parent reply other threads:[~2022-03-22 0:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 10:43 gpiod: Set pullup for Input Line Hans Kurscheidt
2022-03-21 13:34 ` Alexander Dahl
2022-03-21 16:26 ` Andy Shevchenko
2022-03-21 17:27 ` Hans Kurscheidt
2022-03-21 17:33 ` Andy Shevchenko
2022-03-21 18:17 ` Hans Kurscheidt
2022-03-21 20:25 ` Fwd: " Hans Kurscheidt
2022-03-22 0:59 ` Kent Gibson [this message]
[not found] ` <1a7fd31a-221e-7b23-b95f-d71e440b3ff0@gmail.com>
2022-03-22 8:39 ` Hans Kurscheidt
2022-03-22 8:50 ` Andy Shevchenko
2022-03-22 9:39 ` Hans Kurscheidt
2022-03-22 16:12 ` Kent Gibson
2022-03-22 16:11 ` Kent Gibson
2022-03-22 16:11 ` Kent Gibson
[not found] <ab3240e5-df61-cff4-ebba-f6a7e5d99f52@gmail.com>
2022-03-21 13:48 ` Hans Kurscheidt
2022-03-21 14:42 ` Alexander Dahl
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=20220322005911.GA6650@sol \
--to=warthog618@gmail.com \
--cc=andy.shevchenko@gmail.com \
--cc=brgl@bgdev.pl \
--cc=linux-gpio@vger.kernel.org \
--cc=lve0200@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 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).