From: Anssi Hannula <anssi.hannula@gmail.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Jiri Kosina <jkosina@suse.cz>,
linux-input@vger.kernel.org, James Carthew <jcarthew@gmail.com>
Subject: Re: Sleeping inside spinlock in force feedback input event code
Date: Mon, 21 Jul 2008 11:27:31 +0300 [thread overview]
Message-ID: <48844873.8050705@gmail.com> (raw)
In-Reply-To: <20080721042112.GB14432@anvil.corenet.prv>
Dmitry Torokhov wrote:
> On Sun, Jul 20, 2008 at 05:10:21PM +0300, Anssi Hannula wrote:
>> Ping? Please comment :) I'd really much like the hid-pidff driver
>> to not panic when used.
>>
>> For the record, here is a workqueue solution. It is much less
>> intrusive than the previous patch, but IMO less correct.
>>
>
> I was deferring the final judgement to Jiri but I like the generic
> solution with com plete copy of the report best of all. I also wonder if
> we could pre-allocate the buffer for the report queue so we dont need to
> allocate it separately for each request.
It would take (biggest report of the hid device)*64 bytes for output
fifo and (biggest report of the hid device)*256 bytes for control fifo.
Maximum report size is 4096 bytes, though I guess most devices' biggest
report is far shorter than that.
I'll leave it up to you people. I'll be away (military service) for the
next 2 weeks, but after that I can do some quick testing on any
suggested patch on my next short vacation.
--
Anssi Hannula
next prev parent reply other threads:[~2008-07-21 8:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4868e2410806150157o5b290bf7kaccdeb2faf5057d6@mail.gmail.com>
[not found] ` <485540A6.1050306@gmail.com>
[not found] ` <4868e2410806151023j67ceea16pe1c5ad8ab9a8e122@mail.gmail.com>
[not found] ` <4855507E.4030201@gmail.com>
[not found] ` <4868e2410806151036o1a1652d8y8bf8432e3c6c0d06@mail.gmail.com>
[not found] ` <4868e2410806151036r6d96a840v41b8ee745041db35@mail.gmail.com>
[not found] ` <4868e2410806151105v3fec88a1qa439e2cc1423bc6a@mail.gmail.com>
2008-06-15 19:01 ` Sleeping inside spinlock in force feedback input event code Anssi Hannula
2008-06-16 18:34 ` Dmitry Torokhov
2008-06-17 18:52 ` Anssi Hannula
2008-06-17 19:43 ` Dmitry Torokhov
2008-06-17 20:02 ` Anssi Hannula
2008-06-29 1:40 ` Anssi Hannula
2008-07-20 14:10 ` Anssi Hannula
2008-07-21 4:21 ` Dmitry Torokhov
2008-07-21 8:27 ` Anssi Hannula [this message]
2008-07-25 9:25 ` Jiri Kosina
2008-09-20 20:31 ` Anssi Hannula
2008-10-03 9:24 ` Jiri Kosina
2008-10-04 11:33 ` Anssi Hannula
2008-10-04 11:59 ` Jiri Kosina
2008-10-04 12:41 ` Anssi Hannula
2008-10-04 12:46 ` Jiri Kosina
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=48844873.8050705@gmail.com \
--to=anssi.hannula@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=jcarthew@gmail.com \
--cc=jkosina@suse.cz \
--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).