From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 01/04] ARM: shmobile: Initial r8a73a4 SoC support
Date: Tue, 12 Mar 2013 12:25:39 +0000 [thread overview]
Message-ID: <201303121225.40230.arnd@arndb.de> (raw)
In-Reply-To: <20130312045609.19701.39029.sendpatchset@w520>
On Tuesday 12 March 2013, Magnus Damm wrote:
> +static struct platform_device *r8a73a4_devices[] __initdata = {
> +};
> +
> +void __init r8a73a4_add_standard_devices(void)
> +{
> + r8a73a4_clock_init();
> +
> + platform_add_devices(r8a73a4_devices, ARRAY_SIZE(r8a73a4_devices));
> +}
I would suggest doing the platform_add_devices() only when you actually
add devices to the array, unless you have a number of conflicting patches
that each want to add their own devices.
> +#ifdef CONFIG_USE_OF
> +void __init r8a73a4_add_standard_devices_dt(void)
> +{
> + of_platform_populate(NULL, of_default_bus_match_table, NULL, NULL);
> +}
I have a patch that will make this function definition the default, so you
no longer have to provide an init_machine callback if you don't do anything
special. It's ok to leave it in for now, but we might want to do a follow
up patch to remove it once both patches are merged.
> +static const char *r8a73a4_boards_compat_dt[] __initdata = {
> + "renesas,r8a73a4",
> + NULL,
> +};
> +
> +DT_MACHINE_START(R8A73A4_DT, "Generic R8A73A4 (Flattened Device Tree)")
> + .init_irq = irqchip_init,
Same thing for the default irqchip_init.
> + .init_machine = r8a73a4_add_standard_devices_dt,
> + .init_time = shmobile_timer_init,
> + .dt_compat = r8a73a4_boards_compat_dt,
Have you looked into using clocksource_of_init() here? Since you are using
the ARM architected timers, I would expect that they soon will get probed
using that function, which means we have to be careful crossing patches
if someone wants to convert over all the existing users and you add a new one
here.
Arnd
next prev parent reply other threads:[~2013-03-12 12:25 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-12 4:55 [PATCH 00/04] ARM: shmobile: r8a73a4 SoC and APE6EVM board support Magnus Damm
2013-03-12 4:56 ` [PATCH 01/04] ARM: shmobile: Initial r8a73a4 SoC support Magnus Damm
2013-03-12 12:25 ` Arnd Bergmann [this message]
2013-03-14 7:44 ` Magnus Damm
2013-03-14 9:06 ` Arnd Bergmann
2013-03-19 3:22 ` Magnus Damm
2013-03-22 16:03 ` Arnd Bergmann
2013-03-12 4:56 ` [PATCH 02/04] ARM: shmobile: r8a73a4 SCIF support Magnus Damm
2013-03-12 4:56 ` [PATCH 03/04] ARM: shmobile: r8a73a4 IRQC support Magnus Damm
2013-03-12 12:31 ` Arnd Bergmann
2013-03-14 6:59 ` Magnus Damm
2013-03-14 13:43 ` Arnd Bergmann
2013-03-15 5:32 ` Magnus Damm
2013-03-22 16:00 ` Arnd Bergmann
2013-03-12 4:56 ` [PATCH 04/04] ARM: shmobile: APE6EVM support Magnus Damm
2013-03-12 7:51 ` Kuninori Morimoto
2013-03-12 7:57 ` Magnus Damm
2013-03-12 12:16 ` Arnd Bergmann
2013-03-14 7:01 ` Magnus Damm
2013-03-12 5:19 ` [PATCH 00/04] ARM: shmobile: r8a73a4 SoC and APE6EVM board support Kuninori Morimoto
2013-03-12 12:28 ` Arnd Bergmann
2013-03-14 7:28 ` Magnus Damm
2013-03-14 8:59 ` Arnd Bergmann
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=201303121225.40230.arnd@arndb.de \
--to=arnd@arndb.de \
--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).