From: Kent Gibson <warthog618@gmail.com>
To: Hans Kurscheidt <lve0200@gmail.com>
Cc: linux-gpio@vger.kernel.org
Subject: Re: Edit/gpiomon: Question about mode
Date: Tue, 29 Mar 2022 11:38:40 +0800 [thread overview]
Message-ID: <20220329033840.GA14149@sol> (raw)
In-Reply-To: <c02dbd80-5971-7319-17ad-acba33c10da6@gmail.com>
On Mon, Mar 28, 2022 at 07:13:13PM +0200, Hans Kurscheidt wrote:
>
> Am 28.03.2022 um 15:16 schrieb Hans Kurscheidt:
> > Hi,
> >
> > what would be the right mode for gpiomon call from
> >
> > a shellscript executed as root from systemd at system start
> >
> > waiting on a Pin w/ pullup for invoking shutdown upon rising* edge.
> > *changed
> >
> >
> > Lots of interupts, Signals and other GPIO ongoing from other user APPs &
> > threads in multi-user state.
>
> 2b more precise: I wired a GPIO Pin to GND.
>
> Upon the cmd: sudo gpiomon -r -n1 <chip> <offset>
>
> the program exits immediately with 1 event, although there was never a
> rising edge due to the fix wire to GND. Is this a feature or a bug, and is
> it reproducible?
>
Not a feature and not reproducible for me on a Raspberry Pi4 with the
setup you describe, so probably a bug specific to your hardware platform,
whatever that may be.
If it is 100% reproduceable for you, and assuming it is an initialisation
issue so you only get the one spurious event, how about using -n2 as a
workaround ;-)?
Cheers,
Kent.
next prev parent reply other threads:[~2022-03-29 3:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-28 13:16 gpiomon: Question about mode Hans Kurscheidt
2022-03-28 17:13 ` Edit/gpiomon: " Hans Kurscheidt
2022-03-29 3:38 ` Kent Gibson [this message]
2022-03-29 8:07 ` Hans Kurscheidt
2022-03-29 8:38 ` Kent Gibson
2022-03-29 8:43 ` Hans Kurscheidt
2022-03-29 8:51 ` Kent Gibson
2022-03-29 9:03 ` Hans Kurscheidt
2022-03-29 13:37 ` Hans Kurscheidt
2022-03-29 13:56 ` Hans Kurscheidt
2022-03-29 15:25 ` Kent Gibson
2022-03-29 15:26 ` Hans Kurscheidt
2022-03-29 14:46 ` 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=20220329033840.GA14149@sol \
--to=warthog618@gmail.com \
--cc=linux-gpio@vger.kernel.org \
--cc=lve0200@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.