From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
To: "Sverdlin, Alexander" <alexander.sverdlin@siemens.com>
Cc: "brgl@bgdev.pl" <brgl@bgdev.pl>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>
Subject: Re: [PATCH libgpiod v5 4/4] dbus: add the D-Bus daemon, command-line client and tests
Date: Mon, 28 Oct 2024 20:13:12 +0100 [thread overview]
Message-ID: <CACMJSetD8JeP+5AV9tcGXPVQQaUO=e3bG6ZNVd82kdREOqXUJw@mail.gmail.com> (raw)
In-Reply-To: <93c9d617df7cc3f6814a56d07d90aa3f98e352f6.camel@siemens.com>
On Mon, 28 Oct 2024 at 14:07, Sverdlin, Alexander
<alexander.sverdlin@siemens.com> wrote:
>
> Hi Bartosz!
>
> On Mon, 2024-08-12 at 10:22 +0200, Bartosz Golaszewski wrote:
> > From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
> >
> > Add the D-Bus API definition and its implementation in the form of a GPIO
> > manager daemon and a companion command-line client as well as some
> > additional configuration and data files (systemd service, example udev
> > configuration, etc.) and test suites.
> >
> > Tested-by: Alexander Sverdlin <alexander.sverdlin@siemens.com>
> > Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
>
[snip]
>
> Strange, I'd expect from this code to detect pre-existing chips immediately,
> but this is not what I observe in practice:
>
> $ gpiocli info --chip=gpiochip0 | head -n 1
> gpiochip0 - 24 lines:
> $ gpiocli wait --chip=gpiochip0 --timeout=1
> gpiocli wait: wait timed out!
>
> (without timeout it would wait endlessly)
>
> This is not expected, right, otherwise it would be counter-intuitive and racy?
>
gpiochip0 here is the device name. It's dynamic so you cannot use it
with gpiocli wait as you cannot know it in advance. You need to use
the label of the chip instead.
IOW it's a feature. :)
Bart
next prev parent reply other threads:[~2024-10-28 19:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 8:22 [PATCH libgpiod v5 0/4] dbus: add GLib-based D-Bus daemon and command-line client Bartosz Golaszewski
2024-08-12 8:22 ` [PATCH libgpiod v5 1/4] tests: split out reusable test code into a local static library Bartosz Golaszewski
2024-08-12 8:22 ` [PATCH libgpiod v5 2/4] tests: split out the common test code for bash scripts Bartosz Golaszewski
2024-08-12 8:22 ` [PATCH libgpiod v5 3/4] bindings: add GLib bindings Bartosz Golaszewski
2024-08-12 8:22 ` [PATCH libgpiod v5 4/4] dbus: add the D-Bus daemon, command-line client and tests Bartosz Golaszewski
2024-10-28 13:07 ` Sverdlin, Alexander
2024-10-28 19:13 ` Bartosz Golaszewski [this message]
2024-10-28 19:35 ` Sverdlin, Alexander
2024-10-28 19:44 ` Bartosz Golaszewski
2024-10-28 19:52 ` Sverdlin, Alexander
2024-08-12 13:19 ` [PATCH libgpiod v5 0/4] dbus: add GLib-based D-Bus daemon and command-line client Andy Shevchenko
2024-08-13 8:49 ` 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='CACMJSetD8JeP+5AV9tcGXPVQQaUO=e3bG6ZNVd82kdREOqXUJw@mail.gmail.com' \
--to=bartosz.golaszewski@linaro.org \
--cc=alexander.sverdlin@siemens.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).