From: Mike Rapoport <mike@compulab.co.il>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Jean Delvare <khali@linux-fr.org>,
grinberg <grinberg@compulab.co.il>,
linux-input <linux-input@vger.kernel.org>
Subject: Re: [PATCH v2] input: add synaptics_i2c driver
Date: Thu, 11 Jun 2009 13:35:21 +0300 [thread overview]
Message-ID: <4A30DDE9.1050103@compulab.co.il> (raw)
In-Reply-To: <20090611071428.GC8035@dtor-d630.eng.vmware.com>
Hi Dmitry,
Dmitry Torokhov wrote:
> Hi Mike,
>
> On Wed, Jun 03, 2009 at 10:59:27AM +0300, Mike Rapoport wrote:
>> This driver supports Synaptics I2C touchpad controller on eXeda
>> mobile device.
>>
>>
>
> Looks much better, one concern still though:
>
>> +
>> +/* Work Handler */
>> +static void synaptics_i2c_work_handler(struct work_struct *work)
>> +{
>> + int data = 1;
>> + struct synaptics_i2c *touch =
>> + container_of(work, struct synaptics_i2c, dwork.work);
>> + unsigned long delay;
>> +
>> + synaptics_i2c_check_params(touch);
>> +
>> + do {
>> + data = synaptics_i2c_get_input(touch);
>> + delay = synaptics_i2c_fix_delay(touch, data);
>> + } while (data);
>> +
>
> This will spin in the work handler for the duration of the touch
> hogging keventd on this CPU and delaying all other scheduled works. I
> don't think we can do that.
>
> Please try the patchg below and if it still works I will fold it all
> together and queue for upstream. Thanks!
>
Works Ok. Thanks for cleaning up the style :)
--
Sincerely yours,
Mike.
prev parent reply other threads:[~2009-06-11 10:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-20 12:36 [PATCH v2] input: add synaptics_i2c driver Mike Rapoport
2009-05-20 12:49 ` Jean Delvare
2009-06-02 5:40 ` Mike Rapoport
2009-06-02 11:58 ` Dmitry Torokhov
2009-06-03 7:59 ` Mike Rapoport
2009-06-11 5:52 ` Mike Rapoport
2009-06-11 7:14 ` Dmitry Torokhov
2009-06-11 10:35 ` Mike Rapoport [this message]
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=4A30DDE9.1050103@compulab.co.il \
--to=mike@compulab.co.il \
--cc=dmitry.torokhov@gmail.com \
--cc=grinberg@compulab.co.il \
--cc=khali@linux-fr.org \
--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).