From: Jonathan Cameron <jic23@kernel.org>
To: Matt Ranostay <mranostay@gmail.com>
Cc: "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Subject: Re: [PATCH] iio: light: apds9960: correct ->last_busy count
Date: Sun, 15 Nov 2015 11:19:57 +0000 [thread overview]
Message-ID: <56486A5D.6090100@kernel.org> (raw)
In-Reply-To: <CAKzfze-dhPiOksAdnGW=FjS346LxZ66kFMd30OiRKRg6U57+rw@mail.gmail.com>
On 08/11/15 21:23, Matt Ranostay wrote:
> On Sun, Nov 8, 2015 at 7:13 AM, Jonathan Cameron <jic23@kernel.org> wrote:
>> On 08/11/15 04:21, Matt Ranostay wrote:
>>> Add missing pm_runtime_mark_last_busy to apds9960_set_power_state
>>> function.
>>>
>>> Signed-off-by: Matt Ranostay <mranostay@gmail.com>
>> Hi Matt,
>>
>> Could you elaborate on what the result of this not being there is?
>> My first thought is that this probably wants to go as a fix, but for
>> that I need details of what the effects of the 'bug' are.
>
> Unless pm_runtime_mark_last_busy is called the
> pm_runtime_put_autosuspend may put the device into suspend before the
> delay time requested.
Have added this text to the commit message and applied to the
temporary branch
fixes-togreg-post-rc1 which should go out in a few days.
Jonathan
>
>
> Thanks,
>
> Matt
>
>
>>
>> Jonathan
>>> ---
>>> drivers/iio/light/apds9960.c | 1 +
>>> 1 file changed, 1 insertion(+)
>>>
>>> diff --git a/drivers/iio/light/apds9960.c b/drivers/iio/light/apds9960.c
>>> index 7d269ef..f6a07dc 100644
>>> --- a/drivers/iio/light/apds9960.c
>>> +++ b/drivers/iio/light/apds9960.c
>>> @@ -453,6 +453,7 @@ static int apds9960_set_power_state(struct apds9960_data *data, bool on)
>>> usleep_range(data->als_adc_int_us,
>>> APDS9960_MAX_INT_TIME_IN_US);
>>> } else {
>>> + pm_runtime_mark_last_busy(dev);
>>> ret = pm_runtime_put_autosuspend(dev);
>>> }
>>>
>>>
>>
prev parent reply other threads:[~2015-11-15 11:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-08 4:21 [PATCH] iio: light: apds9960: correct ->last_busy count Matt Ranostay
2015-11-08 15:13 ` Jonathan Cameron
2015-11-08 21:23 ` Matt Ranostay
2015-11-15 11:19 ` 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=56486A5D.6090100@kernel.org \
--to=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=mranostay@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.