From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: hw_breakpoint: clear DBGVCR out of reset
Date: Sun, 03 Apr 2011 13:22:54 +0100 [thread overview]
Message-ID: <1301833374.5022.9.camel@jazzbox> (raw)
In-Reply-To: <4D9820D6.5040502@codeaurora.org>
Hi Stephen,
On Sun, 2011-04-03 at 08:25 +0100, Stephen Boyd wrote:
> On 4/1/2011 4:24 AM, Will Deacon wrote:
> > The DBGVCR, used for configuring vector catch debug events, is UNKNOWN
> > out of reset on ARMv7. When enabling monitor mode, this must be zeroed
> > to avoid UNPREDICTABLE behaviour.
> >
> > This patch adds the zeroing code to the debug reset path.
> >
> > Reported-by: Stepan Moskovchenko <stepanm@codeaurora.org>
> > Signed-off-by: Will Deacon <will.deacon@arm.com>
>
> Please Cc stable as this fix should go to the 37 and 38 stable trees.
Will do. If you could please confirm that it fixes the problems reported
initially then that would be great.
Thanks,
Will
next prev parent reply other threads:[~2011-04-03 12:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-01 11:24 [PATCH] ARM: hw_breakpoint: clear DBGVCR out of reset Will Deacon
2011-04-03 7:25 ` Stephen Boyd
2011-04-03 12:22 ` Will Deacon [this message]
2011-04-04 20:03 ` Stepan Moskovchenko
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=1301833374.5022.9.camel@jazzbox \
--to=will.deacon@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 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).