From: Sudeep Holla <sudeep.holla@arm.com>
To: Ran Wang <ran.wang_1@nxp.com>, Shawn Guo <shawnguo@kernel.org>
Cc: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
Sudeep Holla <sudeep.holla@arm.com>, Leo Li <leoyang.li@nxp.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Yuantian Tang <andy.tang@nxp.com>
Subject: Re: [PATCH 3/3] arm64: dts: update the cpu idle node
Date: Thu, 15 Mar 2018 15:25:12 +0000 [thread overview]
Message-ID: <346ad3d2-04e4-7df3-5187-36124b3c717b@arm.com> (raw)
In-Reply-To: <20180208075436.38443-3-ran.wang_1@nxp.com>
(sorry for replying so late, just found this by accident when clearing
old emails)
On 08/02/18 07:54, Ran Wang wrote:
> From: Yuantian Tang <andy.tang@nxp.com>
>
> According to PSCI standard v0.2, for CPU_SUSPEND call, which is
> used by cpu idle framework, bit[16] of state parameter must be 0.
> So update bit[16] of property 'arm,psci-suspend-param', which is
> used as state parameter, to 0.
>
This changelog makes zero sense to me.
1. PSCI specification makes no reference to "cpu idle framework".
It's not a Linux specification to reference anything specific to
Linux CPUIdle framework.
2. "for CPU_SUSPEND call,...bit[16] of state parameter must be 0."
Where exactly to you see that ? Specification tells what value of
0 or 1 in bit[16] means.
3. Is this retention state and doesn't need any save restore ? If not
this change is wrong and will break if and when we use
CPU_PM_CPU_IDLE_ENTER_RETENTION if this bit is not set.
--
Regards,
Sudeep
next prev parent reply other threads:[~2018-03-15 15:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-08 7:54 [PATCH 1/3] arm64: dts: ls1012a: add cpu idle support Ran Wang
2018-02-08 7:54 ` [PATCH 2/3] arm64: dts: ls1043a: " Ran Wang
2018-02-08 7:54 ` [PATCH 3/3] arm64: dts: update the cpu idle node Ran Wang
2018-03-15 15:25 ` Sudeep Holla [this message]
2018-02-24 6:25 ` [PATCH 1/3] arm64: dts: ls1012a: add cpu idle support Shawn Guo
2018-02-24 7:12 ` Shawn Guo
2018-02-26 5:08 ` Ran Wang
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=346ad3d2-04e4-7df3-5187-36124b3c717b@arm.com \
--to=sudeep.holla@arm.com \
--cc=andy.tang@nxp.com \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=ran.wang_1@nxp.com \
--cc=robh+dt@kernel.org \
--cc=shawnguo@kernel.org \
--cc=will.deacon@arm.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®