From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linuxppc-dev@ozlabs.org, devicetree-discuss@lists.ozlabs.org,
David Miller <davem@davemloft.net>,
jk@ozlabs.org
Subject: Re: Deprecating of_platform, the path from here...
Date: Sat, 12 Dec 2009 09:19:16 +1100 [thread overview]
Message-ID: <1260569956.16132.380.camel@pasglop> (raw)
In-Reply-To: <200912111625.29674.arnd@arndb.de>
> The key to the solution IMHO is the ability to create an of_platform_device
> in a hardcoded way without data from a device tree, like we create a
> platform_device today. All these static of_devices would then be rooted
> in /sys/platform by default, while those that come from a device tree are
> in the hierarchy defined there.
.../...
But that has the exact same problem as the other approaches proposed,
which is that in order to convert a driver, all the platforms in all
archs that use it need to be converted to use the new mechanisms,
properties etc...
This is going to be really hard since we don't have access to all of
that HW and will introduce huge lag as I can expect the various embedded
platforms maintainers being in no hurry to help initially.
Cheers,
Ben.
next prev parent reply other threads:[~2009-12-11 22:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-09 22:06 Deprecating of_platform, the path from here Grant Likely
2009-12-10 0:15 ` David Miller
2009-12-10 0:21 ` David Miller
2009-12-10 20:47 ` Grant Likely
2009-12-10 21:56 ` David Miller
2009-12-10 22:03 ` Grant Likely
2009-12-11 15:25 ` Arnd Bergmann
2009-12-11 15:53 ` Joakim Tjernlund
2009-12-11 16:44 ` Grant Likely
2009-12-11 21:17 ` Arnd Bergmann
2009-12-11 22:19 ` Benjamin Herrenschmidt [this message]
2009-12-10 1:45 ` Benjamin Herrenschmidt
2009-12-10 21:30 ` Benjamin Herrenschmidt
2009-12-10 21:53 ` 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=1260569956.16132.380.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=jk@ozlabs.org \
--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