From: "André Apitzsch" <git@apitzsch.eu>
To: Sakari Ailus <sakari.ailus@linux.intel.com>,
Val Packett <val@packett.cool>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org, Daniel Scally <djrscally@gmail.com>,
~postmarketos/upstreaming@lists.sr.ht,
phone-devel@vger.kernel.org, linux-media@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 7/7] media: i2c: dw9719: Fix power on/off sequence
Date: Mon, 15 Sep 2025 22:48:23 +0200 [thread overview]
Message-ID: <550f28a9aa82a28beb35fd3490dbe08928ba9eed.camel@apitzsch.eu> (raw)
In-Reply-To: <aKLZ39IzI_azrDIu@kekkonen.localdomain>
Hi Sakari,
@Val, please see below.
Am Montag, dem 18.08.2025 um 07:44 +0000 schrieb Sakari Ailus:
> Hi André,
>
> On Sun, Aug 17, 2025 at 07:09:26PM +0200, André Apitzsch via B4 Relay
> wrote:
> > From: Val Packett <val@packett.cool>
> >
> > The "jiggle" code was not actually expecting failure, which it
> > should because that's what actually happens when the device wasn't
> > already woken up by the regulator power-on (i.e. in the case of a
> > shared regulator).
> >
> > Also, do actually enter the internal suspend mode on shutdown, to
> > save power in the case of a shared regulator.
> >
> > Also, wait a bit longer (2x tOPR) on waking up, 1x is not enough at
> > least on the DW9718S as found on the motorola-nora smartphone.
> >
> > Signed-off-by: Val Packett <val@packett.cool>
> > Signed-off-by: André Apitzsch <git@apitzsch.eu>
> > ---
> > drivers/media/i2c/dw9719.c | 23 ++++++++++++++++-------
> > 1 file changed, 16 insertions(+), 7 deletions(-)
> >
> > diff --git a/drivers/media/i2c/dw9719.c
> > b/drivers/media/i2c/dw9719.c
> > index
> > 63c7fd4ab70a0e02518252b23b89c45df4ba273d..dd28a0223d6ac980084b1f661
> > bd029ea6b0be503 100644
> > --- a/drivers/media/i2c/dw9719.c
> > +++ b/drivers/media/i2c/dw9719.c
> > @@ -95,12 +95,19 @@ struct dw9719_device {
> >
> > static int dw9719_power_down(struct dw9719_device *dw9719)
> > {
> > + u32 reg_pwr = (dw9719->model == DW9718S) ? DW9718S_PD :
> > DW9719_CONTROL;
>
> Extra parentheses.
>
> > +
> > + /*
> > + * Worth engaging the internal SHUTDOWN mode especially
> > due to the
> > + * regulator being potentially shared with other devices.
> > + */
> > + cci_write(dw9719->regmap, reg_pwr, DW9719_SHUTDOWN, NULL);
>
> I'd still complain if this fails as we don't return the error.
>
> > return regulator_disable(dw9719->regulator);
> > }
> >
> > static int dw9719_power_up(struct dw9719_device *dw9719, bool
> > detect)
> > {
> > - u32 reg_pwr;
> > + u32 reg_pwr = (dw9719->model == DW9718S) ? DW9718S_PD :
> > DW9719_CONTROL;
>
> Extra parentheses.
>
> > u64 val;
> > int ret;
> > int err;
> > @@ -109,13 +116,15 @@ static int dw9719_power_up(struct
> > dw9719_device *dw9719, bool detect)
> > if (ret)
> > return ret;
> >
> > - /* Jiggle SCL pin to wake up device */
> > - reg_pwr = (dw9719->model == DW9718S) ? DW9718S_PD :
> > DW9719_CONTROL;
> > - cci_write(dw9719->regmap, reg_pwr, DW9719_SHUTDOWN, &ret);
> > - fsleep(100);
> > + /*
> > + * Need 100us to transition from SHUTDOWN to STANDBY.
> > + * Jiggle the SCL pin to wake up the device (even when the
> > regulator
> > + * is shared) and wait double the time to be sure, then
> > retry the write.
>
> Why double? Isn't the datasheet correct when it comes to the power-on
> sequence?
>
I haven't noticed any problems during power-up of DW9761. However,
according to the commit message, there seems be an issue with DW9718S.
But I don't own the device and cannot test it.
Maybe Val can provided some additional information.
Best regards,
André
> > + */
> > + cci_write(dw9719->regmap, reg_pwr, DW9719_STANDBY, &ret);
> > + ret = 0; /* the jiggle is expected to fail, don't even log
> > that as error */
> > + fsleep(200);
> > cci_write(dw9719->regmap, reg_pwr, DW9719_STANDBY, &ret);
>
> Just pass NULL instead of ret as we don't check the value and the ret
> assignment above becomes redundant. Please spare the comment though.
>
> > - /* Need 100us to transit from SHUTDOWN to STANDBY */
> > - fsleep(100);
> >
> > if (detect) {
> > /* This model does not have an INFO register */
> >
next prev parent reply other threads:[~2025-09-15 21:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-17 17:09 [PATCH 0/7] media: i2c: dw9719: add DT compatible and DW9718S support André Apitzsch via B4 Relay
2025-08-17 17:09 ` [PATCH 1/7] dt-bindings: media: i2c: Add DW9718S, DW9719 and DW9761 VCM André Apitzsch via B4 Relay
2025-08-20 21:56 ` Rob Herring
2025-08-26 11:57 ` André Apitzsch
2025-08-17 17:09 ` [PATCH 2/7] media: i2c: dw9719: Deprecate dongwoon,vcm-freq André Apitzsch via B4 Relay
2025-08-17 17:09 ` [PATCH 3/7] media: i2c: dw9719: Add driver_data matching André Apitzsch via B4 Relay
2025-08-17 20:28 ` kernel test robot
2025-08-18 7:38 ` Sakari Ailus
2025-08-17 17:09 ` [PATCH 4/7] media: i2c: dw9719: Add DW9718S support André Apitzsch via B4 Relay
2025-08-17 17:09 ` [PATCH 5/7] media: i2c: dw9719: Update PM last busy time upon close André Apitzsch via B4 Relay
2025-08-18 7:37 ` Sakari Ailus
2025-08-17 17:09 ` [PATCH 6/7] media: i2c: dw9719: Add an of_match_table André Apitzsch via B4 Relay
2025-08-17 17:09 ` [PATCH 7/7] media: i2c: dw9719: Fix power on/off sequence André Apitzsch via B4 Relay
2025-08-18 7:44 ` Sakari Ailus
2025-09-15 20:48 ` André Apitzsch [this message]
2025-09-16 20:08 ` Val Packett
2025-09-17 10:10 ` Sakari Ailus
2025-09-18 21:31 ` André Apitzsch
2025-09-19 6:18 ` Sakari Ailus
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=550f28a9aa82a28beb35fd3490dbe08928ba9eed.camel@apitzsch.eu \
--to=git@apitzsch.eu \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=djrscally@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=phone-devel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=val@packett.cool \
--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