[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20141015130218.GB20034@leverpostej>
Date: Wed, 15 Oct 2014 14:02:18 +0100
From: Mark Rutland <mark.rutland@....com>
To: Lorenzo Pieralisi <Lorenzo.Pieralisi@....com>
Cc: Chander Kashyap <k.chander@...sung.com>,
"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-samsung-soc@...r.kernel.org"
<linux-samsung-soc@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"daniel.lezcano@...aro.org" <daniel.lezcano@...aro.org>,
Catalin Marinas <Catalin.Marinas@....com>,
"rjw@...ysocki.net" <rjw@...ysocki.net>,
"kgene.kim@...sung.com" <kgene.kim@...sung.com>
Subject: Re: [PATCH] arm64: dts: exynos7: add support for cpuidle core power
down
> > + CPU_SLEEP: cpu-sleep {
> > + compatible = "arm,idle-state";
> > + local-timer-stop;
> > + arm,psci-suspend-param = <0x0010000>;
> > + entry-latency-us = <20>;
> > + exit-latency-us = <150>;
> > + min-residency-us = <2100>;
> > + status = "enabled";
While status is a relatively standard property, it's absence implies
everything is OK. There no need for it here as-is.
Additionally, the canonical value is "okay", not "enabled", so this
would fail were we to use of_device_is_available in the idle states
parsing.
> status ? This is not a documented property. If you need it please explain
> why, define its bindings and we can see how to accommodate it.
Do we expect that some idle states won't be available on some boards
built from the same platform?
Mark.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists