From: Jonathan Cameron <jic23@kernel.org>
To: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Cc: linux-iio@vger.kernel.org
Subject: Re: [PATCH v1 1/4] iio: gyro: bmg160: Error handling when mode set fails
Date: Sun, 16 Nov 2014 20:19:43 +0000 [thread overview]
Message-ID: <546906DF.2030805@kernel.org> (raw)
In-Reply-To: <1412998408-31870-2-git-send-email-srinivas.pandruvada@linux.intel.com>
On 11/10/14 04:33, Srinivas Pandruvada wrote:
> When mode set fails due to some transient failures, it will atleast
> reset the state of runtime usage count and also let the runtime
> suspend retry from the driver framework.
>
> Signed-off-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Applied to the fixes-togreg branch of iio.git.
Thanks,
> ---
> drivers/iio/gyro/bmg160.c | 14 +++++++++++++-
> 1 file changed, 13 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/iio/gyro/bmg160.c b/drivers/iio/gyro/bmg160.c
> index 1f967e0d..22bf9db 100644
> --- a/drivers/iio/gyro/bmg160.c
> +++ b/drivers/iio/gyro/bmg160.c
> @@ -250,6 +250,9 @@ static int bmg160_set_power_state(struct bmg160_data *data, bool on)
> if (ret < 0) {
> dev_err(&data->client->dev,
> "Failed: bmg160_set_power_state for %d\n", on);
> + if (on)
> + pm_runtime_put_noidle(&data->client->dev);
> +
> return ret;
> }
> #endif
> @@ -705,6 +708,7 @@ static int bmg160_write_event_config(struct iio_dev *indio_dev,
>
> ret = bmg160_setup_any_motion_interrupt(data, state);
> if (ret < 0) {
> + bmg160_set_power_state(data, false);
> mutex_unlock(&data->mutex);
> return ret;
> }
> @@ -871,6 +875,7 @@ static int bmg160_data_rdy_trigger_set_state(struct iio_trigger *trig,
> else
> ret = bmg160_setup_new_data_interrupt(data, state);
> if (ret < 0) {
> + bmg160_set_power_state(data, false);
> mutex_unlock(&data->mutex);
> return ret;
> }
> @@ -1169,8 +1174,15 @@ static int bmg160_runtime_suspend(struct device *dev)
> {
> struct iio_dev *indio_dev = i2c_get_clientdata(to_i2c_client(dev));
> struct bmg160_data *data = iio_priv(indio_dev);
> + int ret;
>
> - return bmg160_set_mode(data, BMG160_MODE_SUSPEND);
> + ret = bmg160_set_mode(data, BMG160_MODE_SUSPEND);
> + if (ret < 0) {
> + dev_err(&data->client->dev, "set mode failed\n");
> + return -EAGAIN;
> + }
> +
> + return 0;
> }
>
> static int bmg160_runtime_resume(struct device *dev)
>
next prev parent reply other threads:[~2014-11-16 20:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-11 3:33 [PATCH v1 0/4] BMG160 updates Srinivas Pandruvada
2014-10-11 3:33 ` [PATCH v1 1/4] iio: gyro: bmg160: Error handling when mode set fails Srinivas Pandruvada
2014-11-16 20:19 ` Jonathan Cameron [this message]
2014-10-11 3:33 ` [PATCH v1 2/4] iio: gyro: bmg160: Don't let interrupt mode to be open drain Srinivas Pandruvada
2014-11-16 20:20 ` Jonathan Cameron
2014-10-11 3:33 ` [PATCH v1 3/4] iio: gyro: bmg160: Send x, y and z motion separately Srinivas Pandruvada
2014-11-16 20:21 ` Jonathan Cameron
2014-10-11 3:33 ` [PATCH v1 4/4] iio: gyro: bmg160: Fix iio_event_spec direction Srinivas Pandruvada
2014-11-16 20:21 ` 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=546906DF.2030805@kernel.org \
--to=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=srinivas.pandruvada@linux.intel.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;
as well as URLs for NNTP newsgroup(s).