From: gregory.clement@free-electrons.com (Gregory CLEMENT)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/9] ARM: mvebu: prepare set_cpu_coherent() for future extension
Date: Wed, 17 Jun 2015 17:28:18 +0200 [thread overview]
Message-ID: <55819212.8020404@free-electrons.com> (raw)
In-Reply-To: <1434456785-23696-3-git-send-email-thomas.petazzoni@free-electrons.com>
Hi Thomas,
On 16/06/2015 14:12, Thomas Petazzoni wrote:
> From: Nadav Haklai <nadavh@marvell.com>
>
> This patch prepares the set_cpu_coherent() function in coherency.c to
> be extended to support other SoCs than Armada XP. It will be needed on
> Armada 38x to re-enable the coherency after exiting from suspend to
> RAM.
>
> This preparation simply moves the function further down in coherency.c
> so that it can use coherency_type(), and uses that function to only do
> the Armada XP specific work if we are on Armada XP.
>
> Signed-off-by: Nadav Haklai <nadavh@marvell.com>
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Acked-by: Gregory CLEMENT <gregory.clement@free-electrons.com>
Thanks,
Gregory
> ---
> arch/arm/mach-mvebu/coherency.c | 29 +++++++++++++++++------------
> 1 file changed, 17 insertions(+), 12 deletions(-)
>
> diff --git a/arch/arm/mach-mvebu/coherency.c b/arch/arm/mach-mvebu/coherency.c
> index e46e9ea..44eedf3 100644
> --- a/arch/arm/mach-mvebu/coherency.c
> +++ b/arch/arm/mach-mvebu/coherency.c
> @@ -65,18 +65,6 @@ static const struct of_device_id of_coherency_table[] = {
> int ll_enable_coherency(void);
> void ll_add_cpu_to_smp_group(void);
>
> -int set_cpu_coherent(void)
> -{
> - if (!coherency_base) {
> - pr_warn("Can't make current CPU cache coherent.\n");
> - pr_warn("Coherency fabric is not initialized\n");
> - return 1;
> - }
> -
> - ll_add_cpu_to_smp_group();
> - return ll_enable_coherency();
> -}
> -
> static int mvebu_hwcc_notifier(struct notifier_block *nb,
> unsigned long event, void *__dev)
> {
> @@ -206,6 +194,23 @@ static int coherency_type(void)
> return type;
> }
>
> +int set_cpu_coherent(void)
> +{
> + int type = coherency_type();
> +
> + if (type == COHERENCY_FABRIC_TYPE_ARMADA_370_XP) {
> + if (!coherency_base) {
> + pr_warn("Can't make current CPU cache coherent.\n");
> + pr_warn("Coherency fabric is not initialized\n");
> + return 1;
> + }
> + ll_add_cpu_to_smp_group();
> + return ll_enable_coherency();
> + }
> +
> + return 0;
> +}
> +
> int coherency_available(void)
> {
> return coherency_type() != COHERENCY_FABRIC_TYPE_NONE;
>
--
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2015-06-17 15:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-16 12:12 [PATCH 0/9] ARM: mvebu: add suspend to RAM support for Armada 38x Thomas Petazzoni
2015-06-16 12:12 ` [PATCH 1/9] ARM: mvebu: fix suspend to RAM on big-endian configurations Thomas Petazzoni
2015-06-17 15:24 ` Gregory CLEMENT
2015-06-16 12:12 ` [PATCH 2/9] ARM: mvebu: prepare set_cpu_coherent() for future extension Thomas Petazzoni
2015-06-17 15:28 ` Gregory CLEMENT [this message]
2015-06-16 12:12 ` [PATCH 3/9] ARM: mvebu: do not check machine in mvebu_pm_init() Thomas Petazzoni
2015-06-17 15:32 ` Gregory CLEMENT
2015-06-16 12:13 ` [PATCH 4/9] ARM: mvebu: prepare mvebu_pm_store_bootinfo() to support multiple SoCs Thomas Petazzoni
2015-06-17 16:12 ` Gregory CLEMENT
2015-06-16 12:13 ` [PATCH 5/9] ARM: mvebu: prepare pm-board.c for the introduction of Armada 38x support Thomas Petazzoni
2015-06-17 16:13 ` Gregory CLEMENT
2015-06-16 12:13 ` [PATCH 6/9] ARM: mvebu: add suspend/resume support for Armada 38x Thomas Petazzoni
2015-06-16 12:13 ` [PATCH 7/9] ARM: mvebu: add suspend/resume related definitions in Armada 38x Device Tree Thomas Petazzoni
2015-06-16 12:13 ` [PATCH 8/9] ARM: mvebu: add suspend/resume DT information for Armada 388 GP Thomas Petazzoni
2015-06-16 12:13 ` [PATCH 9/9] ARM: mvebu: adjust board name and compatible " Thomas Petazzoni
2015-06-17 16:31 ` Gregory CLEMENT
2015-06-17 20:48 ` Thomas Petazzoni
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=55819212.8020404@free-electrons.com \
--to=gregory.clement@free-electrons.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).