From: Kent Gibson <warthog618@gmail.com>
To: Alexandre Ghiti <alexandre.ghiti@canonical.com>
Cc: linux-gpio@vger.kernel.org, brgl@bgdev.pl
Subject: Re: libgpiod API v2 release
Date: Thu, 14 Jul 2022 11:10:36 +0800 [thread overview]
Message-ID: <20220714031036.GA74086@sol> (raw)
In-Reply-To: <CA+zEjCsqpAffGqJPJrsLJLeyrJJDch_-Qctb1Zxi+j5JU9Wg9A@mail.gmail.com>
On Tue, Jul 12, 2022 at 09:48:45AM +0200, Alexandre Ghiti wrote:
> Hi,
>
> Ubuntu kernels do not enable GPIO_CDEV_V1 as it is deprecated, but the
> libgpiod package that we ship is still based on the latest version
> 1.6.3 which does not implement the API v2. So I'd like to update
> libgpiod, do you have any recommendations about what branch/sha1 I
> should use? Do you plan to make a release that implements the API v2?
>
Firstly, libgpiod is Bart's library so he is the authority, but this
is my understanding...
TLDR: You should keep GPIO_CDEV_V1 enabled.
v1 is deprecated from a development perspective, so all new feature
development will occur on v2, and new applications should target v2.
Existing apps targetting v1, be that directly or via libgpiod v1.6.3,
will require GPIO_CDEV_V1 until they migrate to v2.
The mainline kernel will continue to support v1 while userspace
transitions.
libgpiod v2 is in active development, and should reach its first release
shortly.
Note that it is NOT a plugin replacement for v1. It has a different API,
for similar reasons to why we had to switch in the kernel, so apps will
need to be actively migrated.
I wouldn't suggest making any effort to package libgpiod v2 until Bart
makes an official release.
Cheers,
Kent.
next prev parent reply other threads:[~2022-07-14 3:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-12 7:48 libgpiod API v2 release Alexandre Ghiti
2022-07-14 3:10 ` Kent Gibson [this message]
2023-03-29 11:03 ` Dimitri John Ledkov
2023-03-29 11:36 ` Kent Gibson
2023-03-29 11:42 ` Dimitri John Ledkov
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=20220714031036.GA74086@sol \
--to=warthog618@gmail.com \
--cc=alexandre.ghiti@canonical.com \
--cc=brgl@bgdev.pl \
--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 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).