Re: [PATCH 2/2] clk: mvebu: dynamically allocate resources in Armada CP110 system controller

On 08/30, Marcin Wojtas wrote: > 2016-08-25 2:16 GMT+02:00 Stephen Boyd : > > On 08/23, Marcin Wojtas wrote: > >> @@ -335,10 +343,12 @@ static int cp110_syscon_clk_probe(struct > >> platform_device *pdev) > >> cp110_clks[CP110_MAX_CORE_CLOCKS + i] = clk; > >>

Re: [PATCH 2/2] clk: mvebu: dynamically allocate resources in Armada CP110 system controller

On 08/30, Marcin Wojtas wrote: > 2016-08-25 2:16 GMT+02:00 Stephen Boyd : > > On 08/23, Marcin Wojtas wrote: > >> @@ -335,10 +343,12 @@ static int cp110_syscon_clk_probe(struct > >> platform_device *pdev) > >> cp110_clks[CP110_MAX_CORE_CLOCKS + i] = clk; > >> } > >> > >> -

Re: [PATCH 2/2] clk: mvebu: dynamically allocate resources in Armada CP110 system controller

Hi Stephen, 2016-08-25 2:16 GMT+02:00 Stephen Boyd : > On 08/23, Marcin Wojtas wrote: >> Original commit, which added support for Armada CP110 system controller >> used global variables for storing all clock information. It worked >> fine for Armada 7k SoC, with single CP110

Re: [PATCH 2/2] clk: mvebu: dynamically allocate resources in Armada CP110 system controller

Hi Stephen, 2016-08-25 2:16 GMT+02:00 Stephen Boyd : > On 08/23, Marcin Wojtas wrote: >> Original commit, which added support for Armada CP110 system controller >> used global variables for storing all clock information. It worked >> fine for Armada 7k SoC, with single CP110 block. After

Re: [PATCH 2/2] clk: mvebu: dynamically allocate resources in Armada CP110 system controller

Hello, On Tue, 23 Aug 2016 08:26:49 +0200, Marcin Wojtas wrote: > Original commit, which added support for Armada CP110 system controller > used global variables for storing all clock information. It worked > fine for Armada 7k SoC, with single CP110 block. After dual-CP110 Armada 8k > was

Re: [PATCH 2/2] clk: mvebu: dynamically allocate resources in Armada CP110 system controller

Hello, On Tue, 23 Aug 2016 08:26:49 +0200, Marcin Wojtas wrote: > Original commit, which added support for Armada CP110 system controller > used global variables for storing all clock information. It worked > fine for Armada 7k SoC, with single CP110 block. After dual-CP110 Armada 8k > was

Re: [PATCH 2/2] clk: mvebu: dynamically allocate resources in Armada CP110 system controller

On 08/23, Marcin Wojtas wrote: > Original commit, which added support for Armada CP110 system controller > used global variables for storing all clock information. It worked > fine for Armada 7k SoC, with single CP110 block. After dual-CP110 Armada 8k > was introduced, the data got overwritten and

Re: [PATCH 2/2] clk: mvebu: dynamically allocate resources in Armada CP110 system controller

On 08/23, Marcin Wojtas wrote: > Original commit, which added support for Armada CP110 system controller > used global variables for storing all clock information. It worked > fine for Armada 7k SoC, with single CP110 block. After dual-CP110 Armada 8k > was introduced, the data got overwritten and

[PATCH 2/2] clk: mvebu: dynamically allocate resources in Armada CP110 system controller

Original commit, which added support for Armada CP110 system controller used global variables for storing all clock information. It worked fine for Armada 7k SoC, with single CP110 block. After dual-CP110 Armada 8k was introduced, the data got overwritten and corrupted. This patch fixes the issue

[PATCH 2/2] clk: mvebu: dynamically allocate resources in Armada CP110 system controller

Original commit, which added support for Armada CP110 system controller used global variables for storing all clock information. It worked fine for Armada 7k SoC, with single CP110 block. After dual-CP110 Armada 8k was introduced, the data got overwritten and corrupted. This patch fixes the issue