[GIT PULL 1/7] Broadcom soc changes for 4.8 Part 1

[GIT PULL 1/7] Broadcom soc changes for 4.8 Part 1

[Florian Fainelli]

The following changes since commit 1a695a905c18548062509178b98bc91e67510864:

  Linux 4.7-rc1 (2016-05-29 09:29:24 -0700)

are available in the git repository at:

  http://github.com/Broadcom/stblinux.git tags/arm-soc/for-4.8/soc

for you to fetch changes up to 423779cfd3ca73b9236e6eb798477f3a4f13355d:

  ARM: bcm: fix missing include of kona_l2_cache.h (2016-06-08 10:17:15 -0700)

----------------------------------------------------------------
This pull request contains SoC changes for Broadcom ARM-based SoCs:

- Chris prepares support for the BCM23550 by removing reset code in the
  BCM21664 machine code since a proper drivers/power/reset driver is provided and
  shared, he then adds a machine entry point for BCM23550 and updates the SMP
  code to bring-up the secondary cores on BCM23550

- Ben fixes a warning in the Kona L2 SMC code by adding the missing include file

----------------------------------------------------------------
Ben Dooks (1):
      ARM: bcm: fix missing include of kona_l2_cache.h

Chris Brand (3):
      ARM: bcm21664: Remove reset code
      ARM: Add support for Broadcom BCM23550 SoC
      ARM: BCM23550 SMP support

 arch/arm/mach-bcm/Kconfig          | 12 ++++++--
 arch/arm/mach-bcm/Makefile         |  5 +++-
 arch/arm/mach-bcm/board_bcm21664.c | 42 ---------------------------
 arch/arm/mach-bcm/board_bcm23550.c | 25 ++++++++++++++++
 arch/arm/mach-bcm/kona_l2_cache.c  |  1 +
 arch/arm/mach-bcm/platsmp.c        | 58 ++++++++++++++++++++++++++++++++++++++
 6 files changed, 98 insertions(+), 45 deletions(-)
 create mode 100644 arch/arm/mach-bcm/board_bcm23550.c

[GIT PULL 2/7] Broadcom soc-arm64 changes for 4.8 Part 1

[Florian Fainelli]

The following changes since commit 1a695a905c18548062509178b98bc91e67510864:

  Linux 4.7-rc1 (2016-05-29 09:29:24 -0700)

are available in the git repository at:

  http://github.com/Broadcom/stblinux.git tags/arm-soc/for-4.8/soc-arm64

for you to fetch changes up to 9c7a68017503eda3071ba8647bd0b4c716f18c74:

  arm64: vulcan: enable GPIOLIB in Kconfig (2016-05-31 10:52:25 -0700)

----------------------------------------------------------------
This pull request contains SoC changes for Broadcom ARM64-based SoCs:

- Kamlakant updates the Broadcom Vulcan Kconfig entry with GPIOLIB to enable
  GPIO on these platforms

----------------------------------------------------------------
Kamlakant Patel (1):
      arm64: vulcan: enable GPIOLIB in Kconfig

 arch/arm64/Kconfig.platforms | 1 +
 1 file changed, 1 insertion(+)

[GIT PULL 2/7] Broadcom soc-arm64 changes for 4.8 Part 1

[Olof Johansson]

On Thu, Jun 16, 2016 at 06:56:10PM -0700, Florian Fainelli wrote:
> The following changes since commit 1a695a905c18548062509178b98bc91e67510864:
> 
>   Linux 4.7-rc1 (2016-05-29 09:29:24 -0700)
> 
> are available in the git repository at:
> 
>   http://github.com/Broadcom/stblinux.git tags/arm-soc/for-4.8/soc-arm64
> 
> for you to fetch changes up to 9c7a68017503eda3071ba8647bd0b4c716f18c74:
> 
>   arm64: vulcan: enable GPIOLIB in Kconfig (2016-05-31 10:52:25 -0700)
> 
> ----------------------------------------------------------------
> This pull request contains SoC changes for Broadcom ARM64-based SoCs:
> 
> - Kamlakant updates the Broadcom Vulcan Kconfig entry with GPIOLIB to enable
>   GPIO on these platforms

Merged, thanks.


-Olof

[GIT PULL 3/7] Broadcom devicetree changes for 4.8 Part 1

[Florian Fainelli]

The following changes since commit 1a695a905c18548062509178b98bc91e67510864:

  Linux 4.7-rc1 (2016-05-29 09:29:24 -0700)

are available in the git repository at:

  http://github.com/Broadcom/stblinux.git tags/arm-soc/for-4.8/devicetree

for you to fetch changes up to 2df1808dc0e2b5358e13beb95192b15200017776:

  ARM: dts: BCM5310x: Enable switch ports on SmartRG SR400AC (2016-06-13 12:44:46 -0700)

----------------------------------------------------------------
This pull request contains Device Tree changes for Broadcom ARM-based SoCs:

- Chris provides documentation and DTS fixes for the bcm11351 CPU enable-method in preparation
  for adding support for the BCM23550 SoC and its corresponding documentation, SoC dtsi
  and the Sparrow board DTS file

- Jon adds MSI support to the PCI nodes, updates the secondary cores boot address for the B0
  production revision of the Northstar Plus SoC, adds a DTS for the BCM958625HR board, another
  one for the BCM958525XMC board, and finally adds the PL330 DMA controller to the NSP DTS

- Rafal enables the SPI NOR flash on dual flash systems (NAND + SPI) on the BCM5301x SoCs
  and devices

- Florian adds support for the BCM5301x built-in Ethernet switch by adding nodes for the
  Gigabit MAC controllers and the Switch Register Access block, and finally updates the
  SmartRG SR-400AC board with its switch port layout

