From: David Miller <davem@davemloft.net>
To: linuxppc-dev@ozlabs.org
Subject: on the topic of of_device resources...
Date: Mon, 05 May 2008 00:59:58 -0700 (PDT) [thread overview]
Message-ID: <20080505.005958.186160264.davem@davemloft.net> (raw)
Since it came to my attention due to the build error fix
I just had to fix, I figured I'd mention some things.
Right now, powerpc and sparc differ in how they resolve
interrupts and resources.
Powerpc uses an on-demand model, whereas Sparc pre-resolves
everything at bootup when parsing the OF tree.
Unfortunately they operate on differing objects too, otherwise I could
provide routines to match the interfaces that powerpc OF drivers want
:-/
Powerpc drivers want device_node objects, whereas sparc roots all
driver usable objects under of_platform_bus using of_device objects
(which point to the device_node if the driver needs that).
Inside of the of_device is where we hang the fully resolved resources
and interrupts.
I'd like to see consolidation in this area, and in return I'll be
compiling all of your PPC_OF devices in my allmodconfig builds on
sparc :-)
next reply other threads:[~2008-05-05 7:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-05 7:59 David Miller [this message]
2008-05-05 8:26 ` on the topic of of_device resources Benjamin Herrenschmidt
2008-05-05 8:44 ` David Miller
2008-05-05 8:55 ` Benjamin Herrenschmidt
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=20080505.005958.186160264.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linuxppc-dev@ozlabs.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).