From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: "Murphy, Dan" <dmurphy@ti.com>
Cc: "V, Hemanth" <hemanthv@ti.com>,
Jonathan Cameron <jic23@cam.ac.uk>,
Andrew Morton <akpm@linux-foundation.org>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [RFC] [PATCH V2 1/2] input: CMA3000 Accelerometer driver
Date: Sun, 29 Aug 2010 11:24:36 -0700 [thread overview]
Message-ID: <20100829182435.GB26209@core.coreip.homeip.net> (raw)
In-Reply-To: <C9D59C82B94F474B872F2092A87F261412470D0874@dlee07.ent.ti.com>
On Fri, Aug 13, 2010 at 08:34:07AM -0500, Murphy, Dan wrote:
> Hemanth
> I have a few comments on this patch.
>
> +static ssize_t cma3000_store_attr_mdfftmr(struct device *dev,
> + struct device_attribute *attr,
> + const char *buf, size_t count)
> +{
> + struct platform_device *pdev = to_platform_device(dev);
> + struct cma3000_accl_data *data = platform_get_drvdata(pdev);
> + unsigned long val;
> + int error;
> +
> + error = strict_strtoul(buf, 0, &val);
> + if (error)
> + return error;
> +
> + mutex_lock(&data->mutex);
> + data->pdata.mdfftmr = val;
> +
> + disable_irq(data->client->irq);
> You should use disable_irq_nosync here. This may not work properly on SMP.
This is an incorrect statement. disable_irq() is not safe to use on SMP when
caller may not sleep (since it will wait for the running handler to
complete), but in this context it is perfectly safe,
--
Dmitry
next prev parent reply other threads:[~2010-08-29 18:24 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-21 6:52 [RFC] [PATCH V2 1/2] input: CMA3000 Accelerometer driver Hemanth V
2010-05-21 11:57 ` Jonathan Cameron
2010-05-21 14:13 ` Hemanth V
2010-08-13 12:47 ` Hemanth V
2010-08-13 13:34 ` Murphy, Dan
2010-08-16 9:45 ` Hemanth V
2010-08-29 18:24 ` Dmitry Torokhov [this message]
2010-08-29 18:49 ` Dmitry Torokhov
2010-08-30 16:04 ` Sensors and the input layer (was Re: [RFC] [PATCH V2 1/2] input: CMA3000 Accelerometer driver) Felipe Balbi
2010-08-30 16:28 ` Dmitry Torokhov
2010-08-30 17:10 ` Felipe Balbi
2010-08-30 17:21 ` Dmitry Torokhov
2010-08-30 18:52 ` Felipe Balbi
2010-08-30 20:50 ` Dmitry Torokhov
2010-08-31 9:53 ` Alan Cox
2010-08-30 17:41 ` Jonathan Cameron
2010-08-30 20:40 ` Alan Cox
2010-08-30 20:44 ` Dmitry Torokhov
2010-08-30 21:28 ` Linus Torvalds
2010-08-30 21:43 ` Dmitry Torokhov
2010-08-30 22:05 ` Linus Torvalds
2010-08-30 22:43 ` Dmitry Torokhov
2010-08-31 5:15 ` Felipe Balbi
2010-08-31 9:44 ` Alan Cox
2010-08-31 12:35 ` Jonathan Cameron
2010-08-31 16:17 ` Dmitry Torokhov
2010-08-31 16:59 ` Alan Cox
2010-08-31 17:09 ` Dmitry Torokhov
2010-08-31 17:24 ` Mohamed Ikbel Boulabiar
2010-08-31 18:14 ` Jonathan Cameron
2010-08-31 22:21 ` Chris Hudson
2010-09-24 13:02 ` Pavel Machek
2010-09-24 13:26 ` Jonathan Cameron
2010-08-31 18:03 ` Jonathan Cameron
2010-08-31 18:20 ` Jonathan Cameron
2010-09-14 7:12 ` Pavel Machek
2010-08-31 9:46 ` Alan Cox
2010-08-31 12:51 ` Jonathan Cameron
2010-08-31 18:18 ` Daniel Barkalow
2010-09-03 10:32 ` [RFC] [PATCH V2 1/2] input: CMA3000 Accelerometer driver Hemanth V
2010-09-03 16:34 ` Dmitry Torokhov
2010-09-06 9:03 ` Hemanth V
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=20100829182435.GB26209@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=dmurphy@ti.com \
--cc=hemanthv@ti.com \
--cc=jic23@cam.ac.uk \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@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).