Messages in this thread |  | | Date | Thu, 17 Jan 2013 19:00:17 -0800 | From | Greg Kroah-Hartman <> | Subject | Re: [PATCH] platform: Fix platform device resource linking |
| |
On Thu, Jan 17, 2013 at 07:27:21PM +0200, Pantelis Antoniou wrote: > >> In a nutshell, we have to exercise the platform device subsystem, in ways > >> that never happened before, so all sorts of weird bugs that no-one has seen > >> before. > > > > Why do you have to do this? What are you doing that is so different > > from everyone else? What drivers are you using that trigger this type > > of thing? > > > > This is all part of a larger patchset; I guess you weren't directly CCed. > The name of the patchset is 'Introducing Device Tree Overlays' and is a > method of changing the live device tree and have the changes reflected to > the kernel's state.
Ok, no wonder I was confused :)
How about cc:ing me on the next round of these patches, all of the, which will give me the proper background as to what is going on?
> >> In that case, the code path for creating platform devices from DT is > >> not the same as the one that is used when creating platform device from > >> a board file. > > > > Why not? > > > > Because while DT creates platform devices, it doesn't use the platform device > methods to do so, rather than builds the platform device itself. This is > something that was overlooked.
Can't this be fixed? What does the platform device core need to do to resolve this?
thanks,
greg k-h
|  |