----------------------------------------------------------------
Chris Brand (5):
      Documentation: Binding docs for bcm11351 enable method
      ARM: dts: fix use of bcm11351 enable method
      ARM: BCM: modify Broadcom CPU enable method
      Documentation: devicetree: Document BCM23550 bindings
      ARM: dts: bcm23550: Add device tree files

Florian Fainelli (3):
      ARM: dts: Enable SRAB switch and GMACs on 5301x DTS
      ARM: dts: BCM5301X: Add SRAB interrupts
      ARM: dts: BCM5310x: Enable switch ports on SmartRG SR400AC

Jon Mason (5):
      ARM: dts: NSP: Add MSI support on PCI
      ARM: dts: NSP: modify second CPU address
      ARM: dts: NSP: Add new DT file for bcm958625hr
      ARM: dts: NSP: Add XMC board support
      ARM: dts: NSP: Add PL330 support

Rafa? Mi?ecki (1):
      ARM: BCM5301X: Enable SPI-NOR on dual flash devices

 .../bindings/arm/bcm/brcm,bcm11351-cpu-method.txt  |   6 +-
 .../bindings/arm/bcm/brcm,bcm23550-cpu-method.txt  |  36 ++
 .../devicetree/bindings/arm/bcm/brcm,bcm23550.txt  |  15 +
 Documentation/devicetree/bindings/arm/cpus.txt     |   2 +
 arch/arm/boot/dts/Makefile                         |   5 +-
 arch/arm/boot/dts/bcm-nsp.dtsi                     |  55 ++-
 arch/arm/boot/dts/bcm11351.dtsi                    |   2 +-
 arch/arm/boot/dts/bcm21664.dtsi                    |   2 +-
 arch/arm/boot/dts/bcm23550-sparrow.dts             |  80 ++++
 arch/arm/boot/dts/bcm23550.dtsi                    | 415 +++++++++++++++++++++
 arch/arm/boot/dts/bcm4708-buffalo-wzr-1750dhp.dts  |   4 +
 arch/arm/boot/dts/bcm4708-netgear-r6250.dts        |   4 +
 arch/arm/boot/dts/bcm4708-netgear-r6300-v2.dts     |   4 +
 arch/arm/boot/dts/bcm4708-smartrg-sr400ac.dts      |  40 ++
 arch/arm/boot/dts/bcm4709-buffalo-wxr-1900dhp.dts  |   4 +
 arch/arm/boot/dts/bcm47094-dlink-dir-885l.dts      |   4 +
 arch/arm/boot/dts/bcm5301x.dtsi                    |  42 +++
 arch/arm/boot/dts/bcm958525xmc.dts                 | 109 ++++++
 arch/arm/boot/dts/bcm958625hr.dts                  | 107 ++++++
 arch/arm/mach-bcm/platsmp.c                        | 116 ++----
 20 files changed, 966 insertions(+), 86 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/arm/bcm/brcm,bcm23550-cpu-method.txt
 create mode 100644 Documentation/devicetree/bindings/arm/bcm/brcm,bcm23550.txt
 create mode 100644 arch/arm/boot/dts/bcm23550-sparrow.dts
 create mode 100644 arch/arm/boot/dts/bcm23550.dtsi
 create mode 100644 arch/arm/boot/dts/bcm958525xmc.dts
 create mode 100644 arch/arm/boot/dts/bcm958625hr.dts

[GIT PULL 3/7] Broadcom devicetree changes for 4.8 Part 1

[Olof Johansson]

On Thu, Jun 16, 2016 at 06:56:11PM -0700, Florian Fainelli wrote:
> The following changes since commit 1a695a905c18548062509178b98bc91e67510864:
> 
>   Linux 4.7-rc1 (2016-05-29 09:29:24 -0700)
> 
> are available in the git repository at:
> 
>   http://github.com/Broadcom/stblinux.git tags/arm-soc/for-4.8/devicetree
> 
> for you to fetch changes up to 2df1808dc0e2b5358e13beb95192b15200017776:
> 
>   ARM: dts: BCM5310x: Enable switch ports on SmartRG SR400AC (2016-06-13 12:44:46 -0700)
> 
> ----------------------------------------------------------------
> This pull request contains Device Tree changes for Broadcom ARM-based SoCs:
> 
> - Chris provides documentation and DTS fixes for the bcm11351 CPU enable-method in preparation
>   for adding support for the BCM23550 SoC and its corresponding documentation, SoC dtsi
>   and the Sparrow board DTS file
> 
> - Jon adds MSI support to the PCI nodes, updates the secondary cores boot address for the B0
>   production revision of the Northstar Plus SoC, adds a DTS for the BCM958625HR board, another
>   one for the BCM958525XMC board, and finally adds the PL330 DMA controller to the NSP DTS
> 
> - Rafal enables the SPI NOR flash on dual flash systems (NAND + SPI) on the BCM5301x SoCs
>   and devices
> 
> - Florian adds support for the BCM5301x built-in Ethernet switch by adding nodes for the
>   Gigabit MAC controllers and the Switch Register Access block, and finally updates the
>   SmartRG SR-400AC board with its switch port layout
> 

Good tag text, thanks! Merged.


-Olof

[GIT PULL 4/7] Broadcom devicetree-arm64 changes for 4.8 Part 1

[Florian Fainelli]

The following changes since commit 1a695a905c18548062509178b98bc91e67510864:

  Linux 4.7-rc1 (2016-05-29 09:29:24 -0700)

are available in the git repository at:

  http://github.com/Broadcom/stblinux.git tags/arm-soc/for-4.8/devicetree-arm64

for you to fetch changes up to 5dcc9c7618dff61de243ca9bbac7de18ef92f49b:

  arm64: dts: NS2: Add CCI-400 PMU support (2016-05-31 11:00:28 -0700)

----------------------------------------------------------------
This pull request contains Device Tree changes for Broadcom ARM64-based SoCS:

- Anup adds nodes for the AHCI and SATA3 PHY peripherals to the Northstar2 SoCs

- Dhanajay enables pinctrl for the Northstar2 SoCs

- Jon Mason enables all of the UART peripherals found in the NS2 SVK and
  finally adds the CCI-400 and PMU nodes

----------------------------------------------------------------
Anup Patel (2):
      dt-bindings: ata: add compatible string for iProc AHCI controller
      arm64: dts: Add SATA3 AHCI and SATA3 PHY DT nodes for NS2

Jon Mason (2):
      arm64: dts: NS2: Add all of the UARTs
      arm64: dts: NS2: Add CCI-400 PMU support

Yendapally Reddy Dhananjaya Reddy (2):
      arm64: dts: enable pinctrl for Broadcom NS2 SoC
      arm64: dts: Enable GPIO for Broadcom NS2 SoC

 .../devicetree/bindings/ata/ahci-platform.txt      |   1 +
 arch/arm64/boot/dts/broadcom/ns2-svk.dts           |  37 +++++++
 arch/arm64/boot/dts/broadcom/ns2.dtsi              | 119 +++++++++++++++++++++
 3 files changed, 157 insertions(+)

[GIT PULL 4/7] Broadcom devicetree-arm64 changes for 4.8 Part 1

[Olof Johansson]

On Thu, Jun 16, 2016 at 06:56:12PM -0700, Florian Fainelli wrote:
> The following changes since commit 1a695a905c18548062509178b98bc91e67510864:
> 
>   Linux 4.7-rc1 (2016-05-29 09:29:24 -0700)
> 
> are available in the git repository at:
> 
>   http://github.com/Broadcom/stblinux.git tags/arm-soc/for-4.8/devicetree-arm64
> 
> for you to fetch changes up to 5dcc9c7618dff61de243ca9bbac7de18ef92f49b:
> 
>   arm64: dts: NS2: Add CCI-400 PMU support (2016-05-31 11:00:28 -0700)
> 
> ----------------------------------------------------------------
> This pull request contains Device Tree changes for Broadcom ARM64-based SoCS:
> 
> - Anup adds nodes for the AHCI and SATA3 PHY peripherals to the Northstar2 SoCs
> 
> - Dhanajay enables pinctrl for the Northstar2 SoCs
> 
> - Jon Mason enables all of the UART peripherals found in the NS2 SVK and
>   finally adds the CCI-400 and PMU nodes

Merged, thanks.


-Olof

[GIT PULL 5/7] Broadcom maintainers changes for 4.8 Part 1

[Florian Fainelli]

The following changes since commit 1a695a905c18548062509178b98bc91e67510864:

  Linux 4.7-rc1 (2016-05-29 09:29:24 -0700)

are available in the git repository at:

  http://github.com/Broadcom/stblinux.git tags/arm-soc/for-4.8/maintainers

for you to fetch changes up to f6d925c8f8bb2e01c16dd5cd0e3d773beb84554d:

  MAINTAINERS: Update entry for BCM5301X ARM (2016-06-10 11:30:24 -0700)

----------------------------------------------------------------
This pull request contains MAINTAINERS file updates for Broadcom SoCs:

- Rafal updates the BCM5301x entry wih the typical Broadcom mailing-list

----------------------------------------------------------------
Rafa? Mi?ecki (1):
      MAINTAINERS: Update entry for BCM5301X ARM

 MAINTAINERS | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

[GIT PULL 5/7] Broadcom maintainers changes for 4.8 Part 1

[Olof Johansson]

On Thu, Jun 16, 2016 at 06:56:13PM -0700, Florian Fainelli wrote:
> The following changes since commit 1a695a905c18548062509178b98bc91e67510864:
> 
>   Linux 4.7-rc1 (2016-05-29 09:29:24 -0700)
> 
> are available in the git repository at:
> 
>   http://github.com/Broadcom/stblinux.git tags/arm-soc/for-4.8/maintainers
> 
> for you to fetch changes up to f6d925c8f8bb2e01c16dd5cd0e3d773beb84554d:
> 
>   MAINTAINERS: Update entry for BCM5301X ARM (2016-06-10 11:30:24 -0700)
> 
> ----------------------------------------------------------------
> This pull request contains MAINTAINERS file updates for Broadcom SoCs:
> 
> - Rafal updates the BCM5301x entry wih the typical Broadcom mailing-list
> 
> ----------------------------------------------------------------
> Rafa?? Mi??ecki (1):
>       MAINTAINERS: Update entry for BCM5301X ARM

Is bcm-kernel-feedback-list at broadcom.com a list that the public can subscribe
to, or is it an internal list that the team is on?

If it's the latter then it shouldn't be a mailing list in the maintainers
file. There's a dual purpose to the L: entries -- one is where to cc the
patches to, the other is what list to figure out how to subscribe to if you
care about patches for that platform...


Not merged until the above is clarified.


-Olof

[GIT PULL 5/7] Broadcom maintainers changes for 4.8 Part 1

[Rafał Miłecki]

