Linux GPIO subsystem development
 help / color / mirror / Atom feed
From: Kent Gibson <warthog618@gmail.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: "Linus Walleij" <linus.walleij@linaro.org>,
	"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
	Darrien <darrien@freenet.de>,
	"Viresh Kumar" <viresh.kumar@linaro.org>,
	"Jiri Benc" <jbenc@upir.cz>, "Joel Savitz" <joelsavitz@gmail.com>,
	"Alexander Stein" <alexander.stein@mailbox.org>,
	"David Kozub" <zub@linux.fjfi.cvut.cz>,
	"Jan Kundrát" <jan.kundrat@cesnet.cz>,
	"Michael Beach" <michaelb@ieee.org>,
	"Jack Winch" <sunt.un.morcov@gmail.com>,
	"Geert Uytterhoeven" <geert@linux-m68k.org>,
	linux-gpio@vger.kernel.org,
	"Ben Hutchings" <ben.hutchings@mind.be>
Subject: Re: [libgpiod v2][PATCH] treewide: implement v2 API
Date: Thu, 2 Jun 2022 19:52:41 +0800	[thread overview]
Message-ID: <20220602115241.GA43087@sol> (raw)
In-Reply-To: <20220602112656.31261-1-brgl@bgdev.pl>

On Thu, Jun 02, 2022 at 01:26:56PM +0200, Bartosz Golaszewski wrote:
> This is the main changeset implementing the new libgpiod API for the core
> C library as well as C++ and Python bindings. It's actually the effect of
> squashing all the patches we've had in the next/libgpiod-v2.0 branch (and
> that have been developed and reviewed over the course of several months)
> so that the master branch can remain bisectable.
> 
> Big thanks to Kent Gibson for his reviews.
> 
> Signed-off-by: Bartosz Golaszewski <brgl@bgdev.pl>
> [Ben: fix format specifier for uint64_t]
> Signed-off-by: Ben Hutchings <ben.hutchings@mind.be>
> [Viresh: Fix ioctl number for gpiod_line_request_reconfigure_lines()]
> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
> [Kent: splitting of chip_info out of chip, documentation tweaks and some renaming]
> Signed-off-by: Kent Gibson <warthog618@gmail.com>
> ---
> There were no reviews so far for the python bindings but I'm generally
> happy with them and think that the contents of next/libgpiod-2.0 branch
> are mature enough to get them into master and continue the work incrementally
> there. So this is the amalgamation of all the work done so far on libgpiod v2
> that I'd like to apply soon.
> 

My apologies for not getting back to you earlier wrt the python
bindings.
When I try them I get:

$ python3
Python 3.9.2 (default, Feb 28 2021, 17:03:44)
[GCC 10.2.1 20210110] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import gpiod
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "exception.c", line 1, in <module>
NameError: __build_class__ not found
>>>

I may be doing something dopey, but building v1.6.3 on the same
platform (a clean Debian 11.3 install with a v5.18 kernel with gpiosim
and gpio-mockup) works fine.
Haven't had a chance to look into it further...

Any ideas?

Cheers,
Kent.

       reply	other threads:[~2022-06-02 11:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220602112656.31261-1-brgl@bgdev.pl>
2022-06-02 11:52 ` Kent Gibson [this message]
2022-06-02 13:34   ` [libgpiod v2][PATCH] treewide: implement v2 API Bartosz Golaszewski

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=20220602115241.GA43087@sol \
    --to=warthog618@gmail.com \
    --cc=alexander.stein@mailbox.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=ben.hutchings@mind.be \
    --cc=brgl@bgdev.pl \
    --cc=darrien@freenet.de \
    --cc=geert@linux-m68k.org \
    --cc=jan.kundrat@cesnet.cz \
    --cc=jbenc@upir.cz \
    --cc=joelsavitz@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=michaelb@ieee.org \
    --cc=sunt.un.morcov@gmail.com \
    --cc=viresh.kumar@linaro.org \
    --cc=zub@linux.fjfi.cvut.cz \
    /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