linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: add support for the Cortex-A12 processor
Date: Wed, 6 Nov 2013 17:27:40 +0000	[thread overview]
Message-ID: <20131106172740.GA4524@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <1382532376-22758-1-git-send-email-jonathan.austin@arm.com>

On Wed, Oct 23, 2013 at 01:46:16PM +0100, Jonathan Austin wrote:
> The A12 behaves as the A7/A15 does with respect to setting the SMP bit, and
> doesn't require TLB ops broadcasting to be explicitly enabled like the A9 does.
> 
> Note that as the ACTLR cannot (usually) be written from non-secure, it is the
> responsibility of the bootloader/firmware to set this bit per core - it is
> done here in Linux as last resort in case of bad firmware.
> 
> Acked-by: Catalin Marinas <catalin.marinas@arm.com>
> Signed-off-by: Jonathan Austin <jonathan.austin@arm.com>
> ---
>  arch/arm/mm/proc-v7.S |   11 +++++++++++
>  1 file changed, 11 insertions(+)
> 
> diff --git a/arch/arm/mm/proc-v7.S b/arch/arm/mm/proc-v7.S
> index 3a5922d..9745288 100644
> --- a/arch/arm/mm/proc-v7.S
> +++ b/arch/arm/mm/proc-v7.S
> @@ -164,6 +164,7 @@ __v7_cr7mp_setup:
>  	mov	r10, #(1 << 0)			@ Cache/TLB ops broadcasting
>  	b	1f
>  __v7_ca7mp_setup:
> +__v7_ca12mp_setup:
>  __v7_ca15mp_setup:
>  	mov	r10, #0
>  1:
> @@ -440,6 +441,16 @@ __v7_ca7mp_proc_info:
>  	.size	__v7_ca7mp_proc_info, . - __v7_ca7mp_proc_info
>  
>  	/*
> +	 * ARM Ltd. Cortex A12 processor.
> +	 */
> +	.type	__v7_ca12mp_proc_info, #object
> +__v7_ca12mp_proc_info:
> +	.long	0x410fc0d0

Great, looks like we can't count.

Please put this into the patch system:

  Acked-by: Will Deacon <will.deacon@arm.com>

Will

      reply	other threads:[~2013-11-06 17:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-23 12:46 [PATCH] arm: add support for the Cortex-A12 processor Jonathan Austin
2013-11-06 17:27 ` Will Deacon [this message]

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=20131106172740.GA4524@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).