On Sat, Aug 6, 2011 at 1:19 AM, Kevin Hilman wrote:
> Add omap_device pointer to the ARM-specific arch data in the
> platform_device. This will be used to attach OMAP-specific
> device-data to the platform device with device lifetime.
>
> Suggested-by: Russell King
> Cc: Grant Likely
> Signed-o
Yes, I think this is the right thing to do. It will certainly make it
possible to keep omap-specific hooks out of the device tree
of_platform_populate() path by using a notifier to attach hwmod data
instead.
Lightly-glanced-at-by: Grant Likely
g.
On Sat, Aug 6, 2011 at 1:19 AM, Kevin Hilman w
From: Thomas Meyer
Use kstrdup rather than duplicating its implementation
The semantic patch that makes this output is available
in scripts/coccinelle/api/kstrdup.cocci.
More information about semantic patching is available at
http://coccinelle.lip6.fr/
Signed-off-by: Thomas Meyer
---
d
On Saturday, August 06, 2011, Mark Brown wrote:
> On Fri, Aug 05, 2011 at 09:37:36PM +0200, Rafael J. Wysocki wrote:
> > On Friday, August 05, 2011, Mark Brown wrote:
>
> > > Do you have any examples of this that aren't better expressed in device
> > > specific terms?
>
> > I'm not sure what you
On Sat, Aug 06, 2011 at 09:46:20PM +0200, Rafael J. Wysocki wrote:
> On Saturday, August 06, 2011, Mark Brown wrote:
> > I wouldn't say we've got to rely on userspace here - it seems like we
> > ought to be able to use DMI or other system data to identify the
> > affected systems and activate the
On Fri, Aug 05, 2011 at 02:31:16PM +0200, Cousson, Benoit wrote:
> On 8/5/2011 12:02 PM, Barry Song wrote:
> >>auxdata passes platform_data and overrides the device name when there
> >>is no way easy way to make the driver work without it. It handles the
> >>the current implementation of clocks an
