From: Stephen Boyd <sboyd@codeaurora.org>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Will Deacon <will.deacon@arm.com>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
Steve Muckle <smuckle@codeaurora.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] ARM: vfp: fix fpsid register subarchitecture field mask width
Date: Wed, 27 Feb 2013 09:44:27 -0800 [thread overview]
Message-ID: <512E45FB.90204@codeaurora.org> (raw)
In-Reply-To: <20130226175439.GT17833@n2100.arm.linux.org.uk>
On 02/26/13 09:54, Russell King - ARM Linux wrote:
> What I actually need from you is: for the Qualcomm implementation, what
> are the subarch bits defined as, and what do they correspond with - both
> the VFP version, and whether they correspond with any ARM common VFP
> subarchitecture version.
For the Qualcomm implementation, the subarch bits have always been 0x40
so far. And they are compatible with "VFPv3 architecture or later with
common VFP subarchitecture v3". In your table below it would be the last
row.
>
> In ARM land, these are the possiblities - I've also listed those
> platforms which I definitely know of at the moment which use the
> particular version combination:
>
> VFP version VFP subarch
> V1 -
> V2 V1 Raspberry Pi
> V3 V2 Marvell Dove (Cubox) (though, not ARM)
> V3 NULL OMAP3430 / OMAP4430
> V3 V3
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
WARNING: multiple messages have this Message-ID (diff)
From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: vfp: fix fpsid register subarchitecture field mask width
Date: Wed, 27 Feb 2013 09:44:27 -0800 [thread overview]
Message-ID: <512E45FB.90204@codeaurora.org> (raw)
In-Reply-To: <20130226175439.GT17833@n2100.arm.linux.org.uk>
On 02/26/13 09:54, Russell King - ARM Linux wrote:
> What I actually need from you is: for the Qualcomm implementation, what
> are the subarch bits defined as, and what do they correspond with - both
> the VFP version, and whether they correspond with any ARM common VFP
> subarchitecture version.
For the Qualcomm implementation, the subarch bits have always been 0x40
so far. And they are compatible with "VFPv3 architecture or later with
common VFP subarchitecture v3". In your table below it would be the last
row.
>
> In ARM land, these are the possiblities - I've also listed those
> platforms which I definitely know of at the moment which use the
> particular version combination:
>
> VFP version VFP subarch
> V1 -
> V2 V1 Raspberry Pi
> V3 V2 Marvell Dove (Cubox) (though, not ARM)
> V3 NULL OMAP3430 / OMAP4430
> V3 V3
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
next prev parent reply other threads:[~2013-02-27 17:44 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-22 8:08 [PATCH] ARM: vfp: fix fpsid register subarchitecture field mask width Stephen Boyd
2013-02-22 8:08 ` Stephen Boyd
2013-02-22 18:27 ` Will Deacon
2013-02-22 18:27 ` Will Deacon
2013-02-22 23:46 ` Stephen Boyd
2013-02-22 23:46 ` Stephen Boyd
2013-02-25 11:18 ` Will Deacon
2013-02-25 11:18 ` Will Deacon
2013-02-26 3:01 ` Stephen Boyd
2013-02-26 3:01 ` Stephen Boyd
2013-02-26 17:54 ` Russell King - ARM Linux
2013-02-26 17:54 ` Russell King - ARM Linux
2013-02-27 17:44 ` Stephen Boyd [this message]
2013-02-27 17:44 ` Stephen Boyd
2013-02-25 17:25 ` Russell King - ARM Linux
2013-02-25 17:25 ` Russell King - ARM Linux
2013-02-25 20:02 ` Russell King - ARM Linux
2013-02-25 20:02 ` Russell King - ARM Linux
2013-02-27 1:37 ` Stephen Boyd
2013-02-27 1:37 ` Stephen Boyd
2013-02-27 11:22 ` Russell King - ARM Linux
2013-02-27 11:22 ` Russell King - ARM Linux
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=512E45FB.90204@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=smuckle@codeaurora.org \
--cc=will.deacon@arm.com \
/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.