From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Kent Gibson <warthog618@gmail.com>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Linus Walleij <linus.walleij@linaro.org>,
Jack Winch <sunt.un.morcov@gmail.com>,
Helmut Grohne <helmut.grohne@intenta.de>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>
Subject: Re: [libgpiod][PATCH 4/4] bindings: cxx: implement C++ bindings for libgpiod v2.0
Date: Mon, 28 Jun 2021 14:53:40 +0300 [thread overview]
Message-ID: <CAHp75Vd+5wVa6-B+5kj-0N-wyxr8iT_tSs-A36Pn30p3Z=THQQ@mail.gmail.com> (raw)
In-Reply-To: <20210628113413.GA20057@sol>
On Mon, Jun 28, 2021 at 2:35 PM Kent Gibson <warthog618@gmail.com> wrote:
> On Mon, Jun 28, 2021 at 02:30:05PM +0300, Andy Shevchenko wrote:
> > On Sun, Jun 27, 2021 at 04:47:57PM +0800, Kent Gibson wrote:
...
> > Kent, do I understand correctly that Go bindings use C library?
>
> No, the Go library is pure Go - it makes the ioctl calls itself.
Hmm... Interesting. Why is it so? Performance wise? Other points?
(It means you are basically replicating what libgpiod does, right?)
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2021-06-28 11:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-21 19:18 [libgpiod][PATCH 0/4] libgpiod v2: C++ bindings Bartosz Golaszewski
2021-06-21 19:18 ` [libgpiod][PATCH 1/4] events: hide the *_read_fd() symbols from the API header Bartosz Golaszewski
2021-06-21 19:18 ` [libgpiod][PATCH 2/4] API: drop "peek" functions Bartosz Golaszewski
2021-06-21 19:18 ` [libgpiod][PATCH 3/4] API: add an AS_IS value for bias setting Bartosz Golaszewski
2021-06-21 19:18 ` [libgpiod][PATCH 4/4] bindings: cxx: implement C++ bindings for libgpiod v2.0 Bartosz Golaszewski
2021-06-27 8:47 ` Kent Gibson
2021-06-28 11:30 ` Andy Shevchenko
2021-06-28 11:34 ` Kent Gibson
2021-06-28 11:53 ` Andy Shevchenko [this message]
2021-06-28 14:25 ` Kent Gibson
2021-07-02 8:50 ` Bartosz Golaszewski
2021-07-02 11:38 ` Kent Gibson
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='CAHp75Vd+5wVa6-B+5kj-0N-wyxr8iT_tSs-A36Pn30p3Z=THQQ@mail.gmail.com' \
--to=andy.shevchenko@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=brgl@bgdev.pl \
--cc=helmut.grohne@intenta.de \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=sunt.un.morcov@gmail.com \
--cc=warthog618@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 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.