All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Leach <matthew@mattleach.net>
To: linux-samsung-soc@vger.kernel.org
Subject: Spurious IPIs on secondary cpu bringup with EXYNOS 4412
Date: Mon, 01 Oct 2012 17:48:04 +0100	[thread overview]
Message-ID: <87obkmjfzv.fsf@mattleach.net> (raw)

Hi,

I applied the secondary CPU bringup patch [1] to mainline, however when
booting I get the following spurious IPIs after each core has booted:

[    0.050000] CPU1: Booted secondary processor
[    0.075000] CPU1: thread -1, cpu 1, socket 10, mpidr 80000a01
[    0.080000] CPU1: Unknown IPI message 0x1
[    0.090000] CPU2: Booted secondary processor
[    0.115000] CPU2: thread -1, cpu 2, socket 10, mpidr 80000a02
[    0.120000] CPU2: Unknown IPI message 0x1
[    0.130000] CPU3: Booted secondary processor
[    0.155000] CPU3: thread -1, cpu 3, socket 10, mpidr 80000a03
[    0.160000] CPU3: Unknown IPI message 0x1

Has anyone that has access to the documentation for the 4412 know what
this could be?

[1]: ARM: EXYNOS: Add support for secondary CPU bring-up on Exynos4412

---

Thanks,
Matt

             reply	other threads:[~2012-10-01 16:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-01 16:48 Matthew Leach [this message]
2012-10-02  0:21 ` Spurious IPIs on secondary cpu bringup with EXYNOS 4412 Kyungmin Park

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=87obkmjfzv.fsf@mattleach.net \
    --to=matthew@mattleach.net \
    --cc=linux-samsung-soc@vger.kernel.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.