From: dirk.behme@de.bosch.com (Dirk Behme)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3] ARM: imx: replicate the diagnostic register of boot cpu into secondary cores
Date: Thu, 2 May 2013 08:14:59 +0200 [thread overview]
Message-ID: <51820463.8050000@de.bosch.com> (raw)
In-Reply-To: <20130502022147.GC3442@S2101-09.ap.freescale.net>
On 02.05.2013 04:21, Shawn Guo wrote:
> On Wed, May 01, 2013 at 05:38:17PM +0100, Will Deacon wrote:
>> On Wed, May 01, 2013 at 05:19:24PM +0100, Dirk Behme wrote:
>>> Am 01.05.2013 17:38, schrieb Will Deacon:
>>>> On Wed, May 01, 2013 at 04:32:14PM +0100, Dirk Behme wrote:
>>> Just for a better understanding: What's wrong with using the same
>>> register values on all CPUx? I.e. with copying them from CPU0?
>>> Shouldn't all CPUx use the same setting? Or at least the same errata
>>> bits enabled?
>>
>> There's this thing called big.LITTLE... In this case, we're all A9s, but it
>> still feels horrible.
>
> It sounds more like a feeling instead of any issue in real. Unless I
> hear some convincing technical explanation, I will send the patch for
> -rc to fix the broken reboot on imx6q.
As v3 of this patch touches only i.MX specific code, we know that i.MX6
isn't big.LITTLE and all CPUx are the same, I agree with Shawn that it's
ok to do it this way to fix a real bug.
Acked-by: Dirk Behme <dirk.behme@de.bosch.com>
Thanks and best regards
Dirk
prev parent reply other threads:[~2013-05-02 6:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-26 3:57 [PATCH v3] ARM: imx: replicate the diagnostic register of boot cpu into secondary cores Shawn Guo
2013-04-26 13:21 ` Will Deacon
2013-04-26 13:47 ` Shawn Guo
2013-05-01 15:32 ` Dirk Behme
2013-05-01 15:38 ` Will Deacon
2013-05-01 16:19 ` Dirk Behme
2013-05-01 16:38 ` Will Deacon
2013-05-02 2:21 ` Shawn Guo
2013-05-02 6:14 ` Dirk Behme [this message]
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=51820463.8050000@de.bosch.com \
--to=dirk.behme@de.bosch.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.