Re: [PATCH v3 01/12] pwm: introduce default period and polarity concepts

On 21/09/2015 at 11:33:18 +0200, Boris Brezillon wrote : > When requested by a user, the PWM is assigned a default period and polarity > extracted from the DT, the platform data or statically set by the driver. > Those default values are currently stored in the period and polarity > fields of the

Re: [PATCH v3 01/12] pwm: introduce default period and polarity concepts

On 21/09/2015 at 11:33:18 +0200, Boris Brezillon wrote : > When requested by a user, the PWM is assigned a default period and polarity > extracted from the DT, the platform data or statically set by the driver. > Those default values are currently stored in the period and polarity > fields of the

Re: [PATCH v3 01/12] pwm: introduce default period and polarity concepts

On Mon, 21 Sep 2015, Boris Brezillon wrote: > When requested by a user, the PWM is assigned a default period and polarity > extracted from the DT, the platform data or statically set by the driver. > Those default values are currently stored in the period and polarity > fields of the pwm_device

Re: [PATCH v3 01/12] pwm: introduce default period and polarity concepts

Hi Boris, On 09/21/2015 11:33 AM, Boris Brezillon wrote: When requested by a user, the PWM is assigned a default period and polarity extracted from the DT, the platform data or statically set by the driver. Those default values are currently stored in the period and polarity fields of the

Re: [PATCH v3 01/12] pwm: introduce default period and polarity concepts

Hi Boris, On 09/21/2015 11:33 AM, Boris Brezillon wrote: When requested by a user, the PWM is assigned a default period and polarity extracted from the DT, the platform data or statically set by the driver. Those default values are currently stored in the period and polarity fields of the

Re: [PATCH v3 01/12] pwm: introduce default period and polarity concepts

On Mon, 21 Sep 2015, Boris Brezillon wrote: > When requested by a user, the PWM is assigned a default period and polarity > extracted from the DT, the platform data or statically set by the driver. > Those default values are currently stored in the period and polarity > fields of the pwm_device

Re: [PATCH v3 01/12] pwm: introduce default period and polarity concepts

Boris Brezillon writes: > When requested by a user, the PWM is assigned a default period and polarity > extracted from the DT, the platform data or statically set by the driver. > Those default values are currently stored in the period and polarity > fields of the pwm_device struct, but they

[PATCH v3 01/12] pwm: introduce default period and polarity concepts

When requested by a user, the PWM is assigned a default period and polarity extracted from the DT, the platform data or statically set by the driver. Those default values are currently stored in the period and polarity fields of the pwm_device struct, but they will be stored somewhere else once we

[PATCH v3 01/12] pwm: introduce default period and polarity concepts

When requested by a user, the PWM is assigned a default period and polarity extracted from the DT, the platform data or statically set by the driver. Those default values are currently stored in the period and polarity fields of the pwm_device struct, but they will be stored somewhere else once we

Re: [PATCH v3 01/12] pwm: introduce default period and polarity concepts

Boris Brezillon writes: > When requested by a user, the PWM is assigned a default period and polarity > extracted from the DT, the platform data or statically set by the driver. > Those default values are currently stored in the period and polarity > fields of