From: Wim Van Sebroeck <wim@iguana.be>
To: Oskar Schirmer <oskar@scara.com>
Cc: Sascha Hauer <kernel@pengutronix.de>,
linux-kernel@vger.kernel.org,
Wolfram Sang <w.sang@pengutronix.de>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH v2] watchdog/imx2+: add support for pretimeout interrupt functionality
Date: Tue, 11 Sep 2012 13:00:21 +0200 [thread overview]
Message-ID: <20120911110021.GG27604@spo001.leaseweb.com> (raw)
In-Reply-To: <1347357652-23601-1-git-send-email-oskar@scara.com>
Hi Oskar,
> This watchdog device provides pretimeout facilities:
> Set some timeout value and get informed about imminent
> watchdog activity thru interrupt.
>
> Allow user to wait for this interrupt thru poll(2),
> and to clear it thru read(2).
>
> Signed-off-by: Oskar Schirmer <oskar@scara.com>
> Cc: Wim Van Sebroeck <wim@iguana.be>
> Cc: Wolfram Sang <w.sang@pengutronix.de>
> Cc: Sascha Hauer <kernel@pengutronix.de>
> Cc: Andrew Morton <akpm@linux-foundation.org>
I have a problem with the read and poll.
We had "read()" in the past so we have a possible issue here (different function but userspace apps could still use the old read)...
Can you explain what the read and poll does and where you want to use it.
Kind regards,
Wim.
next prev parent reply other threads:[~2012-09-11 11:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-31 10:37 [PATCH] " Oskar Schirmer
2012-07-03 9:10 ` [PATCH] watchdog/imx2+: add support for pretimeout interrupt Oskar Schirmer
2012-09-05 7:23 ` Oskar Schirmer
2012-09-11 10:00 ` [PATCH v2] watchdog/imx2+: add support for pretimeout interrupt functionality Oskar Schirmer
2012-09-11 11:00 ` Wim Van Sebroeck [this message]
2012-09-11 13:39 ` Oskar Schirmer
2012-09-20 15:37 ` [PATCH v3] " Oskar Schirmer
2012-09-27 13:08 ` Oskar Schirmer
2012-09-27 21:24 ` Wim Van Sebroeck
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=20120911110021.GG27604@spo001.leaseweb.com \
--to=wim@iguana.be \
--cc=akpm@linux-foundation.org \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=oskar@scara.com \
--cc=w.sang@pengutronix.de \
/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
all inboxes | Powered by JetHome®