From: "Zhi Mao (毛智)" <zhi.mao@mediatek.com>
To: "fshao@chromium.org" <fshao@chromium.org>
Cc: "linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"yunkec@chromium.org" <yunkec@chromium.org>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
"Shengnan Wang (王圣男)" <shengnan.wang@mediatek.com>,
"mchehab@kernel.org" <mchehab@kernel.org>,
"Yaya Chang (張雅清)" <Yaya.Chang@mediatek.com>,
"sakari.ailus@linux.intel.com" <sakari.ailus@linux.intel.com>,
"10572168@qq.com" <10572168@qq.com>,
"Teddy Chen (陳乾元)" <Teddy.Chen@mediatek.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"Xiaofeiw Wang (王小飞)" <ot_xiaofeiw.wang@mediatek.com>,
"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
"AngeloGioacchino Del Regno"
<angelogioacchino.delregno@collabora.com>
Subject: Re: [PATCH] media: i2c: improve suspend/resume switch performance for GT9769 VCM driver
Date: Sat, 12 Oct 2024 03:34:45 +0000 [thread overview]
Message-ID: <f7fd295b116be6f590350a4733a299676d759f88.camel@mediatek.com> (raw)
In-Reply-To: <CAC=S1nh76iKhMV4roBe4mLTrq-eHqz-3-fYWzNcWAETvj-JETA@mail.gmail.com>
Hi Fei,
Thanks for your review.
On Mon, 2024-09-23 at 17:07 +0800, Fei Shao wrote:
>
> External email : Please do not click links or open attachments until
> you have verified the sender or the content.
> Hi Zhi,
>
> On Sat, Aug 31, 2024 at 1:54 PM Zhi Mao <zhi.mao@mediatek.com> wrote:
>
> Suggestion for the new patch title:
> media: i2c: dw9768: Use runtime PM autosuspend
>
> to better describe "what" this patch does to the DW9768 driver, not
> "why".
> Also there's nothing to do with GT9769 in this patch.
>
> >
> > Chromebook 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 during switching
> operation.
> > We use autosuspend function can fix this issue.
> >
> > Signed-off-by: Zhi Mao <zhi.mao@mediatek.com>
> > ---
> > drivers/media/i2c/dw9768.c | 3 ++-
> > 1 file changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/media/i2c/dw9768.c
> b/drivers/media/i2c/dw9768.c
> > index 18ef2b35c9aa..7449d29df901 100644
> > --- a/drivers/media/i2c/dw9768.c
> > +++ b/drivers/media/i2c/dw9768.c
> > @@ -374,7 +374,7 @@ static int dw9768_open(struct v4l2_subdev *sd,
> struct v4l2_subdev_fh *fh)
> >
> > static int dw9768_close(struct v4l2_subdev *sd, struct
> v4l2_subdev_fh *fh)
> > {
> > - pm_runtime_put(sd->dev);
>
> Call pm_runtime_mark_last_busy() to update the power.last_busy field
> for autosuspend to work properly.
>
> > + pm_runtime_put_sync_autosuspend(sd->dev);
>
> Use pm_runtime_put_autosuspend().
> Don't switch to the synchronized variant without reasons.
>
> >
> > return 0;
> > }
> > @@ -490,6 +490,7 @@ static int dw9768_probe(struct i2c_client
> *client)
> > goto err_power_off;
> > }
> >
> > + pm_runtime_use_autosuspend(dev);
>
> Add pm_runtime_set_autosuspend_delay() before calling
> pm_runtime_use_autosuspend() to avoid rapid power state bouncing.
>
I have fixed these suggestion above.
please review patch:
https://lore.kernel.org/all/20241012032805.23545-1-zhi.mao@mediatek.com/
> Regards,
> Fei
>
>
>
> > pm_runtime_idle(dev);
> >
> > return 0;
> > --
> > 2.46.0
> >
> >
next prev parent reply other threads:[~2024-10-12 3:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
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 (毛智) [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-08-17 7:34 Zhi Mao
2024-08-28 7:51 ` Sakari Ailus
2024-08-31 5:59 ` 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=f7fd295b116be6f590350a4733a299676d759f88.camel@mediatek.com \
--to=zhi.mao@mediatek.com \
--cc=10572168@qq.com \
--cc=Teddy.Chen@mediatek.com \
--cc=Yaya.Chang@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=fshao@chromium.org \
--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=ot_xiaofeiw.wang@mediatek.com \
--cc=sakari.ailus@linux.intel.com \
--cc=shengnan.wang@mediatek.com \
--cc=yunkec@chromium.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
all inboxes | Powered by JetHome®