From: Andrew Morton <akpm@linux-foundation.org>
To: "Richard Röjfors" <richard.rojfors.ext@mocean-labs.com>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
kwangwoo.lee@gmail.com, thierry.reding@avionic-design.de,
soni.trilok@gmail.com
Subject: Re: [PATCH 1/2] tsc2007: remove HR timer
Date: Thu, 25 Jun 2009 14:20:10 -0700 [thread overview]
Message-ID: <20090625142010.bd656a9d.akpm@linux-foundation.org> (raw)
In-Reply-To: <4A40C288.2060702@mocean-labs.com>
On Tue, 23 Jun 2009 13:54:48 +0200
Richard R__jfors <richard.rojfors.ext@mocean-labs.com> wrote:
> This patch removes the HR timer, since it's bad to do synchronous I2C
> in the HR timer callback context. The new implementation makes use
> of the global workqueue. The work is scheduled every 5ms when polling
> rather than 5 us.
>
"it's bad" isn't a very good description of the problem which the patch
fixes.
This matters. People wish to make decisions about whether this patch
is needed in 2.6.29.x, 2.6.30.x, 2.6.31, 2.6.32, etc. Without knowing
the effects of the problem which the patch fixes, we cannot make that
decision!
>
> + /* cancel any work */
> + cancel_delayed_work(&ts->work);
> +
Should this have been cancel_delayed_work_sync()?
/*
* Kill off a pending schedule_delayed_work(). Note that the work callback
* function may still be running on return from cancel_delayed_work(), unless
* it returns 1 and the work doesn't re-arm itself. Run flush_workqueue() or
* cancel_work_sync() to wait on it.
*/
static inline int cancel_delayed_work(struct delayed_work *work)
next prev parent reply other threads:[~2009-06-25 21:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-23 11:54 [PATCH 1/2] tsc2007: remove HR timer Richard Röjfors
2009-06-25 21:20 ` Andrew Morton [this message]
2009-07-09 16:51 ` Richard Röjfors
2009-07-14 4:59 ` Dmitry Torokhov
2009-07-14 7:08 ` Thierry Reding
2009-07-14 8:00 ` Richard Röjfors
2009-07-14 8:21 ` Dmitry Torokhov
2009-07-14 8:21 ` Dmitry Torokhov
2009-07-14 8:47 ` Richard Röjfors
2009-07-24 14:39 ` Richard Röjfors
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=20090625142010.bd656a9d.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=kwangwoo.lee@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=richard.rojfors.ext@mocean-labs.com \
--cc=soni.trilok@gmail.com \
--cc=thierry.reding@avionic-design.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;
as well as URLs for NNTP newsgroup(s).