From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: andy.green@linaro.org
Cc: Greg KH <greg@kroah.com>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
patches@linaro.org
Subject: Re: [RFC PATCH 3/4] PLATFORM: Introduce async platform_data attach api
Date: Sun, 13 Mar 2011 13:53:54 +0100 [thread overview]
Message-ID: <201103131353.54612.rjw@sisk.pl> (raw)
In-Reply-To: <4D7CB15A.6030203@linaro.org>
On Sunday, March 13, 2011, Andy Green wrote:
> On 03/13/2011 10:41 AM, Somebody in the thread at some point said:
> > On Sunday, March 13, 2011, Greg KH wrote:
> >> On Sat, Mar 12, 2011 at 10:32:27PM +0000, Andy Green wrote:
> >>> This introduces a platform API so busses can allow platform_data to
> >>> be attached to any struct device they create from probing in one step.
> >>>
> >>> The function checks through the async platform_data map if one was
> >>> previously registered, and checks the device's device path for itself
> >>> and its parents against the mapped device path names.
> >>>
> >>> If it sees a match, it attaches the associated platform_data and sets
> >>> that map entry's device_path to NULL so no further time is spent trying
> >>> to match it.
> >>
> >> This _really_ should just use the device tree stuff, that is what it is
> >> for, please don't duplicate it here in a not-as-flexible way.
> >
> > I agree.
> >
> > @Andy: If it doesn't work for you for some reason, please let us know the
> > usage case that is not covered (in detail).
>
> The device tree stuff does not yet exist in a workable way,
> platform_data is established everywhere except USB bus. Device tree
> brings in bootloader version as a dependency: this method doesn't.
It is not the same device tree we are talking about. :-)
I mean device hierarchy (and I guess Greg meant the same).
Thanks,
Rafael
next prev parent reply other threads:[~2011-03-13 12:53 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-12 22:32 [RFC PATCH 0/4] PLATFORM: Support for async platform_data Andy Green
2011-03-12 22:32 ` [RFC PATCH 1/4] PLATFORM: introduce structure to bind async platform data to a dev path name Andy Green
2011-03-12 23:29 ` Rafael J. Wysocki
2011-03-12 23:39 ` Andy Green
2011-03-13 1:03 ` Greg KH
2011-03-13 11:22 ` Andy Green
2011-03-13 12:51 ` Rafael J. Wysocki
2011-03-13 13:53 ` Andy Green
2011-03-13 16:58 ` Rafael J. Wysocki
2011-03-13 17:21 ` Andy Green
2011-03-13 20:45 ` Rafael J. Wysocki
2011-03-13 16:14 ` Greg KH
2011-03-13 17:26 ` Andy Green
2011-03-12 22:32 ` [RFC PATCH 2/4] PLATFORM: Introduce registration function for async platform data maps Andy Green
2011-03-12 22:32 ` [RFC PATCH 3/4] PLATFORM: Introduce async platform_data attach api Andy Green
2011-03-13 1:01 ` Greg KH
2011-03-13 10:41 ` Rafael J. Wysocki
2011-03-13 11:58 ` Andy Green
2011-03-13 12:53 ` Rafael J. Wysocki [this message]
2011-03-13 13:21 ` Andy Green
2011-03-13 16:15 ` Greg KH
2011-03-13 17:13 ` Andy Green
2011-03-13 17:48 ` Greg KH
2011-03-13 18:13 ` Andy Green
2011-03-13 23:26 ` Greg KH
2011-03-14 8:38 ` Andy Green
2011-03-14 20:54 ` Greg KH
2011-03-14 21:03 ` Alan Stern
2011-03-14 21:13 ` Greg KH
2011-03-14 21:10 ` Mark Brown
2011-03-14 21:59 ` Andy Green
2011-03-12 22:32 ` [RFC PATCH 4/4] PLATFORM: Add some documentation to platform docs about async platform_data Andy Green
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=201103131353.54612.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=andy.green@linaro.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=patches@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.