From: Luca Weiss <luca@z3ntu.xyz>
To: Luca Weiss <luca.weiss@fairphone.com>,
~postmarketos/upstreaming@lists.sr.ht
Cc: Markuss Broks <markuss.broks@gmail.com>,
linux-kernel@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht,
phone-devel@vger.kernel.org,
Konrad Dybcio <konrad.dybcio@somainline.org>,
Marijn Suijten <marijn.suijten@somainline.org>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@somainline.org>,
Song Qiang <songqiang1304521@gmail.com>,
Lars-Peter Clausen <lars@metafoo.de>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-msm@vger.kernel.org,
Jonathan Cameron <jic23@kernel.org>
Subject: Re: [PATCH 3/5] proximity: vl53l0x: Handle the VDD regulator
Date: Sun, 12 Jun 2022 11:28:22 +0200 [thread overview]
Message-ID: <13033502.uLZWGnKmhe@g550jk> (raw)
In-Reply-To: <20220612095333.1479464c@jic23-huawei>
Hi Jonathan,
On Sonntag, 12. Juni 2022 10:53:33 CEST Jonathan Cameron wrote:
> On Wed, 08 Jun 2022 12:18:52 +0200
>
> "Luca Weiss" <luca.weiss@fairphone.com> wrote:
> > Hi Markuss,
> >
> > On Mon May 23, 2022 at 7:53 PM CEST, Markuss Broks wrote:
> > > Handle the regulator supplying the VDD pin of VL53L0X.
> > >
> > > Signed-off-by: Markuss Broks <markuss.broks@gmail.com>
> > > ---
> > >
> > > drivers/iio/proximity/vl53l0x-i2c.c | 37 +++++++++++++++++++++++++++++
> > > 1 file changed, 37 insertions(+)
> > >
> > > diff --git a/drivers/iio/proximity/vl53l0x-i2c.c
> > > b/drivers/iio/proximity/vl53l0x-i2c.c index 12a3e2eff464..8581a873919f
> > > 100644
> > > --- a/drivers/iio/proximity/vl53l0x-i2c.c
> > > +++ b/drivers/iio/proximity/vl53l0x-i2c.c
> > > @@ -43,6 +43,7 @@
> > >
> > > struct vl53l0x_data {
> > >
> > > struct i2c_client *client;
> > > struct completion completion;
> > >
> > > + struct regulator *vdd_supply;
> > >
> > > };
> > >
> > > static irqreturn_t vl53l0x_handle_irq(int irq, void *priv)
> > >
> > > @@ -192,10 +193,31 @@ static const struct iio_info vl53l0x_info = {
> > >
> > > .read_raw = vl53l0x_read_raw,
> > >
> > > };
> > >
> > > +static void vl53l0x_power_off(void *_data)
> > > +{
> > > + struct vl53l0x_data *data = _data;
> > > +
> > > + regulator_disable(data->vdd_supply);
> > > +}
> > > +
> > > +static int vl53l0x_power_on(struct vl53l0x_data *data)
> > > +{
> > > + int ret;
> > > +
> > > + ret = regulator_enable(data->vdd_supply);
> > > + if (ret)
> > > + return ret;
> > > +
> > > + usleep_range(3200, 5000);
> > > +
> > > + return 0;
> > > +}
> > > +
> > >
> > > static int vl53l0x_probe(struct i2c_client *client)
> > > {
> > >
> > > struct vl53l0x_data *data;
> > > struct iio_dev *indio_dev;
> > >
> > > + int error;
> > >
> > > indio_dev = devm_iio_device_alloc(&client->dev, sizeof(*data));
> > > if (!indio_dev)
> > >
> > > @@ -210,6 +232,21 @@ static int vl53l0x_probe(struct i2c_client *client)
> > >
> > > I2C_FUNC_SMBUS_BYTE_DATA))
> > >
> > > return -EOPNOTSUPP;
> > >
> > > + data->vdd_supply = devm_regulator_get_optional(&client->dev,
"vdd");
> > > + if (IS_ERR(data->vdd_supply))
> > > + return dev_err_probe(&client->dev, PTR_ERR(data-
>vdd_supply),
> > > + "Unable to get VDD
regulator\n");
> >
> > It looks like this optional regulator is not actually optional.
> >
> > [ 1.919995] vl53l0x-i2c 1-0029: error -ENODEV: Unable to get VDD
> > regulator
> >
> > When using devm_regulator_get instead, a dummy regulator gets returned
> > which I think is what we want here:
> >
> > [ 1.905518] vl53l0x-i2c 1-0029: supply vdd not found, using dummy
> > regulator
> >
> > Can you fix this up or should I send a patch?
>
> Hi Luca,
>
> Please send a patch.
Which commit sha can I use for Fixes: here?
Based your togreg[0] branch currently shows "Age: 20 hours" I guess it was
rebased recently?
Regards
Luca
[0]https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git/log/?h=togreg
>
> Jonathan
>
> > Regards
> > Luca
> >
> > > +
> > > + error = vl53l0x_power_on(data);
> > > + if (error)
> > > + return dev_err_probe(&client->dev, error,
> > > + "Failed to power on the
chip\n");
> > > +
> > > + error = devm_add_action_or_reset(&client->dev, vl53l0x_power_off,
> > > data);
> > > + if (error)
> > > + return dev_err_probe(&client->dev, error,
> > > + "Failed to install poweroff
action\n");
> > > +
> > >
> > > indio_dev->name = "vl53l0x";
> > > indio_dev->info = &vl53l0x_info;
> > > indio_dev->channels = vl53l0x_channels;
next prev parent reply other threads:[~2022-06-12 9:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-23 17:53 [PATCH v5 0/5] Add support for ToF sensor on Yoshino platform Markuss Broks
2022-05-23 17:53 ` [PATCH 1/5] dt-bindings: proximity: vl53l0x: Document optional supply and GPIO properties Markuss Broks
2022-05-23 17:53 ` [PATCH 2/5] proximity: vl53l0x: Prefer pre-initialized interrupt flags Markuss Broks
2022-05-23 17:53 ` [PATCH 3/5] proximity: vl53l0x: Handle the VDD regulator Markuss Broks
2022-06-08 10:18 ` Luca Weiss
2022-06-12 8:53 ` Jonathan Cameron
2022-06-12 9:28 ` Luca Weiss [this message]
2022-06-14 10:48 ` Jonathan Cameron
2022-06-14 10:58 ` Jonathan Cameron
2022-05-23 17:53 ` [PATCH 4/5] proximity: vl53l0x: Handle the reset GPIO Markuss Broks
2022-05-23 17:53 ` [PATCH 5/5] arm64: dts: qcom: msm8998-xperia: Introduce ToF sensor support Markuss Broks
2022-07-03 3:56 ` (subset) " Bjorn Andersson
2022-06-03 15:23 ` [PATCH v5 0/5] Add support for ToF sensor on Yoshino platform Jonathan Cameron
-- strict thread matches above, loose matches on Subject: below --
2022-05-10 20:42 [PATCH " Markuss Broks
2022-05-10 20:42 ` [PATCH 3/5] proximity: vl53l0x: Handle the VDD regulator Markuss Broks
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=13033502.uLZWGnKmhe@g550jk \
--to=luca@z3ntu.xyz \
--cc=agross@kernel.org \
--cc=angelogioacchino.delregno@somainline.org \
--cc=bjorn.andersson@linaro.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=konrad.dybcio@somainline.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.weiss@fairphone.com \
--cc=marijn.suijten@somainline.org \
--cc=markuss.broks@gmail.com \
--cc=phone-devel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=songqiang1304521@gmail.com \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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).