From: Jonathan Cameron <jic23@kernel.org>
To: Linus Walleij <linus.walleij@linaro.org>, linux-iio@vger.kernel.org
Cc: Lars-Peter Clausen <lars@metafoo.de>,
Gregor Boirie <gregor.boirie@parrot.com>,
Richard Leitner <dev@g0hl1n.net>,
Krzysztof Kozlowski <k.kozlowski@samsung.com>,
Gwendal Grignou <gwendal@chromium.org>,
Mark Brown <broonie@kernel.org>
Subject: Re: [PATCH 1/6 v2] iio: magn: ak8975: fix regulator usage
Date: Sun, 26 Jun 2016 15:04:19 +0100 [thread overview]
Message-ID: <21204448-2cb6-3a67-1877-095d8f5d2b2d@kernel.org> (raw)
In-Reply-To: <15061ebe-0401-fb55-73a5-a95e74225d02@kernel.org>
On 26/06/16 15:01, Jonathan Cameron wrote:
> On 24/06/16 10:11, Linus Walleij wrote:
>> IS_ERR_OR_NULL() should never be used with regulators because
>> a NULL pointer may be a perfectly valid dummy regulator
>>
>> We should always succeed to fetch and enable a regulator, but
>> it may be a dummy. That is fine, so bail out for any real
>> errors or probe deferrals
>>
>> Include the error code in the warning print so we know what
>> kind of problem we're dealing with (for example it is nice to
>> see if it is a probe deferral).
>>
>> As we will bail out of probe if the regulator is erroneous,
>> just issue regulator_disable() on the poweroff path: it will
>> succeed.
>>
>> Cc: Mark Brown <broonie@kernel.org>
>> Cc: Lars-Peter Clausen Lars-Peter Clausen <lars@metafoo.de>
>> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> Umm. Linus - something went wrong here... See below...
Pah, I decided the fixup was obvious and have applied this to the
togreg branch of iio.git. Usual pushed out as testing etc etc.
Jonathan
>> ---
>> ChangeLog v1->v2:
>> - No changes
>> ---
>> drivers/iio/magnetometer/ak8975.c | 22 ++--------------------
>> 1 file changed, 2 insertions(+), 20 deletions(-)
>>
>> diff --git a/drivers/iio/magnetometer/ak8975.c b/drivers/iio/magnetometer/ak8975.c
>> index e0e43f497f40..05e9d5041e7a 100644
>> --- a/drivers/iio/magnetometer/ak8975.c
>> +++ b/drivers/iio/magnetometer/ak8975.c
>> @@ -390,10 +390,8 @@ static int ak8975_power_on(struct i2c_client *client)
>> int ret;
>>
>> data->vdd = devm_regulator_get(&client->dev, "vdd");
>> - if (IS_ERR_OR_NULL(data->vdd)) {
>> + if (IS_ERR(data->vdd)) {
>> ret = PTR_ERR(data->vdd);
>> - if (ret == -ENODEV)
>> - ret = 0;
>> } else {
>> ret = regulator_enable(data->vdd);
>> }
>> @@ -402,21 +400,6 @@ static int ak8975_power_on(struct i2c_client *client)
>> "Failed to enable specified Vdd supply\n");
>> return ret;
>> }
>
> Where did the next block come from? You introduce one of these in
> the following patch, but there isn't one currently in the driver.
>> -
>> - data->vid = devm_regulator_get(&client->dev, "vid");
>> - if (IS_ERR_OR_NULL(data->vid)) {
>> - ret = PTR_ERR(data->vdd);
>> - if (ret == -ENODEV)
>> - ret = 0;
>> - } else {
>> - ret = regulator_enable(data->vdd);
>> - }
>> - if (ret) {
>> - dev_warn(&client->dev,
>> - "Failed to enable specified Vid supply\n");
>> - return ret;
>> - }
>> - return 0;
>> }
>>
>> /* Disable attached power regulator if any. */
>> @@ -425,8 +408,7 @@ static void ak8975_power_off(const struct i2c_client *client)
>> const struct iio_dev *indio_dev = i2c_get_clientdata(client);
>> const struct ak8975_data *data = iio_priv(indio_dev);
>>
>> - if (!IS_ERR_OR_NULL(data->vdd))
>> - regulator_disable(data->vdd);
>> + regulator_disable(data->vdd);
>> }
>>
>> /*
>>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-iio" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2016-06-26 14:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-24 9:11 [PATCH 0/6 v2] Fix regulators and PM for AK8975 Linus Walleij
2016-06-24 9:11 ` [PATCH 1/6 v2] iio: magn: ak8975: fix regulator usage Linus Walleij
2016-06-26 14:01 ` Jonathan Cameron
2016-06-26 14:04 ` Jonathan Cameron [this message]
2016-06-26 14:17 ` Jonathan Cameron
2016-06-24 9:11 ` [PATCH 2/6 v2] iio: magn: ak8975: add Vid regulator Linus Walleij
2016-06-26 14:09 ` Jonathan Cameron
2016-06-24 9:11 ` [PATCH 3/6 v2] iio: magn: ak8975: refactor regulator handlers Linus Walleij
2016-06-24 9:11 ` [PATCH 4/6 v2] iio: magn: ak8975: allow a delay after enabling regulators Linus Walleij
2016-06-24 9:11 ` [PATCH 5/6 v2] iio: magn: ak8975: make sure to power down at remove() Linus Walleij
2016-06-24 9:11 ` [PATCH 6/6 v2] iio: magn: ak8975: deploy runtime and system PM Linus Walleij
2016-06-26 14:20 ` 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=21204448-2cb6-3a67-1877-095d8f5d2b2d@kernel.org \
--to=jic23@kernel.org \
--cc=broonie@kernel.org \
--cc=dev@g0hl1n.net \
--cc=gregor.boirie@parrot.com \
--cc=gwendal@chromium.org \
--cc=k.kozlowski@samsung.com \
--cc=lars@metafoo.de \
--cc=linus.walleij@linaro.org \
--cc=linux-iio@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).