From: t.figa@samsung•com (Tomasz Figa)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 0/2] cpuidle fixes and cleanup
Date: Tue, 08 Jul 2014 15:56:48 +0200 [thread overview]
Message-ID: <53BBF8A0.1050005@samsung.com> (raw)
In-Reply-To: <CADWw7OgCgg8aE4W6LwmU3axDdmt-5uH=a+0fSSErfqDci3nNUA@mail.gmail.com>
On 02.07.2014 05:11, Chander Kashyap wrote:
> On Tue, Jul 1, 2014 at 8:22 PM, Russell King - ARM Linux
> <linux@arm•linux.org.uk> wrote:
>> On Tue, Jul 01, 2014 at 08:02:36PM +0530, Chander Kashyap wrote:
>>> This patch series fixes the cpuidle for different states. Also removes arm
>>> diagnostic and power register save/restore code as it is made generic.
>>>
>>> Based on:
>>> ARM: save/restore diagnostic register on Cortex-A9 suspend/resume
>>> http://www.spinics.net/lists/arm-kernel/msg340506.html
[Ccing people who participated in discussion in that thread]
>>
>> As there is an outstanding issue with this patch, we can't proceed with
>> this set of changes until we know what's going on there.
>
> Sure, I will wait for the conclusion.
So I believe the conclusion was that this can't be handled in generic
way, because on systems running in non-secure mode writing to those
registers faults.
However I believe this could be moved into generic helpers.
Best regards,
Tomasz
next prev parent reply other threads:[~2014-07-08 13:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-01 14:32 [PATCH 0/2] cpuidle fixes and cleanup Chander Kashyap
2014-07-01 14:32 ` [PATCH 1/2] ARM: Exynos: remove arm diagnostic and power register save/restore code Chander Kashyap
2014-07-01 14:32 ` [PATCH 2/2] cpuidle: Exynos: fix cpuidle for all states Chander Kashyap
2014-07-15 17:41 ` Tomasz Figa
2014-07-16 4:24 ` Chander Kashyap
2014-07-01 14:52 ` [PATCH 0/2] cpuidle fixes and cleanup Russell King - ARM Linux
2014-07-02 3:11 ` Chander Kashyap
2014-07-08 13:56 ` Tomasz Figa [this message]
2014-07-08 14:17 ` Russell King - ARM Linux
2014-07-09 8:23 ` Chander Kashyap
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=53BBF8A0.1050005@samsung.com \
--to=t.figa@samsung$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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