[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <51153136.7010705@wwwdotorg.org>
Date: Fri, 08 Feb 2013 10:09:10 -0700
From: Stephen Warren <swarren@...dotorg.org>
To: Marc Dietrich <marvin24@....de>
CC: Hiroshi Doyu <hdoyu@...dia.com>, linux-tegra@...r.kernel.org,
arnd@...db.de, Russell King <linux@....linux.org.uk>,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/4] ARM: tegra: Unify tegra{20,30,114}_init_early()
On 02/08/2013 05:29 AM, Marc Dietrich wrote:
> Hiroshi,
>
> Am Freitag, 8. Februar 2013, 09:29:31 schrieb Hiroshi Doyu:
>> Refactored tegra{20,30,114}_init_early() so that we have the unified
>> tegra_init_early().
>> diff --git a/arch/arm/mach-tegra/hotplug.c b/arch/arm/mach-tegra/hotplug.c
>> +void __init tegra_hotplug_init(void)
>> {
>> + switch (tegra_chip_id) {
>> +#ifdef CONFIG_ARCH_TEGRA_2x_SOC
>> + case TEGRA20:
>> + tegra_hotplug_shutdown = tegra20_hotplug_shutdown;
>> + break;
>> #endif
>> +#if defined(CONFIG_ARCH_TEGRA_3x_SOC)
>> + case TEGRA30:
>> + tegra_hotplug_shutdown = tegra30_hotplug_shutdown;
>> + break;
>> #endif
>> + default:
>> + BUG_ON(IS_ENABLED(CONFIG_HOTPLUG_CPU));
>> + break;
>> + }
>> +}
>
> are these ifdefs really needed? Multisoc kernels will enable them all anyway
> and there is a case structure which protects the assignments. Also the hotplug
> functions are very tiny, so there shouldn't be a big loss.
The files that contain/implement those functions are separate for each
SoC and only included in the build when the individual SoCs are enabled.
While multi-platform SoCs do make sense for distros, we also very
specifically want to support the case where only Tegra, and only a
single Tegra SoC, is enabled, hence this separation.
(and Tegra doesn't support multi-platform yet; maybe in another kernel
release or two)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists