Re: [PATCH v4 0/3] clk: Broadcom BCM63138 support

2015-11-20 Thread Stephen Boyd
On 11/20, Florian Fainelli wrote: > On 20/11/15 10:46, Stephen Boyd wrote: > > On 11/19, Florian Fainelli wrote: > >> On 19/11/15 17:00, Florian Fainelli wrote: > >>> On 29/10/15 18:23, Florian Fainelli wrote: > This patch series adds support for the Broadcom BCM63138 DSL SoCs > clocking

Re: [PATCH v4 0/3] clk: Broadcom BCM63138 support

2015-11-20 Thread Florian Fainelli
On 20/11/15 10:46, Stephen Boyd wrote: > On 11/19, Florian Fainelli wrote: >> On 19/11/15 17:00, Florian Fainelli wrote: >>> On 29/10/15 18:23, Florian Fainelli wrote: This patch series adds support for the Broadcom BCM63138 DSL SoCs clocking framework. Since the HW is identical

Re: [PATCH v4 0/3] clk: Broadcom BCM63138 support

2015-11-20 Thread Stephen Boyd
On 11/19, Florian Fainelli wrote: > On 19/11/15 17:00, Florian Fainelli wrote: > > On 29/10/15 18:23, Florian Fainelli wrote: > >> This patch series adds support for the Broadcom BCM63138 DSL SoCs > >> clocking framework. > >> > >> Since the HW is identical to the one found in Broadcom iProc SoCs,

Re: [PATCH v4 0/3] clk: Broadcom BCM63138 support

2015-11-19 Thread Florian Fainelli
On 19/11/15 17:00, Florian Fainelli wrote: > On 29/10/15 18:23, Florian Fainelli wrote: >> This patch series adds support for the Broadcom BCM63138 DSL SoCs >> clocking framework. >> >> Since the HW is identical to the one found in Broadcom iProc SoCs, but the >> integration is different (obviously

Re: [PATCH v4 0/3] clk: Broadcom BCM63138 support

2015-11-19 Thread Florian Fainelli
On 29/10/15 18:23, Florian Fainelli wrote: > This patch series adds support for the Broadcom BCM63138 DSL SoCs > clocking framework. > > Since the HW is identical to the one found in Broadcom iProc SoCs, but the > integration is different (obviously), there is still a new compatible string > intro

[PATCH v4 0/3] clk: Broadcom BCM63138 support

2015-10-29 Thread Florian Fainelli
This patch series adds support for the Broadcom BCM63138 DSL SoCs clocking framework. Since the HW is identical to the one found in Broadcom iProc SoCs, but the integration is different (obviously), there is still a new compatible string introduced just in case we happen to find issues in the futu