From: Hans Kurscheidt <lve0200@gmail.com>
To: Kent Gibson <warthog618@gmail.com>
Cc: linux-gpio@vger.kernel.org
Subject: Re: Edit/gpiomon: Question about mode
Date: Tue, 29 Mar 2022 10:43:19 +0200 [thread overview]
Message-ID: <3d6f8156-fcf0-21cf-c9bc-6543d982e89a@gmail.com> (raw)
In-Reply-To: <20220329083823.GA94201@sol>
Am 29.03.2022 um 10:38 schrieb Kent Gibson:
> On Tue, Mar 29, 2022 at 10:07:57AM +0200, Hans Kurscheidt wrote:
>> Am 29.03.2022 um 05:38 schrieb Kent Gibson:
>>> 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.
>> It appears 2b reproduceable 100% on my OrangePi zero+ (Allwinner H5) and
>> using -n2 does the trick, but isn't gpiod not supposed to work on all
>> commercial HW platforms and related kernels, rather then only on RPI??
>>
> gpiod will work on any platform with a supporting kernel.
> How well depends on the underlying hardware and driver.
> The RPi4 was merely a counter-example demonstrating that your issue is
> not universal, using hardware I happen to have readily available.
>
> Cheers,
> Kent.
So if I understand you right, gpiod works on sort of a logical level,
while the HW dependend part depends of the kernel driver implementation
of the specific HW?
next prev parent reply other threads:[~2022-03-29 8:43 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
2022-03-29 8:07 ` Hans Kurscheidt
2022-03-29 8:38 ` Kent Gibson
2022-03-29 8:43 ` Hans Kurscheidt [this message]
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=3d6f8156-fcf0-21cf-c9bc-6543d982e89a@gmail.com \
--to=lve0200@gmail.com \
--cc=linux-gpio@vger.kernel.org \
--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 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).