From: dirk.behme@de.bosch.com (Dirk Behme)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/1 v2] ARM: coresight: fix system halt when etm enable and add nosmp to command line
Date: Fri, 20 Feb 2015 08:18:51 +0100 [thread overview]
Message-ID: <54E6DFDB.8070603@de.bosch.com> (raw)
In-Reply-To: <1424354275-18747-1-git-send-email-Frank.Li@freescale.com>
Hi Frank,
On 19.02.2015 14:57, Frank.Li at freescale.com wrote:
> From: Frank Li <Frank.Li@freescale.com>
>
> when nosmp set, only 1 core enabled. try to access disable core will halt.
> dts need added arm,primecell-periphid = <id> for none-boot core
> otherwise amba_device_add will halt when read peripheral id.
>
> Signed-off-by: Frank Li <Frank.Li@freescale.com>
Just out of interest: Do you have the coresight patches working on
i.MX6, now?
I.e. is
http://www.spinics.net/lists/arm-kernel/msg397864.html
clarified, now?
Best regards
Dirk
next prev parent reply other threads:[~2015-02-20 7:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-19 13:57 [PATCH 1/1 v2] ARM: coresight: fix system halt when etm enable and add nosmp to command line Frank.Li at freescale.com
2015-02-20 7:18 ` Dirk Behme [this message]
2015-02-20 14:15 ` Zhi Li
2015-02-24 22:00 ` Mathieu Poirier
2015-03-13 15:56 ` Zhi Li
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=54E6DFDB.8070603@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).