From: marc.zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: cpu_pm breaks 3.2 boot on platforms with cascading GICs
Date: Thu, 24 Nov 2011 16:38:43 +0000 [thread overview]
Message-ID: <4ECE7313.8070104@arm.com> (raw)
In-Reply-To: <20111124161336.GB22031@mudshark.cambridge.arm.com>
On 24/11/11 16:13, Will Deacon wrote:
>
> I'm not sure how you want to handle this. Clearly you should only register one
> notifier for the GIC, but it does need to handle the cascading situation
> properly.
>
> This affects current mainline, so we need a solution for 3.2.
I quickly hacked the attached patch, which allows me to boot on PB11MP.
M.
--
Jazz is not dead. It just smells funny...
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-ARM-cpu_pm-register-GIC-PM-notifier-only-once.patch
Type: text/x-patch
Size: 1241 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20111124/caea2993/attachment-0001.bin>
next prev parent reply other threads:[~2011-11-24 16:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-24 16:13 cpu_pm breaks 3.2 boot on platforms with cascading GICs Will Deacon
2011-11-24 16:38 ` Marc Zyngier [this message]
2011-11-24 16:53 ` Will Deacon
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=4ECE7313.8070104@arm.com \
--to=marc.zyngier@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.