From: Arjan van de Ven <arjan@infradead.org>
To: linux-kernel@vger.kernel.org
Cc: anssi.hannula@gmail.com, dtor_core@ameritech.net
Subject: Re: + input-new-force-feedback-interface.patch added to -mm tree
Date: Thu, 18 May 2006 16:44:01 +0200 [thread overview]
Message-ID: <1147963441.2866.5.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <200605180446.k4I4kFxs007658@shell0.pdx.osdl.net>
On Wed, 2006-05-17 at 21:46 -0700, akpm@osdl.org wrote:
> +
> +#ifdef DEBUG
> +#define debug(format, arg...) printk(KERN_DEBUG "ff-effects: " format "\n" , ## arg)
> +#else
> +#define debug(format, arg...) do {} while (0)
> +#endif
please just use the existing prdebug() thing for this, no need to invent
your own ;)
> +
> +EXPORT_SYMBOL(input_ff_allocate);
> +EXPORT_SYMBOL(input_ff_register);
> +EXPORT_SYMBOL(input_ff_upload);
> +EXPORT_SYMBOL(input_ff_erase);
should these be _GPL exports?
> +
> +#define spin_ff_cond_lock(_ff, _flags) \
> + do { \
> + if (!_ff->driver->playback) \
> + spin_lock_irqsave(&_ff->atomiclock, _flags); \
> + } while (0);
> +
> +#define spin_ff_cond_unlock(_ff, _flags) \
> + do { \
> + if (!_ff->driver->playback) \
> + spin_unlock_irqrestore(&_ff->atomiclock, _flags); \
> + } while (0);
hmmm conditional locking like this always makes me very nervous... what
is preventing ->playback from changing halfway a locked sequence?
> + if (!events) {
> + debug("no actions");
> + del_timer(&ff->timer);
are you really sure you don't need del_timer_sync() here?
> +static void input_ff_timer(unsigned long timer_data)
> +{
> + struct input_dev *dev = (struct input_dev *) timer_data;
> + struct ff_device *ff = dev->ff;
> + struct ff_effect effect;
> + int i;
> + unsigned long flags;
> + int effects_pending;
> + unsigned long effect_handled[NBITS(FF_EFFECTS_MAX)];
hmmm stack space?
> + } else {
> + ret = -ENOSYS;
that is almost always a wrong return value
> + if (test_bit(FF_CONSTANT, dev->ff->flags))
> + set_bit(FF_CONSTANT, dev->ffbit);
> + if (test_bit(FF_SPRING, dev->ff->flags))
> + set_bit(FF_SPRING, dev->ffbit);
> + if (test_bit(FF_FRICTION, dev->ff->flags))
> + set_bit(FF_FRICTION, dev->ffbit);
> + if (test_bit(FF_DAMPER, dev->ff->flags))
> + set_bit(FF_DAMPER, dev->ffbit);
> + if (test_bit(FF_INERTIA, dev->ff->flags))
are you really sure you need atomic set_bit()'s here??
if so.. I think you have a race ;)
next parent reply other threads:[~2006-05-19 1:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200605180446.k4I4kFxs007658@shell0.pdx.osdl.net>
2006-05-18 14:44 ` Arjan van de Ven [this message]
2006-05-22 16:12 ` Anssi Hannula
2006-05-23 1:03 ` Arjan van de Ven
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=1147963441.2866.5.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=anssi.hannula@gmail.com \
--cc=dtor_core@ameritech.net \
--cc=linux-kernel@vger.kernel.org \
/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®