From: Will Deacon <will.deacon@arm.com>
To: Gregory CLEMENT <gregory.clement@free-electrons.com>
Cc: Lior Amsalem <alior@marvell.com>, Andrew Lunn <andrew@lunn.ch>,
Ike Pan <ike.pan@canonical.com>,
Nadav Haklai <nadavh@marvell.com>,
Ian Molton <ian.molton@codethink.co.uk>,
David Marlin <dmarlin@redhat.com>,
Yehuda Yitschak <yehuday@marvell.com>,
Jani Monoses <jani.monoses@canonical.com>,
Russell King <linux@arm.linux.org.uk>,
Tawfik Bayouk <tawfik@marvell.com>,
Dan Frazier <dann.frazier@canonical.com>,
Eran Ben-Avi <benavi@marvell.com>,
Leif Lindholm <Leif.Lindholm@arm.com>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
Jason Cooper <jason@lakedaemon.net>,
Arnd Bergmann <arnd@arndb.de>, "jcm@redhat.com" <jcm@redhat.com>,
"devicetree-discuss@lists.ozlabs.org"
<devicetree-discuss@lists.ozlabs.org>,
"rob.herring@calxeda.com" <rob.herring@calxeda.com>,
Ben Dooks <ben-linux@fluff.org>,
Mike Turquette <mturquette@linaro.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH V4 1/5] arm: mvebu: Added support for coherency fabric in mach-mvebu
Date: Tue, 20 Nov 2012 16:32:43 +0000 [thread overview]
Message-ID: <20121120163243.GA27765@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <1353357360-7242-2-git-send-email-gregory.clement@free-electrons.com>
Hi Gregory,
Thanks for turning this around so quickly! I still have a few comments on
your assembly, but you've got the right idea:
On Mon, Nov 19, 2012 at 08:35:55PM +0000, Gregory CLEMENT wrote:
> From: Yehuda Yitschak <yehuday@marvell.com>
>
> Signed-off-by: Yehuda Yitschak <yehuday@marvell.com>
> Signed-off-by: Gregory CLEMENT <gregory.clement@free-electrons.com>
[...]
> +/* Function defined in coherncy_ll.S */
> +extern void ll_set_cpu_coherent(void __iomem *base_addr,
> + unsigned int hw_cpu_id);
> +
> +int set_cpu_coherent(unsigned int hw_cpu_id, int smp_group_id)
> +{
> + if (!coherency_base) {
> + pr_warn("Can't make CPU %d cache coherent.\n", hw_cpu_id);
> + pr_warn("Coherency fabric is not initialized\n");
> + return 1;
> + }
> + ll_set_cpu_coherent(coherency_base, hw_cpu_id);
> + return 0;
> +}
Yup, something like this is neater I reckon. You could even make
ll_set_cpu_coherent return 0 if you wanted, but it's up to you.
> +#include <linux/linkage.h>
> +#define ARMADA_XP_CFB_CTL_REG_OFFSET 0x0
> +#define ARMADA_XP_CFB_CFG_REG_OFFSET 0x4
> +
> + .text
> +/*
> + * r0: CFB base adresse register
address
> + * r1: HW CPU id
> + */
> +ENTRY(ll_set_cpu_coherent)
> + /* Create bit by cpu index */
> + add r1,r1,#24
> + mov r3, #1
Can you instead mov r3, #(1 << 24) and get rid of these two instructions?
> + lsl r1, r3, r1
> +
> +
> + /* Add CPU to SMP group - Atomic */
> + orr r0, r0, #ARMADA_XP_CFB_CTL_REG_OFFSET
An add might be clearer here, despite the address alignment.
> + ldr r4, [r0]
> + orr r4 , r4, r1
> + str r4,[r0]
You haven't saved r4, so you can't use it here. It looks like you have r2
spare -- why not use that instead?
> + /* Enable coherency on CPU - Atomic*/
> + orr r0, r0, #ARMADA_XP_CFB_CFG_REG_OFFSET
add
> + ldr r4, [r0]
> + orr r4 , r4, r1
> + str r4,[r0]
mov r0, #0 here if you want to return 0.
> + mov pc, lr
> +ENDPROC(ll_set_cpu_coherent)
Will
next prev parent reply other threads:[~2012-11-20 16:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-19 20:35 [PATCH V4 0/5] SMP support for Armada XP Gregory CLEMENT
[not found] ` <1353357360-7242-1-git-send-email-gregory.clement-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
2012-11-19 20:35 ` [PATCH V4 1/5] arm: mvebu: Added support for coherency fabric in mach-mvebu Gregory CLEMENT
2012-11-20 16:32 ` Will Deacon [this message]
[not found] ` <20121120163243.GA27765-MRww78TxoiP5vMa5CHWGZ34zcgK1vI+I0E9HWUfgJXw@public.gmane.org>
2012-11-20 16:44 ` Gregory CLEMENT
2012-11-19 20:35 ` [PATCH V4 2/5] arm: mvebu: Added initial support for power managmement service unit Gregory CLEMENT
2012-11-19 20:35 ` [PATCH V4 3/5] arm: mvebu: Added IPI support via doorbells Gregory CLEMENT
2012-11-19 20:35 ` [PATCH V4 4/5] arm: mm: Added support for PJ4B cpu and init routines Gregory CLEMENT
2012-11-19 20:35 ` [PATCH V4 5/5] arm: mvebu: Added SMP support for Armada XP Gregory CLEMENT
[not found] ` <1353357360-7242-6-git-send-email-gregory.clement-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
2012-11-20 16:40 ` Will Deacon
[not found] ` <20121120164058.GB27765-MRww78TxoiP5vMa5CHWGZ34zcgK1vI+I0E9HWUfgJXw@public.gmane.org>
2012-11-20 16:49 ` Gregory CLEMENT
[not found] ` <50ABB499.6090508-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
2012-11-20 17:01 ` Will Deacon
[not found] ` <20121120170127.GE27765-MRww78TxoiP5vMa5CHWGZ34zcgK1vI+I0E9HWUfgJXw@public.gmane.org>
2012-11-20 17:06 ` Gregory CLEMENT
2012-11-20 17:07 ` Thomas Petazzoni
2012-11-20 17:09 ` Will Deacon
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=20121120163243.GA27765@mudshark.cambridge.arm.com \
--to=will.deacon@arm.com \
--cc=Leif.Lindholm@arm.com \
--cc=alior@marvell.com \
--cc=andrew@lunn.ch \
--cc=arnd@arndb.de \
--cc=ben-linux@fluff.org \
--cc=benavi@marvell.com \
--cc=dann.frazier@canonical.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=dmarlin@redhat.com \
--cc=gregory.clement@free-electrons.com \
--cc=ian.molton@codethink.co.uk \
--cc=ike.pan@canonical.com \
--cc=jani.monoses@canonical.com \
--cc=jason@lakedaemon.net \
--cc=jcm@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux@arm.linux.org.uk \
--cc=mturquette@linaro.org \
--cc=nadavh@marvell.com \
--cc=rob.herring@calxeda.com \
--cc=sebastian.hesselbarth@gmail.com \
--cc=tawfik@marvell.com \
--cc=yehuday@marvell.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 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).