Re: [PATCH v2 0/6] Add initial support for Broadcom Cygnus SoC

From: Florian Fainelli
Date: Thu Sep 25 2014 - 20:14:48 EST


Scott, Jonathan,

On 09/25/2014 02:22 PM, Florian Fainelli wrote:
> Hi Scott,
>
> On 09/25/2014 02:04 PM, Scott Branden wrote:
>> Hi Matt/Christian (and others),
>>
>> We would like to move forward in getting our base Cygnus support into
>> the mainline kernel. From there we will be able to contribute
>> additional drivers.
>>
>> Is somebody willing to accept this pull request to get this patchset
>> accepted by the open source community?
>
> I am fine with taking the ARM patches and putting them at
> http://github/brcm/linux.git, with C code in cygnus/board and the Device
> Tree files in cygnus/dt for instance?
>
> The clock driver patch will have to go through Mike Turquette's tree
> unless he wants to delegate that one.

Could you resend patch 3 without the clock binding, patch 4 without the
clocks node, and patch 6 without the drivers/clk changes? Once you do
that, I can assemble these patches quickly and send a pull request which
does only contain ARM SoC and DTS changes, and you can get the clock
driver to be reviewed separately by its maintainer?

Thanks!

>
>>
>> Regards,
>> Scott
>>
>>
>> On 14-09-23 02:17 PM, Jonathan Richardson wrote:
>>> Hi,
>>>
>>> This patchset contains initial support for Broadcom's Cygnus SoC based
>>> on our
>>> iProc architecture. Initial support is minimal and includes just the mach
>>> platform code, clock driver, and a basic device tree configuration.
>>> Peripheral
>>> drivers will be submitted soon, as will device tree configurations for
>>> other
>>> Cygnus board variants.
>>>
>>> Changes from v1:
>>> - Address code review comments as per previous responses.
>>> - Copyright headers updated to remove Broadcom URL.
>>> - mach platform code still contains hard coded adresses. These
>>> address are
>>> the same for all Cygnus variants. Could you please provide
>>> guidance on where
>>> they should go if you would still like them changed.
>>>
>>> Thanks,
>>> Jon
>>>
>>> Jonathan Richardson (6):
>>> ARM: cygnus: Initial support for Broadcom Cygnus SoC
>>> clk: Clock driver support for Broadcom Cygnus SoC
>>> dt-bindings: Document Broadcom Cygnus SoC and clock driver
>>> ARM: dts: Enable Broadcom Cygnus SoC
>>> ARM: cygnus defconfig : Initial defconfig for Broadcom Cygnus SoC
>>> MAINTAINERS: Entry for Cygnus/iproc arm architecture and clock
>>> drivers
>>>
>>> Documentation/devicetree/bindings/arm/cygnus.txt | 12 +
>>> .../devicetree/bindings/clock/clk-cygnus.txt | 121 ++
>>> .../devicetree/bindings/clock/clk-iproc.txt | 48 +
>>> MAINTAINERS | 21 +
>>> arch/arm/boot/dts/Makefile | 1 +
>>> arch/arm/boot/dts/bcm-cygnus.dtsi | 349 ++++++
>>> arch/arm/boot/dts/bcm911360_entphn.dts | 22 +
>>> arch/arm/configs/bcm_cygnus_defconfig | 223 ++++
>>> arch/arm/mach-bcm/Kconfig | 31 +
>>> arch/arm/mach-bcm/Makefile | 3 +
>>> arch/arm/mach-bcm/bcm_cygnus.c | 166 +++
>>> drivers/clk/Makefile | 1 +
>>> drivers/clk/bcm/Makefile | 2 +
>>> drivers/clk/bcm/clk-cygnus.c | 1186
>>> ++++++++++++++++++++
>>> drivers/clk/bcm/clk-iproc.c | 451 ++++++++
>>> 15 files changed, 2637 insertions(+)
>>> create mode 100644 Documentation/devicetree/bindings/arm/cygnus.txt
>>> create mode 100644
>>> Documentation/devicetree/bindings/clock/clk-cygnus.txt
>>> create mode 100644
>>> Documentation/devicetree/bindings/clock/clk-iproc.txt
>>> create mode 100644 arch/arm/boot/dts/bcm-cygnus.dtsi
>>> create mode 100644 arch/arm/boot/dts/bcm911360_entphn.dts
>>> create mode 100644 arch/arm/configs/bcm_cygnus_defconfig
>>> create mode 100644 arch/arm/mach-bcm/bcm_cygnus.c
>>> create mode 100644 drivers/clk/bcm/clk-cygnus.c
>>> create mode 100644 drivers/clk/bcm/clk-iproc.c
>>>
>>
>>
>> _______________________________________________
>> linux-arm-kernel mailing list
>> linux-arm-kernel@xxxxxxxxxxxxxxxxxxx
>> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
>

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/