From: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
To: linux-kernel@vger.kernel.org
Cc: linux-iio@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 1/3] iio: temperature: mlx90632 Add runtime powermanagement modes
Date: Sun, 2 Oct 2022 18:11:44 +0200 [thread overview]
Message-ID: <e039d9bd-d2e7-a215-4ec2-7f760e1f83b1@wanadoo.fr> (raw)
Message-ID: <20221002161144.AaJr1fdDgNAOlCNpQ-wP6V0Jpnv1_9lGLqeN3_oY3wQ@z> (raw)
In-Reply-To: <a11b83a9-9e25-bbb5-2556-f5244119e3dc@wanadoo.fr>
Le 02/10/2022 à 18:09, Christophe JAILLET a écrit :
>> static int mlx90632_read_raw(struct iio_dev *indio_dev,
>> struct iio_chan_spec const *channel, int *val,
>> int *val2, long mask)
>> {
>> struct mlx90632_data *data = iio_priv(indio_dev);
>> int ret;
>> + int cr;
>
> This 'cr' seems to be unused.
Ok, used in patch 2/3.
Sorry for the noise.
CJ
>
>> +
>> + pm_runtime_get_sync(&data->client->dev);
>> + ret = mlx90632_pm_interraction_wakeup(data);
>> + if (ret < 0)
>> + goto mlx90632_read_raw_pm;
>
> [...]
>
next prev parent reply other threads:[~2022-10-02 16:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 8:13 [PATCH v6 0/3] iio: temperature: mlx90632: Add powermanagement cmo
2022-09-22 8:13 ` [PATCH v6 1/3] iio: temperature: mlx90632 Add runtime powermanagement modes cmo
2022-10-02 16:09 ` Christophe JAILLET
2022-10-02 16:11 ` Christophe JAILLET [this message]
2022-10-02 16:11 ` Christophe JAILLET
2022-10-03 7:43 ` Andy Shevchenko
2022-10-03 8:20 ` Crt Mori
2022-10-09 16:36 ` Jonathan Cameron
2022-09-22 8:13 ` [PATCH v6 2/3] iio: temperature: mlx90632 Read sampling frequency cmo
2022-09-22 8:13 ` [PATCH v6 3/3] iio: temperature: mlx90632 Change return value of sensor measurement channel cmo
2022-09-24 16:32 ` [PATCH v6 0/3] iio: temperature: mlx90632: Add powermanagement Jonathan Cameron
2022-09-26 13:20 ` Crt Mori
2022-10-02 11:25 ` Jonathan Cameron
2022-10-02 14:36 ` Crt Mori
2022-10-02 14:43 ` 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=e039d9bd-d2e7-a215-4ec2-7f760e1f83b1@wanadoo.fr \
--to=christophe.jaillet@wanadoo.fr \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@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).