Re: [PATCH v2 0/3] Add PWM clock support for bcm2835

2015-11-29 Thread Remi Pommarel
On Sun, Nov 29, 2015 at 10:22:40PM +0100, Stefan Wahren wrote: > Hi Remi, > > Am 29.11.2015 um 01:31 schrieb Remi Pommarel: > >Hi Stefan, > > > >On Sat, Nov 28, 2015 at 09:52:07PM +0100, Stefan Wahren wrote: > >>i applied the series including the devicetree modification, but it > >>doesn't work fo

Re: [PATCH v2 0/3] Add PWM clock support for bcm2835

2015-11-29 Thread Stefan Wahren
Hi Remi, Am 29.11.2015 um 01:31 schrieb Remi Pommarel: Hi Stefan, On Sat, Nov 28, 2015 at 09:52:07PM +0100, Stefan Wahren wrote: i applied the series including the devicetree modification, but it doesn't work for me. First of all i get an ugly division by zero warning from the pwm driver. The

Re: [PATCH v2 0/3] Add PWM clock support for bcm2835

2015-11-28 Thread Remi Pommarel
Hi Stefan, On Sat, Nov 28, 2015 at 09:52:07PM +0100, Stefan Wahren wrote: > i applied the series including the devicetree modification, but it > doesn't work for me. > > First of all i get an ugly division by zero warning from the pwm > driver. The pwm driver still assume a fixed clock and doesn'

Re: [PATCH v2 0/3] Add PWM clock support for bcm2835

2015-11-28 Thread Stefan Wahren
Hi Remi, hi Eric, Am 11.11.2015 um 15:22 schrieb Remi Pommarel: Hi, This patchset adds support for pwm clock. At boot, this clock does not have a default parent nor a default rate set. Thus we should be able to change its parent to get this clock working. The current clock implementation is usi

[PATCH v2 0/3] Add PWM clock support for bcm2835

2015-11-11 Thread Remi Pommarel
Hi, This patchset adds support for pwm clock. At boot, this clock does not have a default parent nor a default rate set. Thus we should be able to change its parent to get this clock working. The current clock implementation is using a mux to select the parent, but these clocks need to add a passw