From: andrew@lunn.ch (Andrew Lunn)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: mvebu: move Armada 370/XP specific definitions to armada-370-xp.h
Date: Thu, 26 Dec 2013 17:00:48 +0100 [thread overview]
Message-ID: <20131226160048.GA19323@lunn.ch> (raw)
In-Reply-To: <1388046026-332-3-git-send-email-thomas.petazzoni@free-electrons.com>
On Thu, Dec 26, 2013 at 09:20:26AM +0100, Thomas Petazzoni wrote:
> In preparation to the introduction of the support for additional SoC,
> the mvebu/common.h should be clear of Armada 370/XP-specific
> definitions. Therefore, move the Armada 370/XP SMP specific
> definitions to the armada-370-xp.h file.
Hi Thomas
Just a question. How much of armada-370-xp.h is specific to just one
of these? Things like all the SMP support is XP only. Does it make
sense to have armada-370.h, armada-xp.h, then a shared
armada-370-xp.h, followed by common.h?
As more SoCs move in, having a clean well defined structure is going
to help with the merging.
Thanks
Andrew
>
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> ---
> arch/arm/mach-mvebu/armada-370-xp.h | 2 ++
> arch/arm/mach-mvebu/common.h | 3 +--
> 2 files changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm/mach-mvebu/armada-370-xp.h b/arch/arm/mach-mvebu/armada-370-xp.h
> index c612b2c..775d9c3 100644
> --- a/arch/arm/mach-mvebu/armada-370-xp.h
> +++ b/arch/arm/mach-mvebu/armada-370-xp.h
> @@ -20,6 +20,8 @@
>
> void armada_mpic_send_doorbell(const struct cpumask *mask, unsigned int irq);
> void armada_xp_mpic_smp_cpu_init(void);
> +void armada_xp_secondary_startup(void);
> +extern struct smp_operations armada_xp_smp_ops;
> #endif
>
> #endif /* __MACH_ARMADA_370_XP_H */
> diff --git a/arch/arm/mach-mvebu/common.h b/arch/arm/mach-mvebu/common.h
> index 4c84689..c23b077 100644
> --- a/arch/arm/mach-mvebu/common.h
> +++ b/arch/arm/mach-mvebu/common.h
> @@ -22,6 +22,5 @@
> void mvebu_restart(enum reboot_mode mode, const char *cmd);
>
> void armada_xp_cpu_die(unsigned int cpu);
> -void armada_xp_secondary_startup(void);
> -extern struct smp_operations armada_xp_smp_ops;
> +
> #endif
> --
> 1.8.3.2
>
next prev parent reply other threads:[~2013-12-26 16:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-26 8:20 [PATCH 0/2] ARM: mvebu: additional cleanups Thomas Petazzoni
2013-12-26 8:20 ` [PATCH 1/2] ARM: mvebu: remove prototypes of non-existing functions from common.h Thomas Petazzoni
2013-12-26 8:20 ` [PATCH 2/2] ARM: mvebu: move Armada 370/XP specific definitions to armada-370-xp.h Thomas Petazzoni
2013-12-26 16:00 ` Andrew Lunn [this message]
2013-12-26 16:04 ` Thomas Petazzoni
2013-12-26 16:18 ` Andrew Lunn
2013-12-26 16:49 ` Thomas Petazzoni
2013-12-27 17:06 ` Jason Cooper
2013-12-27 18:12 ` [PATCH 0/2] ARM: mvebu: additional cleanups Jason Cooper
-- strict thread matches above, loose matches on Subject: below --
2013-12-26 14:22 [PATCH 0/2] ARM: mvebu: minor improvements Thomas Petazzoni
2013-12-26 14:22 ` [PATCH 2/2] ARM: mvebu: move Armada 370/XP specific definitions to armada-370-xp.h 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=20131226160048.GA19323@lunn.ch \
--to=andrew@lunn.ch \
--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).