From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: linux-input@vger.kernel.org
Subject: Re: [PATCH] Input: Document no-sleep requirement for playback() callback
Date: Mon, 26 Nov 2012 22:42:38 -0800 [thread overview]
Message-ID: <20121127064238.GA1989@core.coreip.homeip.net> (raw)
In-Reply-To: <1353997935-7210-1-git-send-email-broonie@opensource.wolfsonmicro.com>
On Tue, Nov 27, 2012 at 06:32:15AM +0000, Mark Brown wrote:
> Avoids surprising users.
>
> Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
> ---
> include/linux/input.h | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/include/linux/input.h b/include/linux/input.h
> index 82ce323..0ba0de1 100644
> --- a/include/linux/input.h
> +++ b/include/linux/input.h
> @@ -475,7 +475,8 @@ extern struct class input_class;
> * struct ff_device - force-feedback part of an input device
> * @upload: Called to upload an new effect into device
> * @erase: Called to erase an effect from device
> - * @playback: Called to request device to start playing specified effect
> + * @playback: Called to request device to start playing specified effect.
> + * Must not sleep.
> * @set_gain: Called to set specified gain
> * @set_autocenter: Called to auto-center device
> * @destroy: called by input core when parent input device is being
We already have a few lines below:
> * Note that playback(), set_gain() and set_autocenter() are called with
> * dev->event_lock spinlock held and interrupts off and thus may not
> * sleep.
So I doubt they will pay more attention to your addition ;)
Thanks.
--
Dmitry
next prev parent reply other threads:[~2012-11-27 6:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-27 6:32 [PATCH] Input: Document no-sleep requirement for playback() callback Mark Brown
2012-11-27 6:42 ` Dmitry Torokhov [this message]
2012-11-27 6:47 ` Mark Brown
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=20121127064238.GA1989@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-input@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;
as well as URLs for NNTP newsgroup(s).