Re: [PATCH v2 0/3] clk: Broadcom BCM63138 support
On 27/10/15 14:08, Stephen Boyd wrote:
> On 10/26, Florian Fainelli wrote:
>> Hi all,
>>
>> 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.
>>
>> This applies on top of clk/next as of
>> 679c51cffc3b316bd89ecc91ef92603dd6d4fc68 ("clk: Add stubs for of_clk_*()
>> APIs when CONFIG_OF=n")
>>
>> Since there is an obvious dependency between patch 2 and 3, we can either
>> merge this through the Clock tree or via a future arm-soc pull requests
>> for Broadcom SoCs.
>
> One way to avoid the dependency would be to stage the first two
> patches in clk tree under clk-bcm63xxx and then pull that into
> your local branch via git FETCH && git checkout FETCH_HEAD and
> then apply the 3rd patch on top, tag it and send it off to
> arm-soc. This way, when arm-soc merges into linus' tree the
> dependency is taken care of and we don't take anything for dtsi
> files through the clk tree. It looks like nothing bad will happen
> if patch 2 is merged before patch 3.
Works for me, thanks!
--
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 v2 0/3] clk: Broadcom BCM63138 support
On 10/26, Florian Fainelli wrote:
> Hi all,
>
> 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.
>
> This applies on top of clk/next as of
> 679c51cffc3b316bd89ecc91ef92603dd6d4fc68 ("clk: Add stubs for of_clk_*() APIs
> when CONFIG_OF=n")
>
> Since there is an obvious dependency between patch 2 and 3, we can either
> merge this through the Clock tree or via a future arm-soc pull requests
> for Broadcom SoCs.
One way to avoid the dependency would be to stage the first two
patches in clk tree under clk-bcm63xxx and then pull that into
your local branch via git FETCH && git checkout FETCH_HEAD and
then apply the 3rd patch on top, tag it and send it off to
arm-soc. This way, when arm-soc merges into linus' tree the
dependency is taken care of and we don't take anything for dtsi
files through the clk tree. It looks like nothing bad will happen
if patch 2 is merged before patch 3.
--
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 v2 0/3] clk: Broadcom BCM63138 support
On 10/26/2015 8:53 PM, Florian Fainelli wrote:
Hi all,
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.
This applies on top of clk/next as of
679c51cffc3b316bd89ecc91ef92603dd6d4fc68 ("clk: Add stubs for of_clk_*() APIs when
CONFIG_OF=n")
Since there is an obvious dependency between patch 2 and 3, we can either
merge this through the Clock tree or via a future arm-soc pull requests
for Broadcom SoCs.
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| 39 --
drivers/clk/bcm/Kconfig| 10 ++
drivers/clk/bcm/Makefile | 1 +
drivers/clk/bcm/clk-bcm63xx.c | 22
5 files changed, 67 insertions(+), 10 deletions(-)
create mode 100644 drivers/clk/bcm/clk-bcm63xx.c
The entire patch set looks good to me.
Reviewed-by: Ray Jui
Thanks,
Ray
--
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 v2 0/3] clk: Broadcom BCM63138 support
Hi all,
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.
This applies on top of clk/next as of
679c51cffc3b316bd89ecc91ef92603dd6d4fc68 ("clk: Add stubs for of_clk_*() APIs
when CONFIG_OF=n")
Since there is an obvious dependency between patch 2 and 3, we can either
merge this through the Clock tree or via a future arm-soc pull requests
for Broadcom SoCs.
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| 39 --
drivers/clk/bcm/Kconfig| 10 ++
drivers/clk/bcm/Makefile | 1 +
drivers/clk/bcm/clk-bcm63xx.c | 22
5 files changed, 67 insertions(+), 10 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
