Re: [PATCH RFC v4 1/3] PM / Runtime: Add an API pm_runtime_set_slave

On Thu, 12 Feb 2015, amit daniel kachhap wrote: > Hi Alan, > > On Mon, Feb 9, 2015 at 9:28 PM, Alan Stern wrote: > > On Mon, 9 Feb 2015, Amit Daniel Kachhap wrote: > > > >> This API creates a pm runtime slave type device which does not itself > >> participates in pm runtime but depends on the ma

Re: [PATCH RFC v4 1/3] PM / Runtime: Add an API pm_runtime_set_slave

Hi Alan, On Mon, Feb 9, 2015 at 9:28 PM, Alan Stern wrote: > On Mon, 9 Feb 2015, Amit Daniel Kachhap wrote: > >> This API creates a pm runtime slave type device which does not itself >> participates in pm runtime but depends on the master devices to power >> manage them. > > This makes no sense.

Re: [PATCH RFC v4 1/3] PM / Runtime: Add an API pm_runtime_set_slave

On Mon, 9 Feb 2015, Amit Daniel Kachhap wrote: > This API creates a pm runtime slave type device which does not itself > participates in pm runtime but depends on the master devices to power > manage them. This makes no sense. How can a master device manage a slave device? Devices are managed

[PATCH RFC v4 1/3] PM / Runtime: Add an API pm_runtime_set_slave

This API creates a pm runtime slave type device which does not itself participates in pm runtime but depends on the master devices to power manage them. These devices should have pm runtime callbacks. These devices (like clock) may not implement complete pm_runtime calls such as pm_runtime_get/pm_