From: Andy Green <andy@warmcat.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
patches@linaro.org
Subject: Re: [RFC PATCH 1/4] PLATFORM: introduce structure to bind async platform data to a dev path name
Date: Sat, 12 Mar 2011 23:39:15 +0000 [thread overview]
Message-ID: <4D7C0423.9020204@linaro.org> (raw)
In-Reply-To: <201103130029.38458.rjw@sisk.pl>
On 03/12/2011 11:29 PM, Somebody in the thread at some point said:
Hi -
> On Saturday, March 12, 2011, Andy Green wrote:
>> This structure allows tagging arbitrary platform_data that can't be attached
>> to a device until after it is probed, with the device path name that it is
>> to be attached to.
>> +struct platform_async_platform_data {
>> + const char *device_path;
>> + void *platform_data;
>> +};
>> +
>> #endif /* _PLATFORM_DEVICE_H_ */
>
> Using device paths for this purpose seems to be very fragile to me. Isn't
> there any better solution?
Given that this targets board definition files which commonly do the
platform_add_device for the USB bus controller synchronously, and the
bus-connected devices it is aimed at are soldered on to the board
connected to specific bus controllers, the bus paths are completely
deterministic.
-Andy
next prev parent reply other threads:[~2011-03-12 23:39 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 [this message]
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
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=4D7C0423.9020204@linaro.org \
--to=andy@warmcat.com \
--cc=andy.green@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=patches@linaro.org \
--cc=rjw@sisk.pl \
/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