From: Sudeep Holla <sudeep.holla@arm.com>
To: Donghyeok Choe <d7271.choe@samsung.com>
Cc: Youngmin Nam <youngmin.nam@samsung.com>,
Marc Zyngier <maz@kernel.org>,
Sudeep Holla <sudeep.holla@arm.com>,
Thomas Gleixner <tglx@linutronix.de>,
Saravana Kannan <saravanak@google.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
Vincent Guittot <vincent.guittot@linaro.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kernel-team@android.com,
hajun.sung@samsung.com, joonki.min@samsung.com,
ne.yoo@samsung.com
Subject: Re: [GICv3 ITS]S2IDLE framework does not invoke syscore_ops in GICv3 ITS driver
Date: Mon, 7 Apr 2025 10:17:43 +0100 [thread overview]
Message-ID: <20250407-amiable-perfect-hummingbird-06ad83@sudeepholla> (raw)
In-Reply-To: <20250404041323.GA685160@tiffany>
On Fri, Apr 04, 2025 at 01:13:23PM +0900, Donghyeok Choe wrote:
> On Thu, Apr 03, 2025 at 10:18:54AM +0100, Sudeep Holla wrote:
> > /me more confused.
> >
> > Are you saying you have some cpuidle platform specific logic inside
> > trace_android_vh_cpuidle_psci_enter(). I would assume it was just to
> > trace the entry into the state and nothing more.
>
> If you have any further questions, feel free to reach out.
>
I was trying to understand the difference in behaviour between normal
cpuidle entering the same deepest state that is entered in s2idle state.
I assume GIC doesn't loose power and no need for GIC ITS save/restore
in normal cpuidle path ?
If so, what triggers the GIC suspend in s2idle path if syscore_ops is
not getting called ?
Why would the firmware pull the plug on GIC ?
Do you use any suspend/resume logic in drivers/irqchip/irq-gic-pm.c ?
I am still missing something in this flow.
--
Regards,
Sudeep
next prev parent reply other threads:[~2025-04-07 9:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20250326030527epcas2p33aa30e62cc8a00c9e151c35bee71dac5@epcas2p3.samsung.com>
[not found] ` <Z+Nv8U/4P3taDpUq@perf>
2025-03-26 8:59 ` [GICv3 ITS]S2IDLE framework does not invoke syscore_ops in GICv3 ITS driver Marc Zyngier
2025-03-27 3:22 ` Youngmin Nam
2025-03-27 8:25 ` Marc Zyngier
2025-03-28 2:10 ` Youngmin Nam
2025-04-01 12:45 ` Ulf Hansson
2025-04-01 13:11 ` Marc Zyngier
2025-04-02 10:57 ` Ulf Hansson
2025-04-03 7:16 ` Marc Zyngier
2025-04-02 11:56 ` Sudeep Holla
2025-04-03 1:30 ` Youngmin Nam
2025-04-03 9:18 ` Sudeep Holla
2025-04-04 4:13 ` Donghyeok Choe
2025-04-07 9:17 ` Sudeep Holla [this message]
2025-04-07 22:51 ` Donghyeok Choe
2025-04-08 6:51 ` Marc Zyngier
2025-04-08 22:28 ` Donghyeok Choe
2025-04-08 10:46 ` Sudeep Holla
2025-04-08 22:11 ` Donghyeok Choe
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=20250407-amiable-perfect-hummingbird-06ad83@sudeepholla \
--to=sudeep.holla@arm.com \
--cc=d7271.choe@samsung.com \
--cc=hajun.sung@samsung.com \
--cc=joonki.min@samsung.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=ne.yoo@samsung.com \
--cc=saravanak@google.com \
--cc=tglx@linutronix.de \
--cc=ulf.hansson@linaro.org \
--cc=vincent.guittot@linaro.org \
--cc=youngmin.nam@samsung.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