From: Pavel Machek <pavel@ucw.cz>
To: "Ильяс Гасанов" <torso.nafi@gmail.com>
Cc: linux-gpio@vger.kernel.org, linux-leds@vger.kernel.org,
linux-watchdog@vger.kernel.org,
Guenter Roeck <linux@roeck-us.net>,
Wim Van Sebroeck <wim@iguana.be>
Subject: Re: A case of watchdog+LED shared GPIO pin
Date: Sun, 4 Mar 2018 20:53:54 +0100 [thread overview]
Message-ID: <20180304195354.GA14472@amd> (raw)
In-Reply-To: <CAEo2pztPD3BoC==+R2AiJ2D3cyBRWphErNTp-evSsFZueK1-Xg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 859 bytes --]
On Sun 2018-03-04 22:45:35, Ильяс Гасанов wrote:
> 2018-03-04 22:19 GMT+03:00 Pavel Machek <pavel@ucw.cz>:
> > Improving WDIOC_SETTIMEOUT is obvious solution. I'd go for that.
>
> Question is, then, - how to do it in a backwards-compatible manner?
> There is very likely to be some userspace software out there which
> relies on the assumption of the currently used whole seconds semantics
> being in effect.
>
> Add a new millisecond argument? But how to detect its presence in the handler?
>
> Introduce a new ioctl? But how to do it neatly and reasonably?
New ioctl. Start from the old one. Keep it neat :-). Negotiate with wd
maintainers if that's ok with them, first.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2018-03-04 19:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-04 16:26 A case of watchdog+LED shared GPIO pin Ильяс Гасанов
2018-03-04 19:19 ` Pavel Machek
2018-03-04 19:45 ` Ильяс Гасанов
2018-03-04 19:53 ` Pavel Machek [this message]
2018-03-07 20:02 ` Guenter Roeck
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=20180304195354.GA14472@amd \
--to=pavel@ucw.cz \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=torso.nafi@gmail.com \
--cc=wim@iguana.be \
/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