On Mon, Aug 08, 2016 at 03:39:15PM +0530, Vignesh R wrote:
> From: Jyri Sarha
>
> Remove all pm_runtime gets and puts, and dummy pm_ops, from the
> pwm-tipwmss driver as there is no direct hardware access. The runtime PM
> needs to be enabled, so that the runtime PM framework
On Mon, Aug 08, 2016 at 03:39:15PM +0530, Vignesh R wrote:
> From: Jyri Sarha
>
> Remove all pm_runtime gets and puts, and dummy pm_ops, from the
> pwm-tipwmss driver as there is no direct hardware access. The runtime PM
> needs to be enabled, so that the runtime PM framework takes care of
>
On 9/5/2016 12:21 PM, Thierry Reding wrote:
> On Mon, Aug 08, 2016 at 03:39:15PM +0530, Vignesh R wrote:
>> From: Jyri Sarha
>>
>> Remove all pm_runtime gets and puts, and dummy pm_ops, from the
>> pwm-tipwmss driver as there is no direct hardware access. The runtime PM
>> needs
On 9/5/2016 12:21 PM, Thierry Reding wrote:
> On Mon, Aug 08, 2016 at 03:39:15PM +0530, Vignesh R wrote:
>> From: Jyri Sarha
>>
>> Remove all pm_runtime gets and puts, and dummy pm_ops, from the
>> pwm-tipwmss driver as there is no direct hardware access. The runtime PM
>> needs to be enabled,
On Mon, Aug 08, 2016 at 03:39:15PM +0530, Vignesh R wrote:
> From: Jyri Sarha
>
> Remove all pm_runtime gets and puts, and dummy pm_ops, from the
> pwm-tipwmss driver as there is no direct hardware access. The runtime PM
> needs to be enabled, so that the runtime PM framework
On Mon, Aug 08, 2016 at 03:39:15PM +0530, Vignesh R wrote:
> From: Jyri Sarha
>
> Remove all pm_runtime gets and puts, and dummy pm_ops, from the
> pwm-tipwmss driver as there is no direct hardware access. The runtime PM
> needs to be enabled, so that the runtime PM framework takes care of
>
On Monday 08 August 2016 03:39 PM, Vignesh R wrote:
> From: Jyri Sarha
>
> Remove all pm_runtime gets and puts, and dummy pm_ops, from the
> pwm-tipwmss driver as there is no direct hardware access. The runtime PM
> needs to be enabled, so that the runtime PM framework takes
On Monday 08 August 2016 03:39 PM, Vignesh R wrote:
> From: Jyri Sarha
>
> Remove all pm_runtime gets and puts, and dummy pm_ops, from the
> pwm-tipwmss driver as there is no direct hardware access. The runtime PM
> needs to be enabled, so that the runtime PM framework takes care of
>
From: Jyri Sarha
Remove all pm_runtime gets and puts, and dummy pm_ops, from the
pwm-tipwmss driver as there is no direct hardware access. The runtime PM
needs to be enabled, so that the runtime PM framework takes care of
enabling/disabling of PWMSS clock when submodules of PWMSS
From: Jyri Sarha
Remove all pm_runtime gets and puts, and dummy pm_ops, from the
pwm-tipwmss driver as there is no direct hardware access. The runtime PM
needs to be enabled, so that the runtime PM framework takes care of
enabling/disabling of PWMSS clock when submodules of PWMSS (ECAP or
10 matches
Mail list logo