On 20 June 2016 at 07:51, Olof Johansson <olof@lixom.net> wrote:
> On Thu, Jun 16, 2016 at 06:56:13PM -0700, Florian Fainelli wrote:
>> The following changes since commit 1a695a905c18548062509178b98bc91e67510864:
>>
>>   Linux 4.7-rc1 (2016-05-29 09:29:24 -0700)
>>
>> are available in the git repository at:
>>
>>   http://github.com/Broadcom/stblinux.git tags/arm-soc/for-4.8/maintainers
>>
>> for you to fetch changes up to f6d925c8f8bb2e01c16dd5cd0e3d773beb84554d:
>>
>>   MAINTAINERS: Update entry for BCM5301X ARM (2016-06-10 11:30:24 -0700)
>>
>> ----------------------------------------------------------------
>> This pull request contains MAINTAINERS file updates for Broadcom SoCs:
>>
>> - Rafal updates the BCM5301x entry wih the typical Broadcom mailing-list
>>
>> ----------------------------------------------------------------
>> Rafa?? Mi??ecki (1):
>>       MAINTAINERS: Update entry for BCM5301X ARM
>
> Is bcm-kernel-feedback-list at broadcom.com a list that the public can subscribe
> to, or is it an internal list that the team is on?
>
> If it's the latter then it shouldn't be a mailing list in the maintainers
> file. There's a dual purpose to the L: entries -- one is where to cc the
> patches to, the other is what list to figure out how to subscribe to if you
> care about patches for that platform...
>
> Not merged until the above is clarified.

I was asked by Florian to add bcm-kernel-feedback-list@ but indeed he
didn't specify if this should be L: entry.
[21:24:43] <[florian]> rmilecki: also submit a patch that includes
bcm-kernel-feedback-list at broadcom.com in the MAINTAINERS file for
BCM5310X
[21:36:51] <rmilecki> [florian]: I wasn't sure if I'm supposed to do that
[21:36:53] <rmilecki> i can try I guess

I'm afraid this mailing list is closed. Would M: entry work for it?

-- 
Rafa?

[GIT PULL 5/7] Broadcom maintainers changes for 4.8 Part 1

[Arnd Bergmann]

On Monday, June 20, 2016 9:35:53 AM CEST Rafa? Mi?ecki wrote:
> 
> I was asked by Florian to add bcm-kernel-feedback-list@ but indeed he
> didn't specify if this should be L: entry.
> [21:24:43] <[florian]> rmilecki: also submit a patch that includes
> bcm-kernel-feedback-list at broadcom.com in the MAINTAINERS file for
> BCM5310X
> [21:36:51] <rmilecki> [florian]: I wasn't sure if I'm supposed to do that
> [21:36:53] <rmilecki> i can try I guess
> 
> I'm afraid this mailing list is closed. Would M: entry work for it?


I think M: is better, we have a couple of examples like that (x86 at kernel.org,
Dept-GELinuxNICDev at qlogic.com, linux-wimax at intel.com, ...).

	Arnd

[GIT PULL 5/7] Broadcom maintainers changes for 4.8 Part 1

[Olof Johansson]

On Mon, Jun 20, 2016 at 12:47 AM, Arnd Bergmann <arnd@arndb.de> wrote:
> On Monday, June 20, 2016 9:35:53 AM CEST Rafa? Mi?ecki wrote:
>>
>> I was asked by Florian to add bcm-kernel-feedback-list@ but indeed he
>> didn't specify if this should be L: entry.
>> [21:24:43] <[florian]> rmilecki: also submit a patch that includes
>> bcm-kernel-feedback-list at broadcom.com in the MAINTAINERS file for
>> BCM5310X
>> [21:36:51] <rmilecki> [florian]: I wasn't sure if I'm supposed to do that
>> [21:36:53] <rmilecki> i can try I guess
>>
>> I'm afraid this mailing list is closed. Would M: entry work for it?
>
>
> I think M: is better, we have a couple of examples like that (x86 at kernel.org,
> Dept-GELinuxNICDev at qlogic.com, linux-wimax at intel.com, ...).

Yep, having it as a M: entry would be fine with me as well. Please
respin the patch/branch -- we can apply a patch directly instead of
doing a merge if that's easier for you.


-Olof

[GIT PULL 5/7] Broadcom maintainers changes for 4.8 Part 1

[Scott Branden]

Hi Olof/Rafal

On 16-06-20 08:30 AM, Olof Johansson wrote:
> On Mon, Jun 20, 2016 at 12:47 AM, Arnd Bergmann <arnd@arndb.de> wrote:
>> On Monday, June 20, 2016 9:35:53 AM CEST Rafa? Mi?ecki wrote:
>>>
>>> I was asked by Florian to add bcm-kernel-feedback-list@ but indeed he
>>> didn't specify if this should be L: entry.
>>> [21:24:43] <[florian]> rmilecki: also submit a patch that includes
>>> bcm-kernel-feedback-list at broadcom.com in the MAINTAINERS file for
>>> BCM5310X
>>> [21:36:51] <rmilecki> [florian]: I wasn't sure if I'm supposed to do that
>>> [21:36:53] <rmilecki> i can try I guess
>>>
>>> I'm afraid this mailing list is closed. Would M: entry work for it?
>>
>>
>> I think M: is better, we have a couple of examples like that (x86 at kernel.org,
>> Dept-GELinuxNICDev at qlogic.com, linux-wimax at intel.com, ...).
>
> Yep, having it as a M: entry would be fine with me as well. Please
> respin the patch/branch -- we can apply a patch directly instead of
> doing a merge if that's easier for you.

If M: is supposed to be used for bcm-kernel-feedback-list then a new 
patch applied to multiple locations in the MAINTAINERS file would solve 
the problem.

>
>
> -Olof
>

Regards,
  Scott

[GIT PULL 6/7] Broadcom defconfig changes for 4.8 Part 1

[Florian Fainelli]

The following changes since commit 1a695a905c18548062509178b98bc91e67510864:

  Linux 4.7-rc1 (2016-05-29 09:29:24 -0700)

are available in the git repository at:

  http://github.com/Broadcom/stblinux.git tags/arm-soc/for-4.8/defconfig

for you to fetch changes up to 41463c3e6eae3dfa4377069966ed02b4ba378e79:

  ARM: Remove bcm_defconfig (2016-06-16 13:40:49 -0700)

