From: "Zoie Lin (林禹妡)" <Zoie.Lin@mediatek.com>
To: "Qii Wang (王琪)" <Qii.Wang@mediatek.com>,
"AngeloGioacchino Del Regno"
<angelogioacchino.delregno@collabora.com>,
"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
"andi.shyti@kernel.org" <andi.shyti@kernel.org>
Cc: "Teddy Chen (陳乾元)" <Teddy.Chen@mediatek.com>,
Project_Global_Chrome_Upstream_Group
<Project_Global_Chrome_Upstream_Group@mediatek.com>,
"Shunchang Wang (王舜昌)" <ot_shunchang.wang@mediatek.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"Joseph-CC Chang (張欽洲)" <Joseph-CC.Chang@mediatek.com>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
"Leilk Liu (刘磊)" <Leilk.Liu@mediatek.com>
Subject: Re: [PATCH v4 0/1] i2c: mediatek: add runtime PM operations and bus regulator control
Date: Tue, 4 Mar 2025 08:37:27 +0000 [thread overview]
Message-ID: <ec77bb9478cd86a6737b92135170064970925b3c.camel@mediatek.com> (raw)
In-Reply-To: <46621db1-6096-46af-b021-c919c1cae7ef@collabora.com>
Hi Angelo,
Thank you for your suggestions regarding the autosuspend delay.
We understand the importance of balancing power efficiency and
responsiveness. Given the diversity of I2C devices connected
under each platform, it is indeed challenging to estimate an
appropriate delay time for testing.
Therefore, we would like to proceed with your initial suggestion
and set the autosuspend delay to 250ms. Based on our preliminary
tests, this adjustment appears to be a practical solution across
our existing platforms.
Thank you.
Best regards,
Zoie
On Thu, 2025-02-13 at 12:57 +0100, AngeloGioacchino Del Regno wrote:
>
>
> Turning on and off regulators at start of transfer and end of
> transfer respectively
> is very expensive and, while it makes sense for power efficiency of
> the controller,
> it doesn't make sense for:
>
> 1. Responsiveness (latency); and
> 2. Platform power efficiency at a whole.
>
> As a start, just set the autosuspend delay to 250ms; this gives you
> at least time
> to bring up clocks and regulators and usually finish a transfer at
> 400KHz, giving
> you the chance to also get some more requests before autosuspend
> decides to, well,
> auto..suspend the device.
>
> The right way of choosing an autosuspend delay a bit more precisely,
> though, for
> this device, would be to check the bus speed and calculate the
> autosuspend time
> accordingly.
>
> Cheers,
> Angelo
>
>
>
next prev parent reply other threads:[~2025-03-04 8:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-11 14:39 [PATCH v4 0/1] i2c: mediatek: add runtime PM operations and bus regulator control Zoie Lin
2025-02-12 18:37 ` Andi Shyti
2025-02-13 11:57 ` AngeloGioacchino Del Regno
2025-03-04 8:37 ` Zoie Lin (林禹妡) [this message]
2025-03-11 23:16 ` Andi Shyti
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=ec77bb9478cd86a6737b92135170064970925b3c.camel@mediatek.com \
--to=zoie.lin@mediatek.com \
--cc=Joseph-CC.Chang@mediatek.com \
--cc=Leilk.Liu@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=Qii.Wang@mediatek.com \
--cc=Teddy.Chen@mediatek.com \
--cc=andi.shyti@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=ot_shunchang.wang@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