From: Jonathan Cameron <jic23@kernel.org>
To: Alison Schofield <amsfield22@gmail.com>
Cc: afd@ti.com, knaack.h@gmx.de, lars@metafoo.de, pmeerw@pmeerw.net,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: health: afe4404: retrieve a valid iio_dev in suspend/resume
Date: Sat, 21 Jan 2017 13:13:43 +0000 [thread overview]
Message-ID: <921be868-529b-bac2-dbca-f1a8ad943cf7@kernel.org> (raw)
In-Reply-To: <20170115035241.GA19555@d830.WORKGROUP>
On 15/01/17 03:52, Alison Schofield wrote:
> The suspend/resume functions were using dev_to_iio_dev() to get
> the iio_dev. That only works on IIO dev's. Replace it with i2c
> functions to get the correct iio_dev.
>
> Signed-off-by: Alison Schofield <amsfield22@gmail.com>
Applied with Andrew's Ack.
> ---
> drivers/iio/health/afe4404.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/iio/health/afe4404.c b/drivers/iio/health/afe4404.c
> index 4526640..964f523 100644
> --- a/drivers/iio/health/afe4404.c
> +++ b/drivers/iio/health/afe4404.c
> @@ -428,7 +428,7 @@ MODULE_DEVICE_TABLE(of, afe4404_of_match);
>
> static int __maybe_unused afe4404_suspend(struct device *dev)
> {
> - struct iio_dev *indio_dev = dev_to_iio_dev(dev);
> + struct iio_dev *indio_dev = i2c_get_clientdata(to_i2c_client(dev));
> struct afe4404_data *afe = iio_priv(indio_dev);
> int ret;
>
> @@ -449,7 +449,7 @@ static int __maybe_unused afe4404_suspend(struct device *dev)
>
> static int __maybe_unused afe4404_resume(struct device *dev)
> {
> - struct iio_dev *indio_dev = dev_to_iio_dev(dev);
> + struct iio_dev *indio_dev = i2c_get_clientdata(to_i2c_client(dev));
> struct afe4404_data *afe = iio_priv(indio_dev);
> int ret;
>
>
prev parent reply other threads:[~2017-01-21 13:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-15 3:52 [PATCH] iio: health: afe4404: retrieve a valid iio_dev in suspend/resume Alison Schofield
2017-01-21 13:13 ` Jonathan Cameron [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=921be868-529b-bac2-dbca-f1a8ad943cf7@kernel.org \
--to=jic23@kernel.org \
--cc=afd@ti.com \
--cc=amsfield22@gmail.com \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
/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).