----------------------------------------------------------------
This pull request contains defconfig changes for Broadcom ARM-based SoCs:

- Florian enables support for the BCM63xx DSL SoCs basic peripherals, enables
  the networking subsystems for Set Top Box SoCs, enables the PWM, watchdog and
  the AHCI controller and SATA PHY drivers

- Florian removes the bcm_defconfig file which is no longer useful and updates
  multi_v7_defconfig to include the Kona watchdog to provide proper reboot for the
  Broadcom Kona platforms

Please note that Tejun Heo has queued a patch which renames AHCI_BRCMSTB into
AHCI_BRCM, to avoid two patches in a row, we just enable AHCI_BRCM to be future
proof

----------------------------------------------------------------
Florian Fainelli (7):
      ARM: multi_v7_defconfig: Enable BCM63xx
      ARM: multi_v7_defconfig: Enable BRCMSTB networking
      ARM: multi_v7_defconfig: Enable Broadcom AHCI
      ARM: multi_v7_defconfig: Enable BCM7038 Watchdog
      ARM: multi_v7_defconfig: Enable Broadcom STB PWM
      ARM: multi_v7_defconfig: Enable Broadcom Kona watchdog
      ARM: Remove bcm_defconfig

 arch/arm/configs/bcm_defconfig      | 141 ------------------------------------
 arch/arm/configs/multi_v7_defconfig |  13 ++++
 2 files changed, 13 insertions(+), 141 deletions(-)
 delete mode 100644 arch/arm/configs/bcm_defconfig

[GIT PULL 6/7] Broadcom defconfig changes for 4.8 Part 1

[Olof Johansson]

On Thu, Jun 16, 2016 at 06:56:14PM -0700, Florian Fainelli wrote:
> The following changes since commit 1a695a905c18548062509178b98bc91e67510864:
> 
>   Linux 4.7-rc1 (2016-05-29 09:29:24 -0700)
> 
> are available in the git repository at:
> 
>   http://github.com/Broadcom/stblinux.git tags/arm-soc/for-4.8/defconfig
> 
> for you to fetch changes up to 41463c3e6eae3dfa4377069966ed02b4ba378e79:
> 
>   ARM: Remove bcm_defconfig (2016-06-16 13:40:49 -0700)
> 
> ----------------------------------------------------------------
> This pull request contains defconfig changes for Broadcom ARM-based SoCs:
> 
> - Florian enables support for the BCM63xx DSL SoCs basic peripherals, enables
>   the networking subsystems for Set Top Box SoCs, enables the PWM, watchdog and
>   the AHCI controller and SATA PHY drivers
> 
> - Florian removes the bcm_defconfig file which is no longer useful and updates
>   multi_v7_defconfig to include the Kona watchdog to provide proper reboot for the
>   Broadcom Kona platforms
> 
> Please note that Tejun Heo has queued a patch which renames AHCI_BRCMSTB into
> AHCI_BRCM, to avoid two patches in a row, we just enable AHCI_BRCM to be future
> proof

So, you say that bcm_defconfig is no longer useful. While I'm happy to see the
number of defconfigs go down, I'd like to clarify that we do still see per-SoC
defconfigs somewhat useful, in that they are a lot closer to what someone would
want to use for defconfig in a product kernel based on the SoC. It's easier to
start from the SoC-specific defconfig and remove pieces that aren't needed than
to start from multi_v7_defconfig.

That being said, I'm happy to remove it if you think that's what works best for
your platform.

Merged into next/defconfig.


-Olof

[GIT PULL 6/7] Broadcom defconfig changes for 4.8 Part 1

[Scott Branden]

Hi Olof,

On 16-06-19 10:54 PM, Olof Johansson wrote:
> On Thu, Jun 16, 2016 at 06:56:14PM -0700, Florian Fainelli wrote:
>> The following changes since commit 1a695a905c18548062509178b98bc91e67510864:
>>
>>    Linux 4.7-rc1 (2016-05-29 09:29:24 -0700)
>>
>> are available in the git repository at:
>>
>>    http://github.com/Broadcom/stblinux.git tags/arm-soc/for-4.8/defconfig
>>
>> for you to fetch changes up to 41463c3e6eae3dfa4377069966ed02b4ba378e79:
>>
>>    ARM: Remove bcm_defconfig (2016-06-16 13:40:49 -0700)
>>
>> ----------------------------------------------------------------
>> This pull request contains defconfig changes for Broadcom ARM-based SoCs:
>>
>> - Florian enables support for the BCM63xx DSL SoCs basic peripherals, enables
>>    the networking subsystems for Set Top Box SoCs, enables the PWM, watchdog and
>>    the AHCI controller and SATA PHY drivers
>>
>> - Florian removes the bcm_defconfig file which is no longer useful and updates
>>    multi_v7_defconfig to include the Kona watchdog to provide proper reboot for the
>>    Broadcom Kona platforms
>>
>> Please note that Tejun Heo has queued a patch which renames AHCI_BRCMSTB into
>> AHCI_BRCM, to avoid two patches in a row, we just enable AHCI_BRCM to be future
>> proof
>
> So, you say that bcm_defconfig is no longer useful. While I'm happy to see the
> number of defconfigs go down, I'd like to clarify that we do still see per-SoC
> defconfigs somewhat useful, in that they are a lot closer to what someone would
> want to use for defconfig in a product kernel based on the SoC. It's easier to
> start from the SoC-specific defconfig and remove pieces that aren't needed than
> to start from multi_v7_defconfig.
I completely agree that per-SoC defconfigs are extremely useful. I 
attempted to do so for Cygnus and would like to for other Broadcom SoCs 
as well. Unfortunately Arnd's policy was one defconfig per company. This 
prevents use from doing so. Broadcom has a variety of SoCs and families. 
Some share technology, others are entirely different. On the projects I 
work with we don't use multi_v7_defconfig nor do our customers. We use 
per SoC defconfigs.

