From: Jonathan Cameron <jic23@kernel.org>
To: Joshua Crofts <joshua.crofts1@gmail.com>
Cc: "Javier Carrasco" <javier.carrasco.cruz@gmail.com>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Rishi Gupta" <gupt21@gmail.com>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/2] iio: light: veml3328: add support for new device
Date: Mon, 1 Jun 2026 10:17:26 +0100 [thread overview]
Message-ID: <20260601101726.203f56cd@jic23-huawei> (raw)
In-Reply-To: <CALoEA-yEA5KcvXqZCCg76qFAgyNq8BQ5+gop442mju-9PiKaxg@mail.gmail.com>
On Sun, 31 May 2026 18:44:43 +0200
Joshua Crofts <joshua.crofts1@gmail.com> wrote:
> On Sun, 31 May 2026 at 11:19, Jonathan Cameron <jic23@kernel.org> wrote:
> > > + pm_runtime_set_active(dev);
> > > + pm_runtime_set_autosuspend_delay(dev, 2000);
> > > + pm_runtime_use_autosuspend(dev);
> >
> > As per other thread check this results in power down.
> > If it doesn't, try moving autosupend calls after devm_pm_runtime_enable()
> > and see if that is enough. Otherwise, you can either manipulate the counters
> > or I think just call pm_runtime_idle() to force it off immediately.
>
> Just to confirm, I've tested this on the actual hardware and it did autosuspend
> after probe, so I'm going to say that Sashiko is a bit off for once.
If you have time to figure out the path that causes that, it would be excellent
to have it recorded. I spent a few minutes the other day on this and couldn't
find it. Maybe ask AI to figure it out :)
J
>
next prev parent reply other threads:[~2026-06-01 9:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-30 17:06 [PATCH v3 0/2] iio: light: veml3328: add support for new sensor Joshua Crofts
2026-05-30 17:06 ` [PATCH v3 1/2] dt-bindings: iio: light: veml6030: add veml3328 Joshua Crofts
2026-05-30 17:06 ` [PATCH v3 2/2] iio: light: veml3328: add support for new device Joshua Crofts
2026-05-30 17:23 ` Joshua Crofts
2026-05-31 9:04 ` Jonathan Cameron
2026-05-31 9:19 ` Jonathan Cameron
2026-05-31 10:48 ` Joshua Crofts
2026-05-31 16:44 ` Joshua Crofts
2026-06-01 9:17 ` Jonathan Cameron [this message]
2026-06-01 14:43 ` Joshua Crofts
2026-06-02 8:14 ` Joshua Crofts
2026-06-02 12:18 ` 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=20260601101726.203f56cd@jic23-huawei \
--to=jic23@kernel.org \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=gupt21@gmail.com \
--cc=javier.carrasco.cruz@gmail.com \
--cc=joshua.crofts1@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=robh@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