On Thu, Jun 25, 2009 at 04:35:43PM +0200, Rafael J. Wysocki wrote: > On Thursday 18 June 2009, Kevin Hilman wrote: > > Magnus Damm <magnus.damm@xxxxxxxxx> writes: > > > > > From: Magnus Damm <damm@xxxxxxxxxx> > > > > > > Allow architecture specific data in struct platform_device V3. > > > > > > With this patch struct pdev_archdata is added to struct > > > platform_device, similar to struct dev_archdata in found in > > > struct device. Useful for architecture code that needs to > > > keep extra data associated with each platform device. > > > > > > Struct pdev_archdata is different from dev.platform_data, the > > > convention is that dev.platform_data points to driver-specific > > > data. It may or may not be required by the driver. The format > > > of this depends on driver but is the same across architectures. > > > > > > The structure pdev_archdata is a place for architecture specific > > > data. This data is handled by architecture specific code (for > > > example runtime PM), and since it is architecture specific it > > > should _never_ be touched by device driver code. Exactly like > > > struct dev_archdata but for platform devices. > > > > > > Signed-off-by: Magnus Damm <damm@xxxxxxxxxx> > > > > Since there is no 'Feature-desired-by:' tag, I'll addd > > > > Acked-by: Kevin Hilman <khilman@xxxxxxxxxxxxxxxxxxx> > > > > For PM on ARM in general, and OMAP in particular we definitely need a > > generic way to handle arch-specific data per platform_device. > > Greg, is this patch fine with you? Yes: Acked-by: Greg Kroah-Hartman <gregkh@xxxxxxx> thanks, greg k-h _______________________________________________ linux-pm mailing list linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/linux-pm
