From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: proc: Add Krait proc info
Date: Fri, 8 Mar 2013 06:41:39 +0000 [thread overview]
Message-ID: <20130308064139.GA31156@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <5136D220.5090904@codeaurora.org>
On Wed, Mar 06, 2013 at 05:20:32AM +0000, Stephen Boyd wrote:
> On 03/05/13 14:03, Stephen Boyd wrote:
> > On 03/05/13 00:34, Will Deacon wrote:
> >> I was looking at this the other day and wondered whether we could set
> >> HWCAP_IDIV in __v7_setup, depending on ID_ISAR0[27:24]. I can't immediately
> >> think why that would be difficult, but similarly there may well be a reason
> >> why we assign it like this.
> >>
> >> Fancy taking a look?
> > Ok I'll take a look.
>
> Hmm. I wonder if we did it this way because between version B and C of
> DDI0406 the definition of those bits changed.
>
> In DDI0406B we have
>
> 0 - no support
> 1 - support
>
> and in DDI0406C we have
>
> 0 - no support
> 1 - support in Thumb
> 2 - support in Thumb and ARM
Well spotted, although I think this a documentation error. I've checked both
A7 and A15 and they both advertise '2' (although r0p0 TRM for A7 also gets
this wrong, the CPU does the right thing).
What about the Qualcomm CPUs?
Will
next prev parent reply other threads:[~2013-03-08 6:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-04 23:21 [PATCH] ARM: proc: Add Krait proc info Stephen Boyd
2013-03-05 8:34 ` Will Deacon
2013-03-05 22:03 ` Stephen Boyd
2013-03-06 0:26 ` Will Deacon
2013-03-06 5:20 ` Stephen Boyd
2013-03-08 6:41 ` Will Deacon [this message]
2013-03-13 1:31 ` Stephen Boyd
2013-03-13 11:22 ` Jonathan Austin
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=20130308064139.GA31156@mudshark.cambridge.arm.com \
--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).