From: Lars-Peter Clausen <lars@metafoo.de>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: Hans Verkuil <hans.verkuil@cisco.com>,
Vladimir Barinov <vladimir.barinov@cogentembedded.com>,
linux-media@vger.kernel.org
Subject: Re: [PATCH 7/7] [media] adv7180: Add support for power down
Date: Mon, 10 Mar 2014 16:32:32 +0100 [thread overview]
Message-ID: <531DDB10.4070806@metafoo.de> (raw)
In-Reply-To: <531DDA30.7080306@xs4all.nl>
On 03/10/2014 04:28 PM, Hans Verkuil wrote:
> On 03/10/2014 04:24 PM, Lars-Peter Clausen wrote:
>> On 03/10/2014 03:37 PM, Hans Verkuil wrote:
>> [...]
>>>> +
>>>> +static int adv7180_s_power(struct v4l2_subdev *sd, int on)
>>>> +{
>>>> + struct adv7180_state *state = to_state(sd);
>>>> + struct i2c_client *client = v4l2_get_subdevdata(sd);
>>>> + int ret;
>>>> +
>>>> + ret = mutex_lock_interruptible(&state->mutex);
>>>> + if (ret)
>>>> + return ret;
>>>> +
>>>> + ret = adv7180_set_power(state, client, on);
>>>> + if (ret)
>>>> + goto out;
>>>> +
>>>> + state->powered = on;
>>>> +out:
>>>
>>> I would change this to:
>>>
>>> if (!ret)
>>> state->powered = on;
>>>
>>> and drop the 'goto'.
>>>
>>
>> ok.
>>
>> [...]
>>>> static int adv7180_resume(struct device *dev)
>>>> @@ -656,10 +687,11 @@ static int adv7180_resume(struct device *dev)
>>>> struct adv7180_state *state = to_state(sd);
>>>> int ret;
>>>>
>>>> - ret = i2c_smbus_write_byte_data(client, ADV7180_PWR_MAN_REG,
>>>> - ADV7180_PWR_MAN_ON);
>>>> - if (ret < 0)
>>>> - return ret;
>>>> + if (state->powered) {
>>>> + ret = adv7180_set_power(state, client, true);
>>>> + if (ret)
>>>> + return ret;
>>>> + }
>>>> ret = init_device(client, state);
>>>> if (ret < 0)
>>>> return ret;
>>>>
>>>
>>> What is the initial state of the driver when loaded? Shouldn't probe() set the
>>> 'powered' variable to true initially?
>>
>> Yep, st->powered should be set to true by default.
>>
>> What's your process in general, want me to resend the whole series, or are
>> you going to apply the patches that are ok?
>
> When do you think you can have a fixed version of this patch ready? If it is
> today/tomorrow, then I'll wait for that, otherwise I'll make a pull request
> for the other 6 patches (which look fine).
I already have the updated version of the patch, will send it out soon.
- Lars
prev parent reply other threads:[~2014-03-10 15:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-07 16:14 [PATCH 1/7] [media] adv7180: Fix remove order Lars-Peter Clausen
2014-03-07 16:14 ` [PATCH 2/7] [media] adv7180: Free control handler on remove() Lars-Peter Clausen
2014-03-07 16:14 ` [PATCH 3/7] [media] adv7180: Remove unnecessary v4l2_device_unregister_subdev() from probe error path Lars-Peter Clausen
2014-03-07 16:14 ` [PATCH 4/7] [media] adv7180: Remove duplicated probe error message Lars-Peter Clausen
2014-03-07 16:14 ` [PATCH 5/7] [media] adv7180: Use threaded IRQ instead of IRQ + workqueue Lars-Peter Clausen
2014-03-07 16:14 ` [PATCH 6/7] [media] adv7180: Add support for async device registration Lars-Peter Clausen
2014-03-07 16:14 ` [PATCH 7/7] [media] adv7180: Add support for power down Lars-Peter Clausen
2014-03-10 14:37 ` Hans Verkuil
2014-03-10 15:24 ` Lars-Peter Clausen
2014-03-10 15:28 ` Hans Verkuil
2014-03-10 15:32 ` Lars-Peter Clausen [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=531DDB10.4070806@metafoo.de \
--to=lars@metafoo.de \
--cc=hans.verkuil@cisco.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=vladimir.barinov@cogentembedded.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