From: "Moffett, Kyle D" <Kyle.D.Moffett@boeing.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Greg KH <gregkh@suse.de>,
Grant Likely <grant.likely@secretlab.ca>,
Rob Herring <rob.herring@calxeda.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>
Subject: Driver core support for early platform devices
Date: Thu, 22 Dec 2011 11:15:06 -0600 [thread overview]
Message-ID: <0282FD61-7E73-45CE-8EC8-32BF411C7619@boeing.com> (raw)
Hi,
I'm tinkering with some improvements to the way that OpenPIC/MPIC are
detected and loaded on PowerPC platforms, and it seems like I am trying
to use the driver model before it is fully initialized.
In particular, it seems like it should be possible to simply declare an
OpenPIC in the device-tree and have it automatically bound to a platform
driver declaring the right OpenFirmware match strings.
Unfortunately, it needs to be bound by init_IRQ() time, while the driver
model does not get initialized until much later (after the scheduler is
up and running).
As far as I can tell, there seem to be 2 possible approaches to making
that possible:
(1) Split the driver-model initialization into "early" and "late" phases
so that drivers can be registered and devices probed very early on
and then replay the necessary scheduler-dependent things after the
system is mostly started up (IE: devtmpfs, etc).
(2) Create a separate mini-platform-driver-model which can create and
probe platform devices early on and then automatically register them
properly on the platform_bus once the driver model comes up.
Do you think this is the right approach? Is there any existing work
being done to support either model?
Thanks for your help!
Cheers,
Kyle Moffett
--
Curious about my work on the Debian powerpcspe port?
I'm keeping a blog here: http://pureperl.blogspot.com/
next reply other threads:[~2011-12-22 18:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-22 17:15 Moffett, Kyle D [this message]
2011-12-22 17:45 ` Greg KH
2011-12-22 17:55 ` Moffett, Kyle D
2011-12-22 18:10 ` Greg KH
2011-12-22 20:45 ` Rob Herring
2012-01-05 18:41 ` Grant Likely
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=0282FD61-7E73-45CE-8EC8-32BF411C7619@boeing.com \
--to=kyle.d.moffett@boeing.com \
--cc=benh@kernel.crashing.org \
--cc=grant.likely@secretlab.ca \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rob.herring@calxeda.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
all inboxes | Powered by JetHome®