public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Zoie Lin <zoie.lin@mediatek.com>
To: Qii Wang <qii.wang@mediatek.com>,
	Andi Shyti <andi.shyti@kernel.org>,
	Matthias Brugger <matthias.bgg@gmail.com>,
	AngeloGioacchino Del Regno
	<angelogioacchino.delregno@collabora.com>
Cc: <linux-i2c@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-mediatek@lists.infradead.org>,
	<Project_Global_Chrome_Upstream_Group@mediatek.com>,
	<teddy.chen@mediatek.com>, Zoie Lin <zoie.lin@mediatek.com>
Subject: [v2,0/1] i2c: mediatek: add runtime PM operations and bus regulator control
Date: Wed, 6 Nov 2024 20:52:11 +0800	[thread overview]
Message-ID: <20241106125212.27362-1-zoie.lin@mediatek.com> (raw)

This series is based on linux-next, tag: next-20241105

Changes in v2:
- author name modification
- replacement of pm runtime API
- removal of redundant error messages
- return value adjustment
- add runtime pm status check

The delay before runtime_put_autosuspend() actually executes 
mtk_i2c_runtime_suspend() depends on the frequency of I2C usage by the 
devices attached to this bus. A 1000ms delay is a balanced value for 
latency and power metrics based on the MTK platform.

Zoie Lin (1):
  i2c: mediatek: add runtime PM operations and bus regulator control

 drivers/i2c/busses/i2c-mt65xx.c | 77 ++++++++++++++++++++++++++++-----
 1 file changed, 65 insertions(+), 12 deletions(-)

-- 
2.45.2


             reply	other threads:[~2024-11-06 12:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-06 12:52 Zoie Lin [this message]
2024-11-06 12:52 ` [v2,1/1] i2c: mediatek: add runtime PM operations and bus regulator control Zoie Lin
2024-11-07 10:13   ` AngeloGioacchino Del Regno
2024-11-07 15:19     ` Zoie Lin (林禹妡)
2024-11-13  8:54       ` AngeloGioacchino Del Regno
2024-11-19 22:08       ` 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=20241106125212.27362-1-zoie.lin@mediatek.com \
    --to=zoie.lin@mediatek.com \
    --cc=Project_Global_Chrome_Upstream_Group@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=qii.wang@mediatek.com \
    --cc=teddy.chen@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