From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Val Packett <val@packett.cool>
Cc: "André Apitzsch" <git@apitzsch.eu>,
"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: Wed, 17 Sep 2025 13:10:02 +0300 [thread overview]
Message-ID: <aMqI-lElZsWV-Hrl@kekkonen.localdomain> (raw)
In-Reply-To: <fad5cb33-0e7c-499b-bad7-bbdacca8076a@packett.cool>
Hi André, Val,
On Tue, Sep 16, 2025 at 05:08:44PM -0300, Val Packett wrote:
>
> On 9/15/25 5:48 PM, André Apitzsch wrote:
> > 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:
> > > > 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.
>
> I haven't had access to the datasheet for the DW9718S, so this was all
> deduced experimentally. By "to be sure" I meant that I literally raised the
> timeout "just in case", not based on actual issues.
>
> The actually important change was expecting the failure on the write and not
> erroring out.
Ack.
André: could you add this information to the comment as well?
--
Kind regards,
Sakari Ailus
next prev parent reply other threads:[~2025-09-17 10:10 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
2025-09-16 20:08 ` Val Packett
2025-09-17 10:10 ` Sakari Ailus [this message]
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=aMqI-lElZsWV-Hrl@kekkonen.localdomain \
--to=sakari.ailus@linux.intel.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=djrscally@gmail.com \
--cc=git@apitzsch.eu \
--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=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