From: Jonathan Cameron <jic23@kernel.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Stephan Gerhold <stephan@gerhold.net>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
Rob Herring <robh+dt@kernel.org>,
linux-iio <linux-iio@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
"H . Nikolaus Schaller" <hns@goldelico.com>
Subject: Re: [PATCH v2 2/2] iio: gyro: bmg160: Add rudimentary regulator support
Date: Tue, 29 Dec 2020 18:30:26 +0000 [thread overview]
Message-ID: <20201229183026.7e5a1d4f@archlinux> (raw)
In-Reply-To: <CACRpkdbEqN95-bYHjo7JEbSrGx9qHNoeW2wHC6KPvwn0sG7isg@mail.gmail.com>
On Mon, 14 Dec 2020 09:57:06 +0100
Linus Walleij <linus.walleij@linaro.org> wrote:
> On Fri, Dec 11, 2020 at 7:39 PM Stephan Gerhold <stephan@gerhold.net> wrote:
>
> > BMG160 needs VDD and VDDIO regulators that might need to be explicitly
> > enabled. Add some rudimentary support to obtain and enable these
> > regulators during probe() and disable them using a devm action.
> >
> > Signed-off-by: Stephan Gerhold <stephan@gerhold.net>
> > ---
> > Changes in v2:
> > - Do regulator_bulk_enable() immediately after devm_regulator_bulk_get()
> > - Simplify error handling using devm_add_action_or_reset()
>
> Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
Series applied,
Thanks,
Jonathan
>
> Yours,
> Linus Walleij
prev parent reply other threads:[~2020-12-29 18:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-11 18:38 [PATCH v2 1/2] dt-bindings: iio: gyroscope: bmg160: Document regulator supplies Stephan Gerhold
2020-12-11 18:38 ` [PATCH v2 2/2] iio: gyro: bmg160: Add rudimentary regulator support Stephan Gerhold
2020-12-13 13:03 ` Jonathan Cameron
2020-12-14 8:57 ` Linus Walleij
2020-12-29 18:30 ` 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=20201229183026.7e5a1d4f@archlinux \
--to=jic23@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hns@goldelico.com \
--cc=lars@metafoo.de \
--cc=linus.walleij@linaro.org \
--cc=linux-iio@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
--cc=robh+dt@kernel.org \
--cc=stephan@gerhold.net \
/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.