From: Arnd Bergmann <arnd@arndb.de>
To: Rob Herring <robherring2@gmail.com>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Santosh Shilimkar <santosh.shilimkar@ti.com>,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
Nicolas Pitre <nico@fluxnic.net>,
Tony Lindgren <tony@atomide.com>, Olof Johansson <olof@lixom.net>,
linux-omap@vger.kernel.org, Fabio Estevam <festevam@gmail.com>
Subject: Re: [PATCH, RFC] default machine descriptor for multiplatform
Date: Tue, 5 Feb 2013 22:23:04 +0000 [thread overview]
Message-ID: <201302052223.04807.arnd@arndb.de> (raw)
In-Reply-To: <CAL_JsqJ2SyGeJePvNh5fREWP5LcAxnvNsiq2=kKNxKrnquyy3Q@mail.gmail.com>
On Tuesday 05 February 2013, Rob Herring wrote:
> >
> > + if (IS_ENABLED(CONFIG_ARCH_MULTIPLATFORM)) {
> > + DT_MACHINE_START(GENERIC_DT, "Generic DT based system")
> > + MACHINE_END
>
> I assume this works, but it looks a bit strange declared here.
Yes, I was wondering whether it should be global instead, but that
would require an #ifdef, or enabling it for all DT-based builds, not
just those with ARCH_MULTIPLATFORM.
> > static int __init customize_machine(void)
> > {
> > - /* customizes platform devices, or adds new ones */
> > + /*
> > + * customizes platform devices, or adds new ones
> > + * On DT based machines, we fall back to populating the
> > + * machine from the device tree, if no callback is provided,
> > + * otherwise we would always need an init_machine callback.
> > + */
> > if (machine_desc->init_machine)
> > machine_desc->init_machine();
> > + else
> > + of_platform_populate(NULL, of_default_bus_match_table,
> > + NULL, NULL);
>
> Could this be unconditional? It should be safe to call multiple times
> if a platform calls this first because ordering matters or there are
> custom match tables. I would guess any ordering requirements need to
> happen before this call anyway.
Yes, possible, but that needs more testing to avoid potential regressions.
Arnd
next prev parent reply other threads:[~2013-02-05 22:23 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-31 1:49 Failure to boot Russell King - ARM Linux
2013-01-31 3:02 ` Olof Johansson
2013-01-31 4:19 ` Nicolas Pitre
2013-01-31 9:20 ` Russell King - ARM Linux
2013-01-31 10:40 ` Russell King - ARM Linux
2013-01-31 12:49 ` Santosh Shilimkar
2013-01-31 13:04 ` Russell King - ARM Linux
2013-01-31 14:00 ` Santosh Shilimkar
2013-01-31 14:10 ` Santosh Shilimkar
2013-01-31 14:13 ` Russell King - ARM Linux
2013-01-31 14:16 ` Russell King - ARM Linux
2013-01-31 14:20 ` Santosh Shilimkar
2013-01-31 14:27 ` Russell King - ARM Linux
2013-01-31 14:43 ` Santosh Shilimkar
2013-01-31 16:00 ` Tony Lindgren
2013-01-31 16:19 ` Russell King - ARM Linux
2013-01-31 16:01 ` Fabio Estevam
2013-01-31 16:18 ` Russell King - ARM Linux
2013-01-31 16:27 ` Arnd Bergmann
2013-01-31 17:51 ` [PATCH, RFC] default machine descriptor for multiplatform Arnd Bergmann
2013-01-31 18:52 ` Stephen Warren
2013-01-31 20:57 ` Arnd Bergmann
2013-01-31 20:34 ` Nicolas Pitre
2013-02-01 11:47 ` Santosh Shilimkar
2013-02-01 12:34 ` Arnd Bergmann
2013-02-05 21:37 ` Rob Herring
2013-02-05 22:23 ` Arnd Bergmann [this message]
2013-02-05 21:39 ` Olof Johansson
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=201302052223.04807.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=festevam@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=nico@fluxnic.net \
--cc=olof@lixom.net \
--cc=robherring2@gmail.com \
--cc=santosh.shilimkar@ti.com \
--cc=tony@atomide.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