From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Eric Andersson <eric.andersson@unixphere.com>
Cc: dmitry.torokhov@gmail.com, linux-input@vger.kernel.org,
linux-kernel@vger.kernel.org, zhengguang.guo@bosch-sensortec.com,
stefan.nilsson@unixphere.com,
Albert Zhang <xu.zhang@bosch-sensortec.com>
Subject: Re: [PATCH v4 1/1] input: add driver for Bosch Sensortec's BMA150 accelerometer
Date: Thu, 21 Jul 2011 10:56:56 +0100 [thread overview]
Message-ID: <20110721105656.1d579b0b@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <1311203359-23779-2-git-send-email-eric.andersson@unixphere.com>
Only detail thing I see is this trivial one:
> +static int bma150_open(struct bma150_data *bma150)
> +{
> + int ret = bma150_set_mode(bma150->client, BMA150_MODE_NORMAL);
> + msleep(2);
> + return ret;
Does the msleep here need to be inside the mutex lock for the IRQ
case ?
Otherwise it looks good except that the lack of runtime pm means it'll
stop the rest of the bus heirarchy from suspending and breaks
suspend/resume on runtime_pm based systems. I think we still need runtime
pm taking the pm reference on the input open dropping it on the close and
that's about it ? That will be sufficient to let the i2c bus controller
also runtime suspend/resume.
Not so sure about the sysfs drop - but I think its probably the right
thing for upstream and any long term 'we need a fancy driver' would be
via IIO which would sort all the interface problems.
Alan
next prev parent reply other threads:[~2011-07-21 9:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-20 23:09 [PATCH v4 0/1] " Eric Andersson
2011-07-20 23:09 ` [PATCH v4 1/1] " Eric Andersson
2011-07-21 9:56 ` Alan Cox [this message]
2011-07-22 8:34 ` Jonathan Cameron
2011-07-22 13:24 ` Eric Andersson
2011-07-22 15:58 ` Jonathan Cameron
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=20110721105656.1d579b0b@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=dmitry.torokhov@gmail.com \
--cc=eric.andersson@unixphere.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stefan.nilsson@unixphere.com \
--cc=xu.zhang@bosch-sensortec.com \
--cc=zhengguang.guo@bosch-sensortec.com \
/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®