From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Zhi Mao <zhi.mao@mediatek.com>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, shengnan.wang@mediatek.com,
yaya.chang@mediatek.com, teddy.chen@mediatek.com,
yunkec@chromium.org, 10572168@qq.com
Subject: Re: [PATCH] media: i2c: improve suspend/resume switch performance for GT9769 VCM driver
Date: Wed, 28 Aug 2024 07:51:16 +0000 [thread overview]
Message-ID: <Zs7W9PDY2ny5JI8w@kekkonen.localdomain> (raw)
In-Reply-To: <20240817073452.21627-1-zhi.mao@mediatek.com>
Hi Zhi,
Thanks for the patch.
On Sat, Aug 17, 2024 at 03:34:02PM +0800, Zhi Mao wrote:
> GT9769 VCM power-on default setting is PD=0,
> so it is not necessary to set again in dw9768_init function,
> and it also has no requirement of setting PD=1
> before power-off in dw9768_release function.
> For GT9769 VCM, PD mode control will add extra time
> when switching between suspend and resume.
> e.g. chrome camera AP can switch between video and photo mode,
> the behavior corresponding to VCM is suspend and resume,
> it will cause camera preview is not smooth.
If this is the problem, wouldn't either of these two be a better option:
- keep the file handle open in the user space, to avoid powering off the
VCM or
- add autosuspend support to the driver.
I also wouldn't differentiate driver behaviour between the chips. If the
hardware default really is different (is it, this is rare for
register-compatible parts), then the driver needs to reprogram it (at least
on the one with a different default).
--
Kind regards,
Sakari Ailus
next prev parent reply other threads:[~2024-08-28 7:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-17 7:34 Zhi Mao
2024-08-28 7:51 ` Sakari Ailus [this message]
2024-08-31 5:59 ` Zhi Mao (毛智)
2024-08-31 5:52 Zhi Mao
2024-09-19 8:10 ` Zhi Mao (毛智)
2024-09-23 9:07 ` Fei Shao
2024-10-12 3:34 ` Zhi Mao (毛智)
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=Zs7W9PDY2ny5JI8w@kekkonen.localdomain \
--to=sakari.ailus@linux.intel.com \
--cc=10572168@qq.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=mchehab@kernel.org \
--cc=shengnan.wang@mediatek.com \
--cc=teddy.chen@mediatek.com \
--cc=yaya.chang@mediatek.com \
--cc=yunkec@chromium.org \
--cc=zhi.mao@mediatek.com \
/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
all inboxes | Powered by JetHome®