Hi Stephen,
Am Freitag, den 13.02.2015, 09:16 -0800 schrieb Stephen Boyd:
> On 12/12/14 02:47, Philipp Zabel wrote:
> > +
> > +const struct clk_ops clk_pwm_ops = {
>
> static?
[...]
> > +int clk_pwm_probe(struct platform_device *pdev)
>
> static?
[...]
> > +int clk_pwm_remove(struct platform_dev
On 12/12/14 02:47, Philipp Zabel wrote:
> +
> +const struct clk_ops clk_pwm_ops = {
static?
> + .prepare = clk_pwm_prepare,
> + .unprepare = clk_pwm_unprepare,
> + .recalc_rate = clk_pwm_recalc_rate,
> +};
> +
> +int clk_pwm_probe(struct platform_device *pdev)
static?
> +{
> + s
Hi Thierry,
thank you for the comments.
Am Donnerstag, den 12.02.2015, 23:29 +0100 schrieb Thierry Reding:
> On Fri, Dec 12, 2014 at 11:47:49AM +0100, Philipp Zabel wrote:
> > Some board designers, when running out of clock output pads, decide to
> > (mis)use PWM output pads to provide a clock to
On Fri, Dec 12, 2014 at 11:47:49AM +0100, Philipp Zabel wrote:
> 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 bind
W dniu 2014-12-12 o 11:47, Philipp Zabel pisze:
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 t
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