So, as it stands bcm_defconfig is of little use to us. We are able to 
upstream everything into the kernel except for the defconfig file. We 
are forced to maintain these internally. Yet we are able to upstream dts 
files which are per board...
>
> That being said, I'm happy to remove it if you think that's what works best for
> your platform.
>
> Merged into next/defconfig.
>
>
> -Olof
>
Regards,
  Scott

[GIT PULL 6/7] Broadcom defconfig changes for 4.8 Part 1

[Florian Fainelli]

On 06/20/2016 02:43 PM, Scott Branden wrote:
> Hi Olof,
> 
> On 16-06-19 10:54 PM, Olof Johansson wrote:
>> On Thu, Jun 16, 2016 at 06:56:14PM -0700, Florian Fainelli wrote:
>>> The following changes since commit
>>> 1a695a905c18548062509178b98bc91e67510864:
>>>
>>>    Linux 4.7-rc1 (2016-05-29 09:29:24 -0700)
>>>
>>> are available in the git repository at:
>>>
>>>    http://github.com/Broadcom/stblinux.git
>>> tags/arm-soc/for-4.8/defconfig
>>>
>>> for you to fetch changes up to 41463c3e6eae3dfa4377069966ed02b4ba378e79:
>>>
>>>    ARM: Remove bcm_defconfig (2016-06-16 13:40:49 -0700)
>>>
>>> ----------------------------------------------------------------
>>> This pull request contains defconfig changes for Broadcom ARM-based
>>> SoCs:
>>>
>>> - Florian enables support for the BCM63xx DSL SoCs basic peripherals,
>>> enables
>>>    the networking subsystems for Set Top Box SoCs, enables the PWM,
>>> watchdog and
>>>    the AHCI controller and SATA PHY drivers
>>>
>>> - Florian removes the bcm_defconfig file which is no longer useful
>>> and updates
>>>    multi_v7_defconfig to include the Kona watchdog to provide proper
>>> reboot for the
>>>    Broadcom Kona platforms
>>>
>>> Please note that Tejun Heo has queued a patch which renames
>>> AHCI_BRCMSTB into
>>> AHCI_BRCM, to avoid two patches in a row, we just enable AHCI_BRCM to
>>> be future
>>> proof
>>
>> So, you say that bcm_defconfig is no longer useful. While I'm happy to
>> see the
>> number of defconfigs go down, I'd like to clarify that we do still see
>> per-SoC
>> defconfigs somewhat useful, in that they are a lot closer to what
>> someone would
>> want to use for defconfig in a product kernel based on the SoC. It's
>> easier to
>> start from the SoC-specific defconfig and remove pieces that aren't
>> needed than
>> to start from multi_v7_defconfig.
> I completely agree that per-SoC defconfigs are extremely useful. I
> attempted to do so for Cygnus and would like to for other Broadcom SoCs
> as well. Unfortunately Arnd's policy was one defconfig per company. This
> prevents use from doing so. Broadcom has a variety of SoCs and families.
> Some share technology, others are entirely different. On the projects I
> work with we don't use multi_v7_defconfig nor do our customers. We use
> per SoC defconfigs.
> 
> So, as it stands bcm_defconfig is of little use to us. We are able to
> upstream everything into the kernel except for the defconfig file. We
> are forced to maintain these internally. Yet we are able to upstream dts
> files which are per board...

I really think the job of building an appropriate .config file for your
platform belongs in the build system you are utilizing. There could be
user-visible option that you allow people to turn on/off (e.g: kernels'
frace along with user-space profiling tools etc.), and in general build
systems enable a bunch of generic options shared across all targets they
support, and they just maintain relevant fragments for the specific
targets you build for, making the defconfig more or less contained
within the build system, and under control.

Maintaining a defconfig file is both boring and a great deal of pain
when trying to resolve conflicts, and keep in mind that the upstream
community can nitpick on every single change you enable/disable in there ;)
-- 
Florian

[GIT PULL 6/7] Broadcom defconfig changes for 4.8 Part 1

[Olof Johansson]

On Mon, Jun 20, 2016 at 2:43 PM, Scott Branden
<scott.branden@broadcom.com> wrote:
> Hi Olof,
>
>
> On 16-06-19 10:54 PM, Olof Johansson wrote:
>>
>> On Thu, Jun 16, 2016 at 06:56:14PM -0700, Florian Fainelli wrote:
>>>
>>> The following changes since commit
>>> 1a695a905c18548062509178b98bc91e67510864:
>>>
>>>    Linux 4.7-rc1 (2016-05-29 09:29:24 -0700)
>>>
>>> are available in the git repository at:
>>>
>>>    http://github.com/Broadcom/stblinux.git tags/arm-soc/for-4.8/defconfig
>>>
>>> for you to fetch changes up to 41463c3e6eae3dfa4377069966ed02b4ba378e79:
>>>
>>>    ARM: Remove bcm_defconfig (2016-06-16 13:40:49 -0700)
>>>
>>> ----------------------------------------------------------------
>>> This pull request contains defconfig changes for Broadcom ARM-based SoCs:
>>>
>>> - Florian enables support for the BCM63xx DSL SoCs basic peripherals,
>>> enables
>>>    the networking subsystems for Set Top Box SoCs, enables the PWM,
>>> watchdog and
>>>    the AHCI controller and SATA PHY drivers
>>>
>>> - Florian removes the bcm_defconfig file which is no longer useful and
>>> updates
>>>    multi_v7_defconfig to include the Kona watchdog to provide proper
>>> reboot for the
>>>    Broadcom Kona platforms
>>>
>>> Please note that Tejun Heo has queued a patch which renames AHCI_BRCMSTB
>>> into
>>> AHCI_BRCM, to avoid two patches in a row, we just enable AHCI_BRCM to be
>>> future
>>> proof
>>
>>
>> So, you say that bcm_defconfig is no longer useful. While I'm happy to see
>> the
>> number of defconfigs go down, I'd like to clarify that we do still see
>> per-SoC
>> defconfigs somewhat useful, in that they are a lot closer to what someone
>> would
>> want to use for defconfig in a product kernel based on the SoC. It's
>> easier to
>> start from the SoC-specific defconfig and remove pieces that aren't needed
>> than
>> to start from multi_v7_defconfig.
>
> I completely agree that per-SoC defconfigs are extremely useful. I attempted
> to do so for Cygnus and would like to for other Broadcom SoCs as well.
> Unfortunately Arnd's policy was one defconfig per company. This prevents use
> from doing so. Broadcom has a variety of SoCs and families. Some share
> technology, others are entirely different. On the projects I work with we
> don't use multi_v7_defconfig nor do our customers. We use per SoC
> defconfigs.

