linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Benoit.Lecardonnel@synopsys.com (Benoit Lecardonnel)
To: linux-arm-kernel@lists.infradead.org
Subject: arm64: Platform devices populated from a device_initcall
Date: Mon, 13 May 2013 17:20:55 +0100	[thread overview]
Message-ID: <519112E7.3040309@synopsys.com> (raw)

Hi all,

In the arm64 kernel, function arm64_device_probe 
(arch/arm64/kernel/setup.c) is in charge of populating the platform 
devices defined by the device tree.

Does anyone know why arm64_device_probe is a device_initcall?

This seems to be in conflict with some I2C drivers: see 
drivers/i2c/busses/i2c-designware-platdrv.c for example.
The driver calls platform_driver_probe from a subsys_initcall.
The probe fails because subsys_initcalls are executed before 
device_initcalls.

Maybe arm64_device_probe could be an arch_initcall?

Thanks,
-- 
Benoit Lecardonnel

             reply	other threads:[~2013-05-13 16:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-13 16:20 Benoit Lecardonnel [this message]
2013-05-14  9:31 ` arm64: Platform devices populated from a device_initcall Catalin Marinas
2013-05-14 11:47   ` Benoit Lecardonnel

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=519112E7.3040309@synopsys.com \
    --to=benoit.lecardonnel@synopsys.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).