On Mon, 28 Oct 2024 at 14:07, Sverdlin, Alexander <alexander.sverdlin@xxxxxxxxxxx> wrote: > > Hi Bartosz! > > On Mon, 2024-08-12 at 10:22 +0200, Bartosz Golaszewski wrote: > > From: Bartosz Golaszewski <bartosz.golaszewski@xxxxxxxxxx> > > > > 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@xxxxxxxxxxx> > > Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@xxxxxxxxxx> > [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