From: sudeep.holla@arm.com (Sudeep Holla)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] arm64: dts: juno: fix cluster sleep state entry latency on all SoC versions
Date: Thu, 1 Dec 2016 10:11:24 +0000 [thread overview]
Message-ID: <ed75f674-feaf-9c4b-a995-3e815054918d@arm.com> (raw)
In-Reply-To: <1479317491-7435-2-git-send-email-sudeep.holla@arm.com>
On 16/11/16 17:31, Sudeep Holla wrote:
> The core and the cluster sleep state entry latencies can't be same as
> cluster sleep involves more work compared to core level e.g. shared
> cache maintenance.
>
> Experiments have shown on an average about 100us more latency for the
> cluster sleep state compared to the core level sleep. This patch fixes
> the entry latency for the cluster sleep state.
>
> Fixes: 28e10a8f3a03 ("arm64: dts: juno: Add idle-states to device tree")
> Cc: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
> Cc: "Jon Medhurst (Tixy)" <tixy@linaro.org>
> Reviewed-by: Liviu Dudau <Liviu.Dudau@arm.com>
> Signed-off-by: Sudeep Holla <sudeep.holla@arm.com>
You missed to pick up this, I posted this along with vexpress config bus
fix. Sorry for the confusion, I feel pull request are better/easier to
track than single patches. I will send PR from next time if also prefer
that. Let me know.
--
Regards,
Sudeep
next prev parent reply other threads:[~2016-12-01 10:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-16 17:31 [PATCH 1/2] bus: vexpress-config: fix device reference leak Sudeep Holla
2016-11-16 17:31 ` [PATCH 2/2] arm64: dts: juno: fix cluster sleep state entry latency on all SoC versions Sudeep Holla
2016-12-01 10:11 ` Sudeep Holla [this message]
2016-12-02 16:30 ` Arnd Bergmann
2016-11-28 13:57 ` [PATCH 1/2] bus: vexpress-config: fix device reference leak Sudeep Holla
2016-11-30 22:31 ` Arnd Bergmann
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=ed75f674-feaf-9c4b-a995-3e815054918d@arm.com \
--to=sudeep.holla@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