From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: avorontsov@ru.mvista.com
Cc: linuxppc-dev@ozlabs.org, linux-pm@lists.linux-foundation.org,
David Miller <davem@davemloft.net>
Subject: Re: [PATCH] of/platform: Implement support for dev_pm_ops
Date: Wed, 14 Oct 2009 15:55:40 +1100 [thread overview]
Message-ID: <1255496140.2347.36.camel@pasglop> (raw)
In-Reply-To: <20091012224410.GA18923@oksana.dev.rtsoft.ru>
On Tue, 2009-10-13 at 02:44 +0400, Anton Vorontsov wrote:
> I agree that there is some room for improvements in general (e.g.
> merging platform and of_platform devices/drivers), but it's not as
> easy as you would like to think. Let's make it in a separate step
> that don't stop real features from being implemented (e.g.
> hibernate).
>
> For the six functions that we can reuse I can prepare a cleanup
> patch that we can merge via -mm, or it can just sit and collect
> needed acks and can be merged via any tree. But please, no
> cross-tree dependencies for the cruicial features.
I agree. I'll take the patch for now.
In the long run, I'm all for killing of_platform if we can find
a "proper" way to replace it with platform.
IE. With dev_archdata, any device carries the of device node, so
of_platform doesn't really buy us much anymore.
We could even "default" by populating platform device resources
with standard-parsing of "reg" properties etc...
So for devices who don't actually need anything more, we may get
away re-using platform devices as-is, all we would need is some
kind of conversion table or such to map OF match to platform dev names,
or maybe a secondary match table in the drivers themselves.
Anyway, that's an old discussion, something we still need to sort out...
Ben.
prev parent reply other threads:[~2009-10-14 4:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-12 15:50 [PATCH] of/platform: Implement support for dev_pm_ops Anton Vorontsov
2009-10-12 22:09 ` Grant Likely
2009-10-12 22:44 ` Anton Vorontsov
2009-10-14 4:55 ` Benjamin Herrenschmidt [this message]
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=1255496140.2347.36.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=avorontsov@ru.mvista.com \
--cc=davem@davemloft.net \
--cc=linux-pm@lists.linux-foundation.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;
as well as URLs for NNTP newsgroup(s).