Re: [PATCH 8/9] OMAP1 / PM: Use generic clock manipulation routines for runtime PM

[Paul Mundt]

On Sun, Apr 17, 2011 at 01:43:28AM +0200, Rafael J. Wysocki wrote:
> @@ -75,24 +69,7 @@ static int __init omap1_pm_runtime_init(
>  	if (!cpu_class_is_omap1())
>  		return -ENODEV;
>  
> -	pm = platform_bus_get_pm_ops();
> -	if (!pm) {
> -		pr_err("%s: unable to get dev_pm_ops from platform_bus\n",
> -			__func__);
> -		return -ENODEV;
> -	}
> -
> -	omap_pm = kmemdup(pm, sizeof(struct dev_pm_ops), GFP_KERNEL);
> -	if (!omap_pm) {
> -		pr_err("%s: unable to alloc memory for new dev_pm_ops\n",
> -			__func__);
> -		return -ENOMEM;
> -	}
> -
> -	omap_pm->runtime_suspend = omap1_pm_runtime_suspend;
> -	omap_pm->runtime_resume = omap1_pm_runtime_resume;
> -
> -	platform_bus_set_pm_ops(omap_pm);
> +	pm_runtim_clock_add_notifier(&platform_bus_type, &platform_bus_notifier);
>  
Presumably you meant pm_runtime_clock_add_notifier() here. You seem to
have the same typo in a few other places too.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/