mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jason-JH Lin (林睿祥)" <Jason-JH.Lin@mediatek.com>
To: "jassisinghbrar@gmail.com" <jassisinghbrar@gmail.com>,
	"angelogioacchino.delregno@collabora.com" 
	<angelogioacchino.delregno@collabora.com>,
	"chunkuang.hu@kernel.org" <chunkuang.hu@kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-mediatek@lists.infradead.org"
	<linux-mediatek@lists.infradead.org>,
	"Singo Chang (張興國)" <Singo.Chang@mediatek.com>,
	"Johnson Wang (王聖鑫)" <Johnson.Wang@mediatek.com>,
	"Jason-ch Chen (陳建豪)" <Jason-ch.Chen@mediatek.com>,
	"Shawn Sung (宋孝謙)" <Shawn.Sung@mediatek.com>,
	"Nancy Lin (林欣螢)" <Nancy.Lin@mediatek.com>,
	Project_Global_Chrome_Upstream_Group
	<Project_Global_Chrome_Upstream_Group@mediatek.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>
Subject: Re: [PATCH v2] mailbox: remove runtime GCE clk control
Date: Fri, 6 Oct 2023 09:15:58 +0000	[thread overview]
Message-ID: <672d86a9e9bb08c770a6884860e9d13a0aaf0eb7.camel@mediatek.com> (raw)
In-Reply-To: <baa122da-4ae3-9023-3529-3ad38204b989@collabora.com>

Hi Angelo,

Thanks for the reviews.

On Wed, 2023-10-04 at 11:20 +0200, AngeloGioacchino Del Regno wrote:
> Il 04/10/23 10:54, Jason-JH.Lin ha scritto:
> > 1. GCE is a frequently used module, so runtime controlling
> > GCE clock won't save too much power and its original design
> > doesn't expect it to be enabled and disabled too frequently.
> > 
> > 2. Runtime controlling GCE clock will cause display HW register
> > configured in worng stream done event issue below:
> >    GCE should config HW in every vblanking duration.
> >    The stream done event is the start signal of vblanking.
> > 
> >    If stream done event is sent between GCE clk_disable
> >    and clk_enable. After GCE clk_enable the stream done event
> >    may not appear immediately and have about 3us delay.
> > 
> >    Normal case:
> >    clk_disable -> get EventA -> clk_enable -> clear EventA
> >    -> wait EventB -> get EventB -> config HW
> > 
> >    Abnormal case:
> >    clk_disable -> get EventA -> clk_enable -> EventA delay appear
> >    -> clear EventA fail -> wait EventB but get EventA -> config HW
> > 
> > So just remove the runtime GCE clock contorl.
> > 
> > Signed-off-by: Jason-JH.Lin <jason-jh.lin@mediatek.com>
> 
> Instead of entirely removing the logic that controls the clocks and
> always
> refuse to save power, what about using autosuspend?
> 
> If the two cases that you're describing are happening always in a
> range of
> time, we could *yes* remove the "manual" bulk disable/enable calls,
> but then
> we could use runtime_suspend/runtime_resume callbacks for that.
> 
> Hint: pm_runtime_set_autosuspend_delay(dev, 1000);
> 
> Regards,
> Angelo
> 

These 2 issues are caused by GCE bulk_clk enable/disable too
frequently.

As I now, pm_runtime_set_autosuspend_delay() is for controlling the
power domain. The power domain of GCE is infrasys which can only be
enabled/disabled by spm during the whole system resume/suspend.
So I'm not sure about how can pm_runtime_set_autosuspend_delay() save 
power for GCE bulk_clk in this case.

Could you give more hint for me please?

Regards,
Jason-JH.Lin


  reply	other threads:[~2023-10-06  9:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20231004085430.19538-1-jason-jh.lin@mediatek.com>
2023-10-04  9:20 ` AngeloGioacchino Del Regno
2023-10-06  9:15   ` Jason-JH Lin (林睿祥) [this message]
2023-10-10 11:52     ` AngeloGioacchino Del Regno
2023-10-11  3:03       ` Jason-JH Lin (林睿祥)

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=672d86a9e9bb08c770a6884860e9d13a0aaf0eb7.camel@mediatek.com \
    --to=jason-jh.lin@mediatek.com \
    --cc=Jason-ch.Chen@mediatek.com \
    --cc=Johnson.Wang@mediatek.com \
    --cc=Nancy.Lin@mediatek.com \
    --cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
    --cc=Shawn.Sung@mediatek.com \
    --cc=Singo.Chang@mediatek.com \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=chunkuang.hu@kernel.org \
    --cc=jassisinghbrar@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=matthias.bgg@gmail.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®