Yeah, I'm with Arnd on this in general; we can't do a crazy number of
defconfigs -- which is why I said it's a starting point for further
paring down. Still, given the variety of platforms from Broadcom it's
likely too broad to be useful. Removing it makes sense.

> So, as it stands bcm_defconfig is of little use to us. We are able to
> upstream everything into the kernel except for the defconfig file. We are
> forced to maintain these internally. Yet we are able to upstream dts files
> which are per board...

There's a huge difference in the cost of carrying a defconfig vs a dts
file. A dts file is very cheap to compile and carry, while each
defconfig adds a significant amount of time spent on build coverage.


-Olof

[GIT PULL 6/7] Broadcom defconfig changes for 4.8 Part 1

[Scott Branden]

HI Olof,

On 16-06-20 03:04 PM, Olof Johansson wrote:
> On Mon, Jun 20, 2016 at 2:43 PM, Scott Branden
> <scott.branden@broadcom.com> wrote:
>> Hi Olof,
>>
>>
>> On 16-06-19 10:54 PM, Olof Johansson wrote:
>>>
>>> On Thu, Jun 16, 2016 at 06:56:14PM -0700, Florian Fainelli wrote:
>>>>
>>>> The following changes since commit
>>>> 1a695a905c18548062509178b98bc91e67510864:
>>>>
>>>>     Linux 4.7-rc1 (2016-05-29 09:29:24 -0700)
>>>>
>>>> are available in the git repository at:
>>>>
>>>>     http://github.com/Broadcom/stblinux.git tags/arm-soc/for-4.8/defconfig
>>>>
>>>> for you to fetch changes up to 41463c3e6eae3dfa4377069966ed02b4ba378e79:
>>>>
>>>>     ARM: Remove bcm_defconfig (2016-06-16 13:40:49 -0700)
>>>>
>>>> ----------------------------------------------------------------
>>>> This pull request contains defconfig changes for Broadcom ARM-based SoCs:
>>>>
>>>> - Florian enables support for the BCM63xx DSL SoCs basic peripherals,
>>>> enables
>>>>     the networking subsystems for Set Top Box SoCs, enables the PWM,
>>>> watchdog and
>>>>     the AHCI controller and SATA PHY drivers
>>>>
>>>> - Florian removes the bcm_defconfig file which is no longer useful and
>>>> updates
>>>>     multi_v7_defconfig to include the Kona watchdog to provide proper
>>>> reboot for the
>>>>     Broadcom Kona platforms
>>>>
>>>> Please note that Tejun Heo has queued a patch which renames AHCI_BRCMSTB
>>>> into
>>>> AHCI_BRCM, to avoid two patches in a row, we just enable AHCI_BRCM to be
>>>> future
>>>> proof
>>>
>>>
>>> So, you say that bcm_defconfig is no longer useful. While I'm happy to see
>>> the
>>> number of defconfigs go down, I'd like to clarify that we do still see
>>> per-SoC
>>> defconfigs somewhat useful, in that they are a lot closer to what someone
>>> would
>>> want to use for defconfig in a product kernel based on the SoC. It's
>>> easier to
>>> start from the SoC-specific defconfig and remove pieces that aren't needed
>>> than
>>> to start from multi_v7_defconfig.
>>
>> I completely agree that per-SoC defconfigs are extremely useful. I attempted
>> to do so for Cygnus and would like to for other Broadcom SoCs as well.
>> Unfortunately Arnd's policy was one defconfig per company. This prevents use
>> from doing so. Broadcom has a variety of SoCs and families. Some share
>> technology, others are entirely different. On the projects I work with we
>> don't use multi_v7_defconfig nor do our customers. We use per SoC
>> defconfigs.
>
> Yeah, I'm with Arnd on this in general; we can't do a crazy number of
> defconfigs -- which is why I said it's a starting point for further
> paring down. Still, given the variety of platforms from Broadcom it's
> likely too broad to be useful. Removing it makes sense.

I have been attempting to add Kconfig defaults to new drivers we are 
upstreaming.  That way if a driver is used for an SoC family you simply 
can select the SoC family and voila the drivers are all default selected 
for you.  An added benefit is we don't need to submit patches for 
multi_v7_defconfig every time we upstream a new driver.  The drivers are 
automatically selected via the Kconfig.  If this was promoted in the 
Kconfig files then all the other SoC specific defconfig files could be 
removed.  All information about the SoC would be contained in the kernel 
instead of being maintained elsewhere.  The user could generate any 
defconfig for their specific SoC(s) and the only paring down to be done 
would be limited to removing drivers that they don't use on their 
specific SoC.  I have not added defaults for existing drivers - but if 
acceptable may do so at some time.  This may make a long list of 
defaults for popular drivers, but it makes things far more maintainable 
than multiple defconfigs or burying SoC kernel specifics in a build system.

