From: Viresh Kumar <viresh.kumar@st.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Wim Van Sebroeck <wim@iguana.be>,
Wolfram Sang <w.sang@pengutronix.de>,
Linus WALLEIJ <linus.walleij@stericsson.com>,
"linux-watchdog@vger.kernel.org" <linux-watchdog@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] watchdog/coh901327: convert to use watchdog core
Date: Fri, 16 Mar 2012 09:17:16 +0530 [thread overview]
Message-ID: <4F62B7C4.7020702@st.com> (raw)
In-Reply-To: <20120315212705.GH10698@spo001.leaseweb.com>
On 3/16/2012 2:57 AM, Wim Van Sebroeck wrote:
> Hi Linus,
>
>> On Wed, Mar 7, 2012 at 5:42 PM, Wolfram Sang <w.sang@pengutronix.de> wrote:
>>
>>>> case WDIOC_GETTIMELEFT:
>>>> clk_enable(clk);
>>>> /* Read repeatedly until the value is stable! */
>>>
>>> I was wondering if it pays to put this IOCTL to watchdog_dev and add another
>>> callback to watchdog_ops? I'd think so. Wim, Linus, what do you think?
>>
>> OK with me, shall I hack a patch?
>
> I think Viresh did something allready.
You can find it here:
http://www.spinics.net/lists/arm-kernel/msg164285.html
--
viresh
WARNING: multiple messages have this Message-ID (diff)
From: viresh.kumar@st.com (Viresh Kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] watchdog/coh901327: convert to use watchdog core
Date: Fri, 16 Mar 2012 09:17:16 +0530 [thread overview]
Message-ID: <4F62B7C4.7020702@st.com> (raw)
In-Reply-To: <20120315212705.GH10698@spo001.leaseweb.com>
On 3/16/2012 2:57 AM, Wim Van Sebroeck wrote:
> Hi Linus,
>
>> On Wed, Mar 7, 2012 at 5:42 PM, Wolfram Sang <w.sang@pengutronix.de> wrote:
>>
>>>> case WDIOC_GETTIMELEFT:
>>>> clk_enable(clk);
>>>> /* Read repeatedly until the value is stable! */
>>>
>>> I was wondering if it pays to put this IOCTL to watchdog_dev and add another
>>> callback to watchdog_ops? I'd think so. Wim, Linus, what do you think?
>>
>> OK with me, shall I hack a patch?
>
> I think Viresh did something allready.
You can find it here:
http://www.spinics.net/lists/arm-kernel/msg164285.html
--
viresh
next prev parent reply other threads:[~2012-03-16 3:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-07 14:52 [PATCH] watchdog/coh901327: convert to use watchdog core Linus Walleij
2012-03-07 14:52 ` Linus Walleij
2012-03-07 16:42 ` Wolfram Sang
2012-03-07 16:42 ` Wolfram Sang
2012-03-08 6:16 ` Linus Walleij
2012-03-08 6:16 ` Linus Walleij
2012-03-15 21:27 ` Wim Van Sebroeck
2012-03-16 3:47 ` Viresh Kumar [this message]
2012-03-16 3:47 ` Viresh Kumar
2012-03-16 8:15 ` Linus Walleij
2012-03-16 8:15 ` Linus Walleij
2012-03-22 14:49 ` Wim Van Sebroeck
2012-03-22 18:09 ` Linus Walleij
2012-03-22 18:09 ` Linus Walleij
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=4F62B7C4.7020702@st.com \
--to=viresh.kumar@st.com \
--cc=linus.walleij@linaro.org \
--cc=linus.walleij@stericsson.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=w.sang@pengutronix.de \
--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 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.