linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: lorenzo.pieralisi@arm.com (Lorenzo Pieralisi)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC] rk3368 idle states
Date: Wed, 2 Dec 2015 11:18:58 +0000	[thread overview]
Message-ID: <20151202111858.GB18981@red-moon> (raw)

Hi Heiko,

while reviewing other dts idle states bindings I spotted the following
snippet in arch/arm64/boot/dts/rockchip/rk3368.dtsi:

cpu_sleep: cpu-sleep-0 {
       compatible = "arm,idle-state";
       arm,psci-suspend-param = <0x1010000>;
       entry-latency-us = <0x3fffffff>;
       exit-latency-us = <0x40000000>;
       min-residency-us = <0xffffffff>;
};

Could you please explain to me how you obtained these residency/latency
values ? They make NO sense whatsoever and I am quite tempted to
ask you to remove this data from the dts file, it is just wrong.

Thanks,
Lorenzo

             reply	other threads:[~2015-12-02 11:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-02 11:18 Lorenzo Pieralisi [this message]
2015-12-03  1:05 ` [RFC] rk3368 idle states Heiko Stübner
2015-12-03 10:11   ` Lorenzo Pieralisi

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=20151202111858.GB18981@red-moon \
    --to=lorenzo.pieralisi@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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;
as well as URLs for NNTP newsgroup(s).