From: Stephen Boyd <sboyd@codeaurora.org>
To: Will Deacon <will.deacon@arm.com>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
Stepan Moskovchenko <stepanm@codeaurora.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ARM: proc: Add Krait proc info
Date: Tue, 05 Mar 2013 21:20:32 -0800 [thread overview]
Message-ID: <5136D220.5090904@codeaurora.org> (raw)
In-Reply-To: <51366B9E.7010502@codeaurora.org>
On 03/05/13 14:03, Stephen Boyd wrote:
> On 03/05/13 00:34, Will Deacon wrote:
>> Hi Stephen, Stepan,
>>
>> On Mon, Mar 04, 2013 at 11:21:39PM +0000, Stephen Boyd wrote:
>>> From: Stepan Moskovchenko <stepanm@codeaurora.org>
>>>
>>> Add processor info for the Qualcomm, Inc. Krait family of
>>> processors, to use the generic ARMv7 initialisation
>>> procedure but explicitly enable the IDIV hardware
>>> capability flag.
>>>
>>> Signed-off-by: Stepan Moskovchenko <stepanm@codeaurora.org>
>>> Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>
>>> ---
>>> arch/arm/mm/proc-v7.S | 10 ++++++++++
>>> 1 file changed, 10 insertions(+)
>>>
>>> diff --git a/arch/arm/mm/proc-v7.S b/arch/arm/mm/proc-v7.S
>>> index 3a3c015..81adeb3 100644
>>> --- a/arch/arm/mm/proc-v7.S
>>> +++ b/arch/arm/mm/proc-v7.S
>>> @@ -434,6 +434,16 @@ __v7_ca15mp_proc_info:
>>> .size __v7_ca15mp_proc_info, . - __v7_ca15mp_proc_info
>>>
>>> /*
>>> + * Qualcomm Inc. Krait processors.
>>> + */
>>> + .type __krait_proc_info, #object
>>> +__krait_proc_info:
>>> + .long 0x510f0400 @ Required ID value
>>> + .long 0xff0ffc00 @ Mask for ID
>>> + __v7_proc __v7_setup, hwcaps = HWCAP_IDIV
>> 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
--
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: proc: Add Krait proc info
Date: Tue, 05 Mar 2013 21:20:32 -0800 [thread overview]
Message-ID: <5136D220.5090904@codeaurora.org> (raw)
In-Reply-To: <51366B9E.7010502@codeaurora.org>
On 03/05/13 14:03, Stephen Boyd wrote:
> On 03/05/13 00:34, Will Deacon wrote:
>> Hi Stephen, Stepan,
>>
>> On Mon, Mar 04, 2013 at 11:21:39PM +0000, Stephen Boyd wrote:
>>> From: Stepan Moskovchenko <stepanm@codeaurora.org>
>>>
>>> Add processor info for the Qualcomm, Inc. Krait family of
>>> processors, to use the generic ARMv7 initialisation
>>> procedure but explicitly enable the IDIV hardware
>>> capability flag.
>>>
>>> Signed-off-by: Stepan Moskovchenko <stepanm@codeaurora.org>
>>> Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>
>>> ---
>>> arch/arm/mm/proc-v7.S | 10 ++++++++++
>>> 1 file changed, 10 insertions(+)
>>>
>>> diff --git a/arch/arm/mm/proc-v7.S b/arch/arm/mm/proc-v7.S
>>> index 3a3c015..81adeb3 100644
>>> --- a/arch/arm/mm/proc-v7.S
>>> +++ b/arch/arm/mm/proc-v7.S
>>> @@ -434,6 +434,16 @@ __v7_ca15mp_proc_info:
>>> .size __v7_ca15mp_proc_info, . - __v7_ca15mp_proc_info
>>>
>>> /*
>>> + * Qualcomm Inc. Krait processors.
>>> + */
>>> + .type __krait_proc_info, #object
>>> +__krait_proc_info:
>>> + .long 0x510f0400 @ Required ID value
>>> + .long 0xff0ffc00 @ Mask for ID
>>> + __v7_proc __v7_setup, hwcaps = HWCAP_IDIV
>> 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
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
next prev parent reply other threads:[~2013-03-06 5:20 UTC|newest]
Thread overview: 16+ 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-04 23:21 ` Stephen Boyd
2013-03-05 8:34 ` Will Deacon
2013-03-05 8:34 ` Will Deacon
2013-03-05 22:03 ` Stephen Boyd
2013-03-05 22:03 ` Stephen Boyd
2013-03-06 0:26 ` Will Deacon
2013-03-06 0:26 ` Will Deacon
2013-03-06 5:20 ` Stephen Boyd [this message]
2013-03-06 5:20 ` Stephen Boyd
2013-03-08 6:41 ` Will Deacon
2013-03-08 6:41 ` Will Deacon
2013-03-13 1:31 ` Stephen Boyd
2013-03-13 1:31 ` Stephen Boyd
2013-03-13 11:22 ` Jonathan Austin
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=5136D220.5090904@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=stepanm@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.