From: Jonathan Cameron <jic23@kernel.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Jonathan Bakker <xc-racer2@live.ca>,
Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald <pmeerw@pmeerw.net>,
linux-iio <linux-iio@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] iio: light: gp2ap002: Take runtime PM reference on light read
Date: Sat, 16 May 2020 17:34:35 +0100 [thread overview]
Message-ID: <20200516173435.674019bd@archlinux> (raw)
In-Reply-To: <CACRpkdZ-uuzjbHz9oXwjkTBO5ss1KcBN2Vth6N6h32zmgYhAUA@mail.gmail.com>
On Tue, 12 May 2020 11:03:22 +0200
Linus Walleij <linus.walleij@linaro.org> wrote:
> On Sun, May 10, 2020 at 5:58 PM Jonathan Bakker <xc-racer2@live.ca> wrote:
>
> > The light sensor needs the regulators to be enabled which means
> > the runtime PM needs to be on. This only happened when the
> > proximity part of the chip was enabled.
> >
> > As fallout from this change, only report changes to the prox
> > state in the interrupt handler when it is explicitly enabled.
> >
> > Fixes: 97d642e23037 ("iio: light: Add a driver for Sharp GP2AP002x00F")
> > Signed-off-by: Jonathan Bakker <xc-racer2@live.ca>
>
> Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
>
> Sorry for missing this!
>
> Yours,
> Linus Walleij
Applied to the fixes-togreg branch of iio.git.
Thanks,
Jonathan
prev parent reply other threads:[~2020-05-16 16:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-09 1:42 [PATCH] iio: light: gp2ap002: Take runtime PM reference on light read Jonathan Bakker
2020-05-10 10:20 ` Jonathan Cameron
2020-05-10 15:58 ` [PATCH v2] " Jonathan Bakker
2020-05-12 9:03 ` Linus Walleij
2020-05-16 16:34 ` 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=20200516173435.674019bd@archlinux \
--to=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linus.walleij@linaro.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
--cc=xc-racer2@live.ca \
/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.