Am Samstag, den 27.09.2014, 13:01 -0700 schrieb Mike Turquette:
Quoting Thierry Reding (2014-09-23 01:51:31)
On Wed, Sep 10, 2014 at 10:05:17PM +0200, Janusz Użycki wrote:
Hi,
http://patchwork.ozlabs.org/patch/359069/
https://lkml.org/lkml/2014/6/12/186
Will the patch ever
W dniu 2014-09-27 o 22:01, Mike Turquette pisze:
Quoting Thierry Reding (2014-09-23 01:51:31)
On Wed, Sep 10, 2014 at 10:05:17PM +0200, Janusz Użycki wrote:
Hi,
http://patchwork.ozlabs.org/patch/359069/
https://lkml.org/lkml/2014/6/12/186
Will the patch ever included to linux-next?
I've
Quoting Thierry Reding (2014-09-23 01:51:31)
On Wed, Sep 10, 2014 at 10:05:17PM +0200, Janusz Użycki wrote:
Hi,
http://patchwork.ozlabs.org/patch/359069/
https://lkml.org/lkml/2014/6/12/186
Will the patch ever included to linux-next?
I've never seen this patch before. From a
On Wed, Sep 10, 2014 at 10:05:17PM +0200, Janusz Użycki wrote:
Hi,
http://patchwork.ozlabs.org/patch/359069/
https://lkml.org/lkml/2014/6/12/186
Will the patch ever included to linux-next?
I've never seen this patch before. From a quick look it doesn't seem
like it would work as is, but
Hi,
http://patchwork.ozlabs.org/patch/359069/
https://lkml.org/lkml/2014/6/12/186
Will the patch ever included to linux-next?
pwm_config() API could be extended to support
not only period [ns] and duty [ns] time
but also frequency [Hz] and duty cycle fraction [1/1000?]
(instead of time in ns)
Some board designers, when running out of clock output pads, decide to
(mis)use PWM output pads to provide a clock to external components.
This driver supports this practice by providing an adapter between the
PWM and clock bindings in the device tree. As the PWM bindings specify
the period in the
