Re: [PATCH v3 0/4] clk: st: New always-on clock domain

2015-04-02 Thread Lee Jones
On Thu, 02 Apr 2015, Geert Uytterhoeven wrote: > On Thu, Mar 26, 2015 at 8:38 PM, Lee Jones wrote: > > On Thu, 26 Mar 2015, Geert Uytterhoeven wrote: > >> On Thu, Mar 26, 2015 at 2:51 PM, Lee Jones wrote: > >> > On Wed, 25 Mar 2015, Geert Uytterhoeven wrote: > >> >> On Mon, Mar 9, 2015 at 10:28 A

Re: [PATCH v3 0/4] clk: st: New always-on clock domain

2015-04-02 Thread Geert Uytterhoeven
Hi Lee, On Thu, Mar 26, 2015 at 8:38 PM, Lee Jones wrote: > On Thu, 26 Mar 2015, Geert Uytterhoeven wrote: >> On Thu, Mar 26, 2015 at 2:51 PM, Lee Jones wrote: >> > On Wed, 25 Mar 2015, Geert Uytterhoeven wrote: >> >> On Mon, Mar 9, 2015 at 10:28 AM, Lee Jones wrote: >> >> > On Fri, 06 Mar 2015

Re: [PATCH v3 0/4] clk: st: New always-on clock domain

2015-03-26 Thread Lee Jones
On Thu, 26 Mar 2015, Geert Uytterhoeven wrote: > Hi Lee, > > On Thu, Mar 26, 2015 at 2:51 PM, Lee Jones wrote: > > On Wed, 25 Mar 2015, Geert Uytterhoeven wrote: > >> On Mon, Mar 9, 2015 at 10:28 AM, Lee Jones wrote: > >> > On Fri, 06 Mar 2015, Mike Turquette wrote: > >> >> This approach looks

Re: [PATCH v3 0/4] clk: st: New always-on clock domain

2015-03-26 Thread Geert Uytterhoeven
Hi Lee, On Thu, Mar 26, 2015 at 2:51 PM, Lee Jones wrote: > On Wed, 25 Mar 2015, Geert Uytterhoeven wrote: >> On Mon, Mar 9, 2015 at 10:28 AM, Lee Jones wrote: >> > On Fri, 06 Mar 2015, Mike Turquette wrote: >> >> This approach looks fine to me. In practice I think it is restricted to >> >> hard

Re: [PATCH v3 0/4] clk: st: New always-on clock domain

2015-03-26 Thread Lee Jones
On Wed, 25 Mar 2015, Geert Uytterhoeven wrote: > Hi Lee, > > On Mon, Mar 9, 2015 at 10:28 AM, Lee Jones wrote: > > On Fri, 06 Mar 2015, Mike Turquette wrote: > >> Quoting Lee Jones (2015-03-04 04:00:03) > >> > Mike, > >> > > >> > Do you want me to resend this set with Robert's Reviewed-by applie

Re: [PATCH v3 0/4] clk: st: New always-on clock domain

2015-03-24 Thread Geert Uytterhoeven
Hi Lee, On Mon, Mar 9, 2015 at 10:28 AM, Lee Jones wrote: > On Fri, 06 Mar 2015, Mike Turquette wrote: >> Quoting Lee Jones (2015-03-04 04:00:03) >> > Mike, >> > >> > Do you want me to resend this set with Robert's Reviewed-by applied, >> > or are you happy to apply it yourself? >> >> No need for

Re: [PATCH v3 0/4] clk: st: New always-on clock domain

2015-03-09 Thread Lee Jones
On Fri, 06 Mar 2015, Mike Turquette wrote: > Quoting Lee Jones (2015-03-04 04:00:03) > > Mike, > > > > Do you want me to resend this set with Robert's Reviewed-by applied, > > or are you happy to apply it yourself? > > No need for the resend. I am hoping for a final review from a DT human. > >

Re: [PATCH v3 0/4] clk: st: New always-on clock domain

2015-03-06 Thread Mike Turquette
Quoting Lee Jones (2015-03-04 04:00:03) > Mike, > > Do you want me to resend this set with Robert's Reviewed-by applied, > or are you happy to apply it yourself? No need for the resend. I am hoping for a final review from a DT human. This approach looks fine to me. In practice I think it is rest

Re: [PATCH v3 0/4] clk: st: New always-on clock domain

2015-03-04 Thread Lee Jones
Mike, Do you want me to resend this set with Robert's Reviewed-by applied, or are you happy to apply it yourself? > v2 => v3: > - Ensure DT actually reflects h/w > - i.e. Nodes should not contain a mishmash of different IP > blocks, but should identify related h/w. In the current >

Re: [PATCH v3 0/4] clk: st: New always-on clock domain

2015-03-02 Thread Lee Jones
On Mon, 02 Mar 2015, Robert Jarzmik wrote: > Lee Jones writes: > > > On Sat, 28 Feb 2015, Robert Jarzmik wrote: > > > >> Lee Jones writes: > >> it doesn't specify which usecase is not covered by CLK_IGNORE_UNUSED, > >> it > >> says, up to my understanding, that is it another way to hav

Re: [PATCH v3 0/4] clk: st: New always-on clock domain

2015-03-02 Thread Robert Jarzmik
Lee Jones writes: > On Sat, 28 Feb 2015, Robert Jarzmik wrote: > >> Lee Jones writes: >> it doesn't specify which usecase is not covered by CLK_IGNORE_UNUSED, it >> says, up to my understanding, that is it another way to have to >> CLK_IGNORE_UNUSED flag applied. > > Well that is exa

Re: [PATCH v3 0/4] clk: st: New always-on clock domain

2015-03-02 Thread Lee Jones
On Sat, 28 Feb 2015, Robert Jarzmik wrote: > Lee Jones writes: > > >> I wonder why there is a need for a new clock when CLK_IGNORE_UNUSED does > >> exist. What is the usecase that is covered by this patchset which is not > >> used by > >> CLK_IGNORE_UNUSED clock flag ? > >> > >> And if that re

Re: [PATCH v3 0/4] clk: st: New always-on clock domain

2015-02-27 Thread Robert Jarzmik
Lee Jones writes: >> I wonder why there is a need for a new clock when CLK_IGNORE_UNUSED does >> exist. What is the usecase that is covered by this patchset which is not >> used by >> CLK_IGNORE_UNUSED clock flag ? >> >> And if that reason exists, I'd like to find it in the commit message. > >

Re: [PATCH v3 0/4] clk: st: New always-on clock domain

2015-02-27 Thread Lee Jones
On Fri, 27 Feb 2015, Robert Jarzmik wrote: > Lee Jones writes: > > > v2 => v3: > > - Ensure DT actually reflects h/w > > - i.e. Nodes should not contain a mishmash of different IP > > blocks, but should identify related h/w. In the current > > example we use interconnects > >

Re: [PATCH v3 0/4] clk: st: New always-on clock domain

2015-02-27 Thread Robert Jarzmik
Lee Jones writes: > v2 => v3: > - Ensure DT actually reflects h/w > - i.e. Nodes should not contain a mishmash of different IP > blocks, but should identify related h/w. In the current > example we use interconnects > - Change naming from clkdomain to clk-always-on > - Plac

Re: [PATCH v3 0/4] clk: st: New always-on clock domain

2015-02-24 Thread Lee Jones
On Tue, 24 Feb 2015, Lee Jones wrote: > v2 => v3: > - Ensure DT actually reflects h/w > - i.e. Nodes should not contain a mishmash of different IP > blocks, but should identify related h/w. In the current > example we use interconnects > - Change naming from clkdomain to clk-a