Re: [PATCH v2 12/16] clk: avoid circular clock topology

On 22 February 2016 at 03:29, Masahiro Yamada wrote: > Hi Joachim, > > > 2016-02-22 6:39 GMT+09:00 Joachim Eastwood : >> Hi everyone, >> >> On 28 December 2015 at 11:10, Masahiro Yamada >> wrote: >>> Currently,

Re: [PATCH v2 12/16] clk: avoid circular clock topology

On 22 February 2016 at 03:29, Masahiro Yamada wrote: > Hi Joachim, > > > 2016-02-22 6:39 GMT+09:00 Joachim Eastwood : >> Hi everyone, >> >> On 28 December 2015 at 11:10, Masahiro Yamada >> wrote: >>> Currently, clk_register() never checks a circular parent looping, >>> but clock providers could

Re: [PATCH v2 12/16] clk: avoid circular clock topology

Hi Joachim, 2016-02-22 6:39 GMT+09:00 Joachim Eastwood : > Hi everyone, > > On 28 December 2015 at 11:10, Masahiro Yamada > wrote: >> Currently, clk_register() never checks a circular parent looping, >> but clock providers could register such

Re: [PATCH v2 12/16] clk: avoid circular clock topology

Hi Joachim, 2016-02-22 6:39 GMT+09:00 Joachim Eastwood : > Hi everyone, > > On 28 December 2015 at 11:10, Masahiro Yamada > wrote: >> Currently, clk_register() never checks a circular parent looping, >> but clock providers could register such an insane clock topology. >> For example, "clk_a"

Re: [PATCH v2 12/16] clk: avoid circular clock topology

Hi everyone, On 28 December 2015 at 11:10, Masahiro Yamada wrote: > Currently, clk_register() never checks a circular parent looping, > but clock providers could register such an insane clock topology. > For example, "clk_a" could have "clk_b" as a parent, and vice

Re: [PATCH v2 12/16] clk: avoid circular clock topology

Hi everyone, On 28 December 2015 at 11:10, Masahiro Yamada wrote: > Currently, clk_register() never checks a circular parent looping, > but clock providers could register such an insane clock topology. > For example, "clk_a" could have "clk_b" as a parent, and vice versa. > In this case,

Re: [RESEND PATCH v2 12/16] clk: avoid circular clock topology

On 12/28, Masahiro Yamada wrote: > Currently, clk_register() never checks a circular parent looping, > but clock providers could register such an insane clock topology. > For example, "clk_a" could have "clk_b" as a parent, and vice versa. > In this case, clk_core_reparent() creates a circular

Re: [RESEND PATCH v2 12/16] clk: avoid circular clock topology

On 12/28, Masahiro Yamada wrote: > Currently, clk_register() never checks a circular parent looping, > but clock providers could register such an insane clock topology. > For example, "clk_a" could have "clk_b" as a parent, and vice versa. > In this case, clk_core_reparent() creates a circular

[RESEND PATCH v2 12/16] clk: avoid circular clock topology

Currently, clk_register() never checks a circular parent looping, but clock providers could register such an insane clock topology. For example, "clk_a" could have "clk_b" as a parent, and vice versa. In this case, clk_core_reparent() creates a circular parent list and __clk_recalc_accuracies()

[PATCH v2 12/16] clk: avoid circular clock topology

Currently, clk_register() never checks a circular parent looping, but clock providers could register such an insane clock topology. For example, "clk_a" could have "clk_b" as a parent, and vice versa. In this case, clk_core_reparent() creates a circular parent list and __clk_recalc_accuracies()

[PATCH v2 12/16] clk: avoid circular clock topology

Currently, clk_register() never checks a circular parent looping, but clock providers could register such an insane clock topology. For example, "clk_a" could have "clk_b" as a parent, and vice versa. In this case, clk_core_reparent() creates a circular parent list and __clk_recalc_accuracies()

[RESEND PATCH v2 12/16] clk: avoid circular clock topology

Currently, clk_register() never checks a circular parent looping, but clock providers could register such an insane clock topology. For example, "clk_a" could have "clk_b" as a parent, and vice versa. In this case, clk_core_reparent() creates a circular parent list and __clk_recalc_accuracies()