Re: [PATCH v3 02/11] pwm: imx: remove ipg clock

2016-11-27 Thread Lukasz Majewski
Hi Boris, Stefan, > On Tue, 22 Nov 2016 13:04:11 -0800 > Stefan Agner wrote: > > > On 2016-11-01 00:10, Lukasz Majewski wrote: > > > From: Sascha Hauer > > > > > > The use of the ipg clock was introduced with commit 7b27c160c681 > > > ("pwm: i.MX: fix

Re: [PATCH v3 02/11] pwm: imx: remove ipg clock

2016-11-27 Thread Lukasz Majewski
Hi Boris, Stefan, > On Tue, 22 Nov 2016 13:04:11 -0800 > Stefan Agner wrote: > > > On 2016-11-01 00:10, Lukasz Majewski wrote: > > > From: Sascha Hauer > > > > > > The use of the ipg clock was introduced with commit 7b27c160c681 > > > ("pwm: i.MX: fix clock lookup"). > > > In the commit

Re: [PATCH v3 02/11] pwm: imx: remove ipg clock

2016-11-23 Thread Boris Brezillon
On Tue, 22 Nov 2016 13:04:11 -0800 Stefan Agner wrote: > On 2016-11-01 00:10, Lukasz Majewski wrote: > > From: Sascha Hauer > > > > The use of the ipg clock was introduced with commit 7b27c160c681 > > ("pwm: i.MX: fix clock lookup"). > > In the commit

Re: [PATCH v3 02/11] pwm: imx: remove ipg clock

2016-11-23 Thread Boris Brezillon
On Tue, 22 Nov 2016 13:04:11 -0800 Stefan Agner wrote: > On 2016-11-01 00:10, Lukasz Majewski wrote: > > From: Sascha Hauer > > > > The use of the ipg clock was introduced with commit 7b27c160c681 > > ("pwm: i.MX: fix clock lookup"). > > In the commit message it was claimed that the ipg clock

Re: [PATCH v3 02/11] pwm: imx: remove ipg clock

2016-11-22 Thread Stefan Agner
On 2016-11-01 00:10, Lukasz Majewski wrote: > From: Sascha Hauer > > The use of the ipg clock was introduced with commit 7b27c160c681 > ("pwm: i.MX: fix clock lookup"). > In the commit message it was claimed that the ipg clock is enabled for > register accesses. This is

Re: [PATCH v3 02/11] pwm: imx: remove ipg clock

2016-11-22 Thread Stefan Agner
On 2016-11-01 00:10, Lukasz Majewski wrote: > From: Sascha Hauer > > The use of the ipg clock was introduced with commit 7b27c160c681 > ("pwm: i.MX: fix clock lookup"). > In the commit message it was claimed that the ipg clock is enabled for > register accesses. This is true for the ->config()

Re: [PATCH v3 02/11] pwm: imx: remove ipg clock

2016-11-01 Thread Philipp Zabel
Am Dienstag, den 01.11.2016, 08:10 +0100 schrieb Lukasz Majewski: > From: Sascha Hauer > > The use of the ipg clock was introduced with commit 7b27c160c681 > ("pwm: i.MX: fix clock lookup"). > In the commit message it was claimed that the ipg clock is enabled for >

Re: [PATCH v3 02/11] pwm: imx: remove ipg clock

2016-11-01 Thread Philipp Zabel
Am Dienstag, den 01.11.2016, 08:10 +0100 schrieb Lukasz Majewski: > From: Sascha Hauer > > The use of the ipg clock was introduced with commit 7b27c160c681 > ("pwm: i.MX: fix clock lookup"). > In the commit message it was claimed that the ipg clock is enabled for > register accesses. This is

[PATCH v3 02/11] pwm: imx: remove ipg clock

2016-11-01 Thread Lukasz Majewski
From: Sascha Hauer The use of the ipg clock was introduced with commit 7b27c160c681 ("pwm: i.MX: fix clock lookup"). In the commit message it was claimed that the ipg clock is enabled for register accesses. This is true for the ->config() callback, but not for the

[PATCH v3 02/11] pwm: imx: remove ipg clock

2016-11-01 Thread Lukasz Majewski
From: Sascha Hauer The use of the ipg clock was introduced with commit 7b27c160c681 ("pwm: i.MX: fix clock lookup"). In the commit message it was claimed that the ipg clock is enabled for register accesses. This is true for the ->config() callback, but not for the ->set_enable() callback. Given