Re: [PATCH v4 0/3] clk: Broadcom BCM63138 support
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 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 future. > > Stephen, could you stage the two patches in a clk-bcm63xx branch that I > could > later utilize while doing the arm-soc DT pull request? > >>> > >>> Stephen, can you queue the first two patches in a topic branch for me to > >>> merge as part of the commit adding the DTS changes? > >> > >> Well, now that I look back at the changes, you can actually merge the > >> two patches in clk-next, and the DTS changes can come in before or > >> after, it does not really matter, this would not cause breakage or > >> anything. Sorry for the noise. > > > > Really? I thought if the clk patches aren't there then the dts > > change would cause some clocks to be orphaned. If that's ok with > > you it's ok with me. > > Woah, I guess I was not thinking very clearly yesterday, yes, we need to > bundle these changes together, so if you are still okay with the topic > branch for me to include as a merge commit, that's fine with me as well. Ok. Done. -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v4 0/3] clk: Broadcom BCM63138 support
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 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 future. Stephen, could you stage the two patches in a clk-bcm63xx branch that I could later utilize while doing the arm-soc DT pull request? >>> >>> Stephen, can you queue the first two patches in a topic branch for me to >>> merge as part of the commit adding the DTS changes? >> >> Well, now that I look back at the changes, you can actually merge the >> two patches in clk-next, and the DTS changes can come in before or >> after, it does not really matter, this would not cause breakage or >> anything. Sorry for the noise. > > Really? I thought if the clk patches aren't there then the dts > change would cause some clocks to be orphaned. If that's ok with > you it's ok with me. Woah, I guess I was not thinking very clearly yesterday, yes, we need to bundle these changes together, so if you are still okay with the topic branch for me to include as a merge commit, that's fine with me as well. /me needs to think twice before typing. -- Florian -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v4 0/3] clk: Broadcom BCM63138 support
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, but the > >> integration is different (obviously), there is still a new compatible > >> string > >> introduced just in case we happen to find issues in the future. > >> > >> Stephen, could you stage the two patches in a clk-bcm63xx branch that I > >> could > >> later utilize while doing the arm-soc DT pull request? > > > > Stephen, can you queue the first two patches in a topic branch for me to > > merge as part of the commit adding the DTS changes? > > Well, now that I look back at the changes, you can actually merge the > two patches in clk-next, and the DTS changes can come in before or > after, it does not really matter, this would not cause breakage or > anything. Sorry for the noise. Really? I thought if the clk patches aren't there then the dts change would cause some clocks to be orphaned. If that's ok with you it's ok with me. -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v4 0/3] clk: Broadcom BCM63138 support
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), there is still a new compatible string >> introduced just in case we happen to find issues in the future. >> >> Stephen, could you stage the two patches in a clk-bcm63xx branch that I could >> later utilize while doing the arm-soc DT pull request? > > Stephen, can you queue the first two patches in a topic branch for me to > merge as part of the commit adding the DTS changes? Well, now that I look back at the changes, you can actually merge the two patches in clk-next, and the DTS changes can come in before or after, it does not really matter, this would not cause breakage or anything. Sorry for the noise. > > Thanks! > >> >> Thank you! >> >> Florian Fainelli (3): >> clk: iproc: Extend binding to cover BCM63138 >> clk: bcm: Add BCM63138 clock support >> ARM: dts: BCM63xx: Add ARMPLL device tree nodes >> >> .../bindings/clock/brcm,iproc-clocks.txt | 5 +++ >> arch/arm/boot/dts/bcm63138.dtsi| 36 >> +- >> drivers/clk/bcm/Kconfig| 10 ++ >> drivers/clk/bcm/Makefile | 1 + >> drivers/clk/bcm/clk-bcm63xx.c | 22 + >> 5 files changed, 66 insertions(+), 8 deletions(-) >> create mode 100644 drivers/clk/bcm/clk-bcm63xx.c >> > > -- Florian -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v4 0/3] clk: Broadcom BCM63138 support
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 > introduced just in case we happen to find issues in the future. > > Stephen, could you stage the two patches in a clk-bcm63xx branch that I could > later utilize while doing the arm-soc DT pull request? Stephen, can you queue the first two patches in a topic branch for me to merge as part of the commit adding the DTS changes? Thanks! > > Thank you! > > Florian Fainelli (3): > clk: iproc: Extend binding to cover BCM63138 > clk: bcm: Add BCM63138 clock support > ARM: dts: BCM63xx: Add ARMPLL device tree nodes > > .../bindings/clock/brcm,iproc-clocks.txt | 5 +++ > arch/arm/boot/dts/bcm63138.dtsi| 36 > +- > drivers/clk/bcm/Kconfig| 10 ++ > drivers/clk/bcm/Makefile | 1 + > drivers/clk/bcm/clk-bcm63xx.c | 22 + > 5 files changed, 66 insertions(+), 8 deletions(-) > create mode 100644 drivers/clk/bcm/clk-bcm63xx.c > -- Florian -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[PATCH v4 0/3] clk: Broadcom BCM63138 support
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 future. Stephen, could you stage the two patches in a clk-bcm63xx branch that I could later utilize while doing the arm-soc DT pull request? Thank you! Florian Fainelli (3): clk: iproc: Extend binding to cover BCM63138 clk: bcm: Add BCM63138 clock support ARM: dts: BCM63xx: Add ARMPLL device tree nodes .../bindings/clock/brcm,iproc-clocks.txt | 5 +++ arch/arm/boot/dts/bcm63138.dtsi| 36 +- drivers/clk/bcm/Kconfig| 10 ++ drivers/clk/bcm/Makefile | 1 + drivers/clk/bcm/clk-bcm63xx.c | 22 + 5 files changed, 66 insertions(+), 8 deletions(-) create mode 100644 drivers/clk/bcm/clk-bcm63xx.c -- 2.1.0 -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
