On 2/19/19 9:55 AM, Uwe Kleine-König wrote:
> On Tue, Feb 19, 2019 at 09:46:32AM +0100, Fabrice Gasnier wrote:
>> On 2/18/19 6:22 PM, Uwe Kleine-König wrote:
>>> Hello,
>>>
>>> On Thu, Feb 14, 2019 at 11:25:51AM +0100, Fabrice Gasnier wrote:
Add a device link between the PWM consumer and the P
On Tue, Feb 19, 2019 at 09:46:32AM +0100, Fabrice Gasnier wrote:
> On 2/18/19 6:22 PM, Uwe Kleine-König wrote:
> > Hello,
> >
> > On Thu, Feb 14, 2019 at 11:25:51AM +0100, Fabrice Gasnier wrote:
> >> Add a device link between the PWM consumer and the PWM provider. This
> >> enforces the PWM user t
On 2/18/19 6:22 PM, Uwe Kleine-König wrote:
> Hello,
>
> On Thu, Feb 14, 2019 at 11:25:51AM +0100, Fabrice Gasnier wrote:
>> Add a device link between the PWM consumer and the PWM provider. This
>> enforces the PWM user to get suspended before the PWM provider. It
>> allows proper synchronization
Hello,
On Thu, Feb 14, 2019 at 11:25:51AM +0100, Fabrice Gasnier wrote:
> Add a device link between the PWM consumer and the PWM provider. This
> enforces the PWM user to get suspended before the PWM provider. It
> allows proper synchronization of suspend/resume sequences: the PWM user
> is respon
Add a device link between the PWM consumer and the PWM provider. This
enforces the PWM user to get suspended before the PWM provider. It
allows proper synchronization of suspend/resume sequences: the PWM user
is responsible for properly stopping PWM, before the provider gets
suspended: see [1]. Add
5 matches
Mail list logo