>
>> So, as it stands bcm_defconfig is of little use to us. We are able to
>> upstream everything into the kernel except for the defconfig file. We are
>> forced to maintain these internally. Yet we are able to upstream dts files
>> which are per board...
>
> There's a huge difference in the cost of carrying a defconfig vs a dts
> file. A dts file is very cheap to compile and carry, while each
> defconfig adds a significant amount of time spent on build coverage.
Perhaps the build coverage should only be for multi_v7_defconfig and a 
big endian build version of it?
>
>
> -Olof
>

Thanks,
  Scott

[GIT PULL 7/7] Broadcom drivers changes for 4.8 Part 1

[Florian Fainelli]

The following changes since commit 1a695a905c18548062509178b98bc91e67510864:

  Linux 4.7-rc1 (2016-05-29 09:29:24 -0700)

are available in the git repository at:

  http://github.com/Broadcom/stblinux.git tags/arm-soc/for-4.8/drivers

for you to fetch changes up to a536bcc931ed5c047100c3a28f521283749d3b9a:

  soc: brcmstb: fix warning from missing include (2016-06-07 13:53:42 -0700)

----------------------------------------------------------------
This pull request contains drivers related changes for Broadcom SoCs:

- Florian moves drivers/soc/brcmstb to drivers/soc/bcm/brcmstb to be consistent with
  how other SoCs are doing it

- Chris provides a reset driver which is common to the BCM21664 and BCM23550 SoCs

- Ben fixes a warning by providing the appropriate include file

----------------------------------------------------------------
Ben Dooks (1):
      soc: brcmstb: fix warning from missing include

Chris Brand (1):
      power: Introduce Broadcom kona reset driver

Florian Fainelli (1):
      soc: Move brcmstb to bcm/brcmstb

 MAINTAINERS                             |  1 +
 drivers/power/reset/Kconfig             | 10 +++++
 drivers/power/reset/Makefile            |  1 +
 drivers/power/reset/brcm-kona-reset.c   | 73 +++++++++++++++++++++++++++++++++
 drivers/soc/Kconfig                     |  1 -
 drivers/soc/Makefile                    |  1 -
 drivers/soc/bcm/Kconfig                 | 15 +++++++
 drivers/soc/bcm/Makefile                |  1 +
 drivers/soc/{ => bcm}/brcmstb/Makefile  |  0
 drivers/soc/{ => bcm}/brcmstb/biuctrl.c |  1 +
 drivers/soc/{ => bcm}/brcmstb/common.c  |  0
 drivers/soc/brcmstb/Kconfig             | 10 -----
 12 files changed, 102 insertions(+), 12 deletions(-)
 create mode 100644 drivers/power/reset/brcm-kona-reset.c
 rename drivers/soc/{ => bcm}/brcmstb/Makefile (100%)
 rename drivers/soc/{ => bcm}/brcmstb/biuctrl.c (98%)
 rename drivers/soc/{ => bcm}/brcmstb/common.c (100%)
 delete mode 100644 drivers/soc/brcmstb/Kconfig

[GIT PULL 7/7] Broadcom drivers changes for 4.8 Part 1

[Olof Johansson]

On Thu, Jun 16, 2016 at 06:56:15PM -0700, Florian Fainelli wrote:
> The following changes since commit 1a695a905c18548062509178b98bc91e67510864:
> 
>   Linux 4.7-rc1 (2016-05-29 09:29:24 -0700)
> 
> are available in the git repository at:
> 
>   http://github.com/Broadcom/stblinux.git tags/arm-soc/for-4.8/drivers
> 
> for you to fetch changes up to a536bcc931ed5c047100c3a28f521283749d3b9a:
> 
>   soc: brcmstb: fix warning from missing include (2016-06-07 13:53:42 -0700)
> 
> ----------------------------------------------------------------
> This pull request contains drivers related changes for Broadcom SoCs:
> 
> - Florian moves drivers/soc/brcmstb to drivers/soc/bcm/brcmstb to be consistent with
>   how other SoCs are doing it
> 
> - Chris provides a reset driver which is common to the BCM21664 and BCM23550 SoCs
> 
> - Ben fixes a warning by providing the appropriate include file

Merged, thanks.


-Olof

[GIT PULL 1/7] Broadcom soc changes for 4.8 Part 1

[Olof Johansson]

On Thu, Jun 16, 2016 at 06:56:09PM -0700, Florian Fainelli wrote:
> The following changes since commit 1a695a905c18548062509178b98bc91e67510864:
> 
>   Linux 4.7-rc1 (2016-05-29 09:29:24 -0700)
> 
> are available in the git repository at:
> 
>   http://github.com/Broadcom/stblinux.git tags/arm-soc/for-4.8/soc
> 
> for you to fetch changes up to 423779cfd3ca73b9236e6eb798477f3a4f13355d:
> 
>   ARM: bcm: fix missing include of kona_l2_cache.h (2016-06-08 10:17:15 -0700)
> 
> ----------------------------------------------------------------
> This pull request contains SoC changes for Broadcom ARM-based SoCs:
> 
> - Chris prepares support for the BCM23550 by removing reset code in the
>   BCM21664 machine code since a proper drivers/power/reset driver is provided and
>   shared, he then adds a machine entry point for BCM23550 and updates the SMP
>   code to bring-up the secondary cores on BCM23550
> 
> - Ben fixes a warning in the Kona L2 SMC code by adding the missing include file
> 
> ----------------------------------------------------------------

Thanks, merged into next/soc.


-Olof