[GIT PULL 1/6] Broadcom soc changes for 4.14

[GIT PULL 1/6] Broadcom soc changes for 4.14

[Florian Fainelli]

The following changes since commit 5771a8c08880cdca3bfb4a3fc6d309d6bba20877:

  Linux v4.13-rc1 (2017-07-15 15:22:10 -0700)

are available in the git repository at:

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

for you to fetch changes up to e831871597aaa1f650b83f96b61858907c203b76:

  Merge tag 'bcm2835-soc-next-2017-08-15' into soc/next (2017-08-16 18:14:49 -0700)

----------------------------------------------------------------
This pull request contains Broadcom ARM-based SoC/Kconfig changes for 4.14,
please pull the following:

- Stefan moves the BCM2836 SMP bring-up code from the irqchip driver down to
  where it belongs under arch/arm/mach-bcm/. This requires us to merge parts
  of the devicetree/next branch because we depend on Eric's change that relocates
  the bcm2836/37 Device Tree files as well as the "enable-method" being correctly
  set in the Device Tree source files.

- Danilo removes the fixed clocks introduced earlier when we did not have a
  CPRMAN clock provider and in the process removes the init_machine callback
  since we no longer need it.

- Phil provides a fix for the SMP bring-up code to have a "sev" (and corresponding
  barrier) instruction in order to wake-up secondary cores. Future Rasperry Pi
  firmware(s) will depend on this.

----------------------------------------------------------------
Danilo Krummrich (1):
      clk: bcm2835: remove remains from stub clk driver

Eric Anholt (2):
      ARM: dts: bcm283x: Move the BCM2837 DT contents from arm64 to arm.
      Merge tag 'bcm2835-dt-next-2017-08-15' into HEAD

Florian Fainelli (3):
      ARM: dts: BCM53573: Add Broadcom BCM947189ACDBMR board support
      Merge tag 'bcm2835-dt-next-2017-08-07' into devicetree/next
      Merge tag 'bcm2835-soc-next-2017-08-15' into soc/next

Jon Mason (3):
      ARM: dts: NSP: Add dma-coherent to relevant DT entries
      ARM: dts: NSP: Rearrage USB entries
      ARM: dts: NSP: Add USB3 and USB3 PHY to NSP

Phil Elwell (1):
      ARM: bcm2836: Send event when onlining other cores

Rafa? Mi?ecki (2):
      ARM: dts: BCM5301X: Specify USB ports for each controller
      ARM: dts: BCM5301X: Specify USB ports for USB LEDs of few devices

Stefan Wahren (6):
      ARM: bcm283x: Define UART pinmuxing on board level
      dt-bindings: bcm: Add Raspberry Pi Zero W
      ARM: dts: bcm2835: Add Raspberry Pi Zero W
      dt-bindings: arm: add SMP enable-method for BCM2836
      ARM: dts: bcm283x: Add 32-bit enable method for SMP
      irqchip: bcm2836: Move SMP startup code to arch/arm

 .../devicetree/bindings/arm/bcm/brcm,bcm2835.txt   |   4 +
 Documentation/devicetree/bindings/arm/cpus.txt     |   1 +
 arch/arm/boot/dts/Makefile                         |   6 +-
 arch/arm/boot/dts/bcm-nsp.dtsi                     |  59 ++++++---
 arch/arm/boot/dts/bcm2835-rpi-a-plus.dts           |   6 +
 arch/arm/boot/dts/bcm2835-rpi-a.dts                |   6 +
 arch/arm/boot/dts/bcm2835-rpi-b-plus.dts           |   6 +
 arch/arm/boot/dts/bcm2835-rpi-b-rev2.dts           |   6 +
 arch/arm/boot/dts/bcm2835-rpi-b.dts                |   6 +
 arch/arm/boot/dts/bcm2835-rpi-zero-w.dts           | 139 +++++++++++++++++++++
 arch/arm/boot/dts/bcm2835-rpi-zero.dts             |   6 +
 arch/arm/boot/dts/bcm2835-rpi.dtsi                 |   2 +-
 arch/arm/boot/dts/bcm2836-rpi-2-b.dts              |   6 +
 arch/arm/boot/dts/bcm2836.dtsi                     |   1 +
 arch/arm/boot/dts/bcm2837-rpi-3-b.dts              |  52 +++++++-
 .../dts/broadcom => arm/boot/dts}/bcm2837.dtsi     |   1 +
 arch/arm/boot/dts/bcm4708-buffalo-wzr-1750dhp.dts  |   4 +
 arch/arm/boot/dts/bcm4708-netgear-r6250.dts        |   3 +
 arch/arm/boot/dts/bcm4708-smartrg-sr400ac.dts      |   6 +
 arch/arm/boot/dts/bcm47081-tplink-archer-c5-v2.dts |   4 +
 arch/arm/boot/dts/bcm4709-tplink-archer-c9-v1.dts  |   5 +
 arch/arm/boot/dts/bcm47094-dlink-dir-885l.dts      |   3 +
 arch/arm/boot/dts/bcm47094-luxul-xwr-3100.dts      |   3 +
 arch/arm/boot/dts/bcm5301x.dtsi                    |  34 +++++
 arch/arm/boot/dts/bcm947189acdbmr.dts              |  97 ++++++++++++++
 arch/arm/boot/dts/bcm958522er.dts                  |   8 ++
 arch/arm/boot/dts/bcm958525er.dts                  |   8 ++
 arch/arm/boot/dts/bcm958525xmc.dts                 |   8 ++
 arch/arm/boot/dts/bcm958622hr.dts                  |   8 ++
 arch/arm/boot/dts/bcm958623hr.dts                  |   8 ++
 arch/arm/boot/dts/bcm958625hr.dts                  |   8 ++
 arch/arm/boot/dts/bcm958625k.dts                   |   8 ++
 arch/arm/mach-bcm/Makefile                         |   5 +
 arch/arm/mach-bcm/board_bcm2835.c                  |   7 --
 arch/arm/mach-bcm/platsmp.c                        |  38 ++++++
 arch/arm64/boot/dts/broadcom/bcm2835-rpi.dtsi      |   1 -
 arch/arm64/boot/dts/broadcom/bcm2837-rpi-3-b.dts   |  42 +------
 .../boot/dts/broadcom/bcm283x-rpi-smsc9514.dtsi    |   1 -
 .../boot/dts/broadcom/bcm283x-rpi-usb-host.dtsi    |   1 -
 arch/arm64/boot/dts/broadcom/bcm283x.dtsi          |   1 -
 drivers/clk/bcm/clk-bcm2835-aux.c                  |   1 -
 drivers/clk/bcm/clk-bcm2835.c                      |  30 -----
 drivers/irqchip/irq-bcm2836.c                      |  79 +-----------
 include/linux/clk/bcm2835.h                        |  24 ----
 include/linux/irqchip/irq-bcm2836.h                |  70 +++++++++++
 45 files changed, 620 insertions(+), 202 deletions(-)
 create mode 100644 arch/arm/boot/dts/bcm2835-rpi-zero-w.dts
 rename arch/{arm64/boot/dts/broadcom => arm/boot/dts}/bcm2837.dtsi (96%)
 create mode 100644 arch/arm/boot/dts/bcm947189acdbmr.dts
 delete mode 120000 arch/arm64/boot/dts/broadcom/bcm2835-rpi.dtsi
 delete mode 120000 arch/arm64/boot/dts/broadcom/bcm283x-rpi-smsc9514.dtsi
 delete mode 120000 arch/arm64/boot/dts/broadcom/bcm283x-rpi-usb-host.dtsi
 delete mode 120000 arch/arm64/boot/dts/broadcom/bcm283x.dtsi
 delete mode 100644 include/linux/clk/bcm2835.h
 create mode 100644 include/linux/irqchip/irq-bcm2836.h

[GIT PULL 2/6] Broadcom devicetree changes for 4.14

[Florian Fainelli]

The following changes since commit 5771a8c08880cdca3bfb4a3fc6d309d6bba20877:

  Linux v4.13-rc1 (2017-07-15 15:22:10 -0700)

are available in the git repository at:

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

for you to fetch changes up to 0173b2cd6948b5b96ac4e8dbc3bcb4dd0b45c296:

  ARM: BCM53573: Specify ports for USB LED for Tenda AC9 (2017-08-17 10:18:07 -0700)

----------------------------------------------------------------
This pull request contains Broadcom ARM-based SoCs Device Tree changes for
4.14, please pull the following:

- Eric moves the bcm2837 DT file from arm64 to arm because it created a maintenance
  problem and would have required either duplication or cross merges

- Stefan changes how the pinmuxing is defined and pushes it at the board level
  to support Raspberry Pi Zero Wireless. He then adds supports for the actual
  Raspberry Pi Zero Wireless board along with binding documentation. Stefan
  also defines a proper SMP enable-method property and binding for BCM2836
  (Raspbery Pi 2)

- Rafal describes the BCM5301X USB ports correctly in Device Tree such that
  it becomes possible to assign them to specific LED triggers (e.g: USB activity).
  He does the same thing for BCM53573 and defines default LED triggers for USB.

- Jon provides a fix for Northstar Plus which consists in correctly defining
  the "dma-coherent" property for peripherals which are DMA coherent. He also
  does a bit of re-arrangement of the USB DT nodes and finally adds USB 3 PHY
  and host controller support for NorthStar Plus

- Florian adds support for Broadcom's BCM947189ACDBMR reference board which is
  based on BCM47182/53573 and which supports external MoCA (BCM6802)

- Ray fixes the wrong UART2 base address for Cygnus

- Scott moves the v3d node in the proper unit address order and defines the correct
  UART alias for the BCM91130_entphn reference board to be UART3

- Jason adds the DT node for the Cygnus Cortex-A9 Performance Monitoring Unit

- Jonathan adds a bunch of additional peripherals to the Cygnus DTS include file:
  SDHCI, Keypad, SPI, DMA and pinmux configurations

- Raveendra adds the Cygnus OHCI and EHCI Device Tree nodes

----------------------------------------------------------------
Eric Anholt (1):
      ARM: dts: bcm283x: Move the BCM2837 DT contents from arm64 to arm.

Florian Fainelli (3):
      ARM: dts: BCM53573: Add Broadcom BCM947189ACDBMR board support
      Merge tag 'bcm2835-dt-next-2017-08-07' into devicetree/next
      Merge tag 'bcm2835-dt-next-2017-08-15' into devicetree/next

Jason Uy (1):
      ARM: dts: cygnus: Enable Performance Monitoring Unit

Jon Mason (3):
      ARM: dts: NSP: Add dma-coherent to relevant DT entries
      ARM: dts: NSP: Rearrage USB entries
      ARM: dts: NSP: Add USB3 and USB3 PHY to NSP

Jonathan Richardson (1):
      ARM: dts: cygnus: Add additional peripherals to dtsi

Rafa? Mi?ecki (3):
      ARM: dts: BCM5301X: Specify USB ports for each controller
      ARM: dts: BCM5301X: Specify USB ports for USB LEDs of few devices
      ARM: BCM53573: Specify ports for USB LED for Tenda AC9

Raveendra Padasalagi (1):
      ARM: dts: cygnus: Add generic-ehci/ohci nodes

Ray Jui (1):
      ARM: dts: cygnus: Fix incorrect UART2 register base

Scott Branden (2):
      ARM: dts: cygnus: place v3d in proper address ordered location
      ARM: dts: cygnus: add serial0 alias for uart3 on bcm91130_entphn

Stefan Wahren (5):
      ARM: bcm283x: Define UART pinmuxing on board level
      dt-bindings: bcm: Add Raspberry Pi Zero W
      ARM: dts: bcm2835: Add Raspberry Pi Zero W
      dt-bindings: arm: add SMP enable-method for BCM2836
      ARM: dts: bcm283x: Add 32-bit enable method for SMP

 .../devicetree/bindings/arm/bcm/brcm,bcm2835.txt   |   4 +
 Documentation/devicetree/bindings/arm/cpus.txt     |   1 +
 arch/arm/boot/dts/Makefile                         |   6 +-
 arch/arm/boot/dts/bcm-cygnus.dtsi                  | 149 +++++++++++++++++++--
 arch/arm/boot/dts/bcm-nsp.dtsi                     |  59 ++++++--
 arch/arm/boot/dts/bcm2835-rpi-a-plus.dts           |   6 +
 arch/arm/boot/dts/bcm2835-rpi-a.dts                |   6 +
 arch/arm/boot/dts/bcm2835-rpi-b-plus.dts           |   6 +
 arch/arm/boot/dts/bcm2835-rpi-b-rev2.dts           |   6 +
 arch/arm/boot/dts/bcm2835-rpi-b.dts                |   6 +
 arch/arm/boot/dts/bcm2835-rpi-zero-w.dts           | 139 +++++++++++++++++++
 arch/arm/boot/dts/bcm2835-rpi-zero.dts             |   6 +
 arch/arm/boot/dts/bcm2835-rpi.dtsi                 |   2 +-
 arch/arm/boot/dts/bcm2836-rpi-2-b.dts              |   6 +
 arch/arm/boot/dts/bcm2836.dtsi                     |   1 +
 arch/arm/boot/dts/bcm2837-rpi-3-b.dts              |  52 ++++++-
 .../dts/broadcom => arm/boot/dts}/bcm2837.dtsi     |   1 +
 arch/arm/boot/dts/bcm4708-buffalo-wzr-1750dhp.dts  |   4 +
 arch/arm/boot/dts/bcm4708-netgear-r6250.dts        |   3 +
 arch/arm/boot/dts/bcm4708-smartrg-sr400ac.dts      |   6 +
 arch/arm/boot/dts/bcm47081-tplink-archer-c5-v2.dts |   4 +
 arch/arm/boot/dts/bcm4709-tplink-archer-c9-v1.dts  |   5 +
 arch/arm/boot/dts/bcm47094-dlink-dir-885l.dts      |   3 +
 arch/arm/boot/dts/bcm47094-luxul-xwr-3100.dts      |   3 +
 arch/arm/boot/dts/bcm47189-tenda-ac9.dts           |   2 +
 arch/arm/boot/dts/bcm5301x.dtsi                    |  34 +++++
 arch/arm/boot/dts/bcm53573.dtsi                    |   4 +
 arch/arm/boot/dts/bcm911360_entphn.dts             |   7 +-
 arch/arm/boot/dts/bcm947189acdbmr.dts              |  97 ++++++++++++++
 arch/arm/boot/dts/bcm958522er.dts                  |   8 ++
 arch/arm/boot/dts/bcm958525er.dts                  |   8 ++
 arch/arm/boot/dts/bcm958525xmc.dts                 |   8 ++
 arch/arm/boot/dts/bcm958622hr.dts                  |   8 ++
 arch/arm/boot/dts/bcm958623hr.dts                  |   8 ++
 arch/arm/boot/dts/bcm958625hr.dts                  |   8 ++
 arch/arm/boot/dts/bcm958625k.dts                   |   8 ++
 arch/arm64/boot/dts/broadcom/bcm2835-rpi.dtsi      |   1 -
 arch/arm64/boot/dts/broadcom/bcm2837-rpi-3-b.dts   |  42 +-----
 .../boot/dts/broadcom/bcm283x-rpi-smsc9514.dtsi    |   1 -
 .../boot/dts/broadcom/bcm283x-rpi-usb-host.dtsi    |   1 -
 arch/arm64/boot/dts/broadcom/bcm283x.dtsi          |   1 -
 41 files changed, 651 insertions(+), 79 deletions(-)
 create mode 100644 arch/arm/boot/dts/bcm2835-rpi-zero-w.dts
 rename arch/{arm64/boot/dts/broadcom => arm/boot/dts}/bcm2837.dtsi (96%)
 create mode 100644 arch/arm/boot/dts/bcm947189acdbmr.dts
 delete mode 120000 arch/arm64/boot/dts/broadcom/bcm2835-rpi.dtsi
 delete mode 120000 arch/arm64/boot/dts/broadcom/bcm283x-rpi-smsc9514.dtsi
 delete mode 120000 arch/arm64/boot/dts/broadcom/bcm283x-rpi-usb-host.dtsi
 delete mode 120000 arch/arm64/boot/dts/broadcom/bcm283x.dtsi

[GIT PULL 3/6] Broadcom devicetree-arm64 changes for 4.14

[Florian Fainelli]

The following changes since commit 5771a8c08880cdca3bfb4a3fc6d309d6bba20877:

  Linux v4.13-rc1 (2017-07-15 15:22:10 -0700)

are available in the git repository at:

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

for you to fetch changes up to 63b2ff6aa608297472313eee473c2df8b060d491:

  arm64: dts: Add SBA-RAID DT nodes for Stingray SoC (2017-08-07 10:30:14 -0700)

----------------------------------------------------------------
This pull request contains Broadcom ARM64-based SoCs Device Tree changes for
4.14, please pull the following:

- Scott moves all the Northstar 2 DTS files into a sub-directory to be consistent
  with what was done for stingray and to future proof the addition of new board
  DTS files

- Velibor adds the ARM CCN-502 interconnect DT node to the Stingray SoC
  DTS include file

- Srinath adds the MDIO multiplexer and SATA nodes to the Stingray DTS
  include files

- Anup adds the SP804 timers, FlexRM (mailbox) and RAID engine DT nodes
  to the Stingray DTS include files

- Abishek adds the BGMAC (Ethernet controller) node to the Stingray DTS
  files

----------------------------------------------------------------
Abhishek Shah (1):
      arm64: dts: Add DT node to enable BGMAC driver on Stingray

Anup Patel (3):
      arm64: dts: Add sp804 DT nodes for Stingray SoC
      arm64: dts: Add FlexRM DT nodes for Stingray
      arm64: dts: Add SBA-RAID DT nodes for Stingray SoC

Scott Branden (1):
      arm64: dts: move ns2 into northstar2 directory

Srinath Mannam (2):
      arm64: dts: Add MDIO multiplexer DT node for Stingray
      arm64: dts: Add SATA DT nodes for Stingray SoC

Velibor Markovski (1):
      arm64: dts: Enable stats for CCN-502 interconnect on Stingray

 arch/arm64/boot/dts/broadcom/Makefile              |   4 +-
 arch/arm64/boot/dts/broadcom/northstar2/Makefile   |   6 +
 .../dts/broadcom/{ => northstar2}/ns2-clock.dtsi   |   0
 .../boot/dts/broadcom/{ => northstar2}/ns2-svk.dts |   0
 .../boot/dts/broadcom/{ => northstar2}/ns2-xmc.dts |   0
 .../boot/dts/broadcom/{ => northstar2}/ns2.dtsi    |   0
 .../boot/dts/broadcom/stingray/bcm958742-base.dtsi |  78 ++++++
 .../boot/dts/broadcom/stingray/bcm958742k.dts      |   4 +
 .../boot/dts/broadcom/stingray/bcm958742t.dts      |   4 +
 .../boot/dts/broadcom/stingray/stingray-fs4.dtsi   | 118 +++++++++
 .../boot/dts/broadcom/stingray/stingray-sata.dtsi  | 278 +++++++++++++++++++++
 .../arm64/boot/dts/broadcom/stingray/stingray.dtsi | 136 ++++++++++
 12 files changed, 626 insertions(+), 2 deletions(-)
 create mode 100644 arch/arm64/boot/dts/broadcom/northstar2/Makefile
 rename arch/arm64/boot/dts/broadcom/{ => northstar2}/ns2-clock.dtsi (100%)
 rename arch/arm64/boot/dts/broadcom/{ => northstar2}/ns2-svk.dts (100%)
 rename arch/arm64/boot/dts/broadcom/{ => northstar2}/ns2-xmc.dts (100%)
 rename arch/arm64/boot/dts/broadcom/{ => northstar2}/ns2.dtsi (100%)
 create mode 100644 arch/arm64/boot/dts/broadcom/stingray/stingray-fs4.dtsi
 create mode 100644 arch/arm64/boot/dts/broadcom/stingray/stingray-sata.dtsi

[GIT PULL 4/6] Broadcom defconfig changes for 4.14

[Florian Fainelli]

The following changes since commit 5771a8c08880cdca3bfb4a3fc6d309d6bba20877:

  Linux v4.13-rc1 (2017-07-15 15:22:10 -0700)

are available in the git repository at:

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

for you to fetch changes up to 8f457cb291342d9ac04dbb8dc565619d220841f8:

  ARM: multi_v7_defconfig: add CONFIG_BRCMSTB_THERMAL (2017-08-15 10:24:46 -0700)

----------------------------------------------------------------
This pull request contains defconfig file changes for Broadcom ARM-based SoCs
for 4.14, please pull the following:

- Markus enables the Broadcom STB AVS thermal monitoring driver as a module
  which is currently queued in Rui Zhang's tree

- Stefan updates the bcm2835_defconfig to contain a few useful changes: the RPI
  mini UART is enabled by default, the default CMA pool is bumped up to 32MB to
  support VC4 usages and finally BRCMFMAC is enabled as module since this is the
  wireless driver used on Raspberry Pi Zero Wireless.

----------------------------------------------------------------
Florian Fainelli (1):
      Merge tag 'bcm2835-defconfig-next-2017-08-07' into defconfig/next

Markus Mayer (1):
      ARM: multi_v7_defconfig: add CONFIG_BRCMSTB_THERMAL

Stefan Wahren (3):
      ARM: bcm2835_defconfig: Enable Mini UART console support
      ARM: bcm2835_defconfig: Increase CMA for VC4
      ARM: bcm2835_defconfig: Enable wifi driver for RPi Zero W

 arch/arm/configs/bcm2835_defconfig  | 7 +++++++
 arch/arm/configs/multi_v7_defconfig | 1 +
 2 files changed, 8 insertions(+)

[GIT PULL 5/6] Broadcom defconfig-arm64 changes for 4.14

[Florian Fainelli]

The following changes since commit 5771a8c08880cdca3bfb4a3fc6d309d6bba20877:

  Linux v4.13-rc1 (2017-07-15 15:22:10 -0700)

are available in the git repository at:

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

for you to fetch changes up to d5512507716eff4594f337d58318a853d1ff94be:

  arm64: defconfig: add CONFIG_BRCMSTB_THERMAL (2017-08-15 10:21:37 -0700)

----------------------------------------------------------------
This pull request contains ARM64 defconfig changes for Broadcom ARM64-based
SoCs for 4.14, please pull the following:

- Markus enables the Broadcom STB AVS thermal monitoring driver as a module
  which is currently queued in Rui Zhang's tree

----------------------------------------------------------------
Markus Mayer (1):
      arm64: defconfig: add CONFIG_BRCMSTB_THERMAL

 arch/arm64/configs/defconfig | 1 +
 1 file changed, 1 insertion(+)

[GIT PULL 6/6] Broadcom drivers changes for 4.14

[Florian Fainelli]

The following changes since commit 5771a8c08880cdca3bfb4a3fc6d309d6bba20877:

  Linux v4.13-rc1 (2017-07-15 15:22:10 -0700)

are available in the git repository at:

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

for you to fetch changes up to 7f95522be533c27a918fe388ae5d733344660ef2:

  soc bcm: brcmstb: Add support for S2/S3/S5 suspend states (MIPS) (2017-07-28 16:57:03 -0700)

----------------------------------------------------------------
This pull request contains Broadcom ARM/ARM64 SoC drivers changes for 4.14,
please pull the following:

- Markus adds support for the Broadcom STB DDR PHY frontend which supports
  dynamic firmware loading and offers the ability to respond with DRAM refresh
  rates. He also adds a proper documentation binding document for that peripheral

- Brian adds support for S2/S3/S5 system suspend/resume modes on ARM-based SoCs
  which is not new but had been lingering for a long time

- Justin adds S2/S3 system suspend/resume modes on MIPS-based SoCs which is a
  bit new newer and builds on top of the ARM-based support

- Florian adds Device Tree binding documents for both ARM and MIPS based systems
  describing the necessary nodes for S2/S3/S5 on these SoCs

----------------------------------------------------------------
Brian Norris (1):
      soc: bcm: brcmstb: Add support for S2/S3/S5 suspend states (ARM)

Florian Fainelli (2):
      dt-bindings: ARM: brcmstb: Update Broadcom STB Power Management binding
      dt-bindings: Document MIPS Broadcom STB power management nodes

Justin Chen (1):
      soc bcm: brcmstb: Add support for S2/S3/S5 suspend states (MIPS)

Markus Mayer (2):
      dt/bindings: Add bindings for Broadcom STB DRAM Sensors
      soc: brcmstb: Add driver for DPFE

 .../devicetree/bindings/arm/bcm/brcm,brcmstb.txt   |   6 +-
 .../devicetree/bindings/mips/brcm/soc.txt          | 153 ++++
 .../devicetree/bindings/soc/bcm/brcm,dpfe-cpu.txt  |  27 +
 MAINTAINERS                                        |   8 +
 drivers/soc/bcm/Kconfig                            |   2 +
 drivers/soc/bcm/brcmstb/Kconfig                    |   9 +
 drivers/soc/bcm/brcmstb/Makefile                   |   3 +-
 drivers/soc/bcm/brcmstb/dpfe.c                     | 689 +++++++++++++++++
 drivers/soc/bcm/brcmstb/pm/Makefile                |   3 +
 drivers/soc/bcm/brcmstb/pm/aon_defs.h              | 113 +++
 drivers/soc/bcm/brcmstb/pm/pm-arm.c                | 822 +++++++++++++++++++++
 drivers/soc/bcm/brcmstb/pm/pm-mips.c               | 461 ++++++++++++
 drivers/soc/bcm/brcmstb/pm/pm.h                    |  89 +++
 drivers/soc/bcm/brcmstb/pm/s2-arm.S                |  76 ++
 drivers/soc/bcm/brcmstb/pm/s2-mips.S               | 200 +++++
 drivers/soc/bcm/brcmstb/pm/s3-mips.S               | 146 ++++
 16 files changed, 2805 insertions(+), 2 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/soc/bcm/brcm,dpfe-cpu.txt
 create mode 100644 drivers/soc/bcm/brcmstb/Kconfig
 create mode 100644 drivers/soc/bcm/brcmstb/dpfe.c
 create mode 100644 drivers/soc/bcm/brcmstb/pm/Makefile
 create mode 100644 drivers/soc/bcm/brcmstb/pm/aon_defs.h
 create mode 100644 drivers/soc/bcm/brcmstb/pm/pm-arm.c
 create mode 100644 drivers/soc/bcm/brcmstb/pm/pm-mips.c
 create mode 100644 drivers/soc/bcm/brcmstb/pm/pm.h
 create mode 100644 drivers/soc/bcm/brcmstb/pm/s2-arm.S
 create mode 100644 drivers/soc/bcm/brcmstb/pm/s2-mips.S
 create mode 100644 drivers/soc/bcm/brcmstb/pm/s3-mips.S

[GIT PULL 4/6] Broadcom defconfig changes for 4.14

[Arnd Bergmann]

On Thu, Aug 17, 2017 at 8:37 PM, Florian Fainelli <f.fainelli@gmail.com> wrote:
> The following changes since commit 5771a8c08880cdca3bfb4a3fc6d309d6bba20877:
>
>   Linux v4.13-rc1 (2017-07-15 15:22:10 -0700)
>
> are available in the git repository at:
>
>   http://github.com/Broadcom/stblinux.git tags/arm-soc/for-4.14/defconfig
>
> for you to fetch changes up to 8f457cb291342d9ac04dbb8dc565619d220841f8:
>
>   ARM: multi_v7_defconfig: add CONFIG_BRCMSTB_THERMAL (2017-08-15 10:24:46 -0700)
>
> ----------------------------------------------------------------
> This pull request contains defconfig file changes for Broadcom ARM-based SoCs
> for 4.14, please pull the following:
>
> - Markus enables the Broadcom STB AVS thermal monitoring driver as a module
>   which is currently queued in Rui Zhang's tree
>
> - Stefan updates the bcm2835_defconfig to contain a few useful changes: the RPI
>   mini UART is enabled by default, the default CMA pool is bumped up to 32MB to
>   support VC4 usages and finally BRCMFMAC is enabled as module since this is the
>   wireless driver used on Raspberry Pi Zero Wireless.

Pulled into next/defconfig, thanks!

    Arnd

[GIT PULL 3/6] Broadcom devicetree-arm64 changes for 4.14

[Arnd Bergmann]

On Thu, Aug 17, 2017 at 8:37 PM, Florian Fainelli <f.fainelli@gmail.com> wrote:
> This pull request contains Broadcom ARM64-based SoCs Device Tree changes for
> 4.14, please pull the following:
>
> - Scott moves all the Northstar 2 DTS files into a sub-directory to be consistent
>   with what was done for stingray and to future proof the addition of new board
>   DTS files
>
> - Velibor adds the ARM CCN-502 interconnect DT node to the Stingray SoC
>   DTS include file
>
> - Srinath adds the MDIO multiplexer and SATA nodes to the Stingray DTS
>   include files
>
> - Anup adds the SP804 timers, FlexRM (mailbox) and RAID engine DT nodes
>   to the Stingray DTS include files
>
> - Abishek adds the BGMAC (Ethernet controller) node to the Stingray DTS
>   files

Pulled into next/dt64, thanks!

      Arnd

[GIT PULL 2/6] Broadcom devicetree changes for 4.14

[Arnd Bergmann]

On Thu, Aug 17, 2017 at 8:37 PM, Florian Fainelli <f.fainelli@gmail.com> wrote:
> The following changes since commit 5771a8c08880cdca3bfb4a3fc6d309d6bba20877:
>
>   Linux v4.13-rc1 (2017-07-15 15:22:10 -0700)
>
> are available in the git repository at:
>
>   http://github.com/Broadcom/stblinux.git tags/arm-soc/for-4.14/devicetree
>
> for you to fetch changes up to 0173b2cd6948b5b96ac4e8dbc3bcb4dd0b45c296:
>
>   ARM: BCM53573: Specify ports for USB LED for Tenda AC9 (2017-08-17 10:18:07 -0700)
>
> ----------------------------------------------------------------
> This pull request contains Broadcom ARM-based SoCs Device Tree changes for
> 4.14, please pull the following:
>
> - Eric moves the bcm2837 DT file from arm64 to arm because it created a maintenance
>   problem and would have required either duplication or cross merges
>
> - Stefan changes how the pinmuxing is defined and pushes it at the board level
>   to support Raspberry Pi Zero Wireless. He then adds supports for the actual
>   Raspberry Pi Zero Wireless board along with binding documentation. Stefan
>   also defines a proper SMP enable-method property and binding for BCM2836
>   (Raspbery Pi 2)
>
> - Rafal describes the BCM5301X USB ports correctly in Device Tree such that
>   it becomes possible to assign them to specific LED triggers (e.g: USB activity).
>   He does the same thing for BCM53573 and defines default LED triggers for USB.
>
> - Jon provides a fix for Northstar Plus which consists in correctly defining
>   the "dma-coherent" property for peripherals which are DMA coherent. He also
>   does a bit of re-arrangement of the USB DT nodes and finally adds USB 3 PHY
>   and host controller support for NorthStar Plus
>
> - Florian adds support for Broadcom's BCM947189ACDBMR reference board which is
>   based on BCM47182/53573 and which supports external MoCA (BCM6802)
>
> - Ray fixes the wrong UART2 base address for Cygnus
>
> - Scott moves the v3d node in the proper unit address order and defines the correct
>   UART alias for the BCM91130_entphn reference board to be UART3
>
> - Jason adds the DT node for the Cygnus Cortex-A9 Performance Monitoring Unit
>
> - Jonathan adds a bunch of additional peripherals to the Cygnus DTS include file:
>   SDHCI, Keypad, SPI, DMA and pinmux configurations
>
> - Raveendra adds the Cygnus OHCI and EHCI Device Tree nodes

Pulled into next/dt, thanks!

     Arnd

[GIT PULL 6/6] Broadcom drivers changes for 4.14

[Arnd Bergmann]

On Thu, Aug 17, 2017 at 8:37 PM, Florian Fainelli <f.fainelli@gmail.com> wrote:
> The following changes since commit 5771a8c08880cdca3bfb4a3fc6d309d6bba20877:
>
>   Linux v4.13-rc1 (2017-07-15 15:22:10 -0700)
>
> are available in the git repository at:
>
>   http://github.com/Broadcom/stblinux.git tags/arm-soc/for-4.14/drivers
>
> for you to fetch changes up to 7f95522be533c27a918fe388ae5d733344660ef2:
>
>   soc bcm: brcmstb: Add support for S2/S3/S5 suspend states (MIPS) (2017-07-28 16:57:03 -0700)
>
> ----------------------------------------------------------------
> This pull request contains Broadcom ARM/ARM64 SoC drivers changes for 4.14,
> please pull the following:
>
> - Markus adds support for the Broadcom STB DDR PHY frontend which supports
>   dynamic firmware loading and offers the ability to respond with DRAM refresh
>   rates. He also adds a proper documentation binding document for that peripheral
>

I had not seen this driver before, but now I looked at it and have two small
comments:

- I'd rather see this added to drivers/memory than drivers/soc. The distinction
  is not always clear, but I think that's where most of the DDR memory interface
  drivers are at the moment.

- In a function called __write_firmware, I stumbled over this small
  hunk and similar functions elsewhere in the driver:

+       /* Now copy it. */
+       if (is_big_endian) {
+               for (i = 0; i < size; i++)
+                       writel_relaxed(be32_to_cpu(fw[i]), mem + i);
+       } else {
+               for (i = 0; i < size; i++)
+                       writel_relaxed(fw[i], mem + i);
+       }

This looks wrong to me, as the behavior is different between
little-endian and big-endian kernels: the former will byteswap
big-endian fw images but not little-endian images, while the
latter will byte-swap both.

What is the expected behavior here?

Both of my points should be easy to address, so I haven't
pulled the branch yet, but expect that it will make it into 4.14
without problems.

       Arnd

[GIT PULL 5/6] Broadcom defconfig-arm64 changes for 4.14

[Arnd Bergmann]

On Thu, Aug 17, 2017 at 8:37 PM, Florian Fainelli <f.fainelli@gmail.com> wrote:
> ----------------------------------------------------------------
> This pull request contains ARM64 defconfig changes for Broadcom ARM64-based
> SoCs for 4.14, please pull the following:
>
> - Markus enables the Broadcom STB AVS thermal monitoring driver as a module
>   which is currently queued in Rui Zhang's tree

Pulled into next/arm64, thanks!

        Arnd

[GIT PULL 6/6] Broadcom drivers changes for 4.14

[Florian Fainelli]

On 08/18/2017 02:58 PM, Arnd Bergmann wrote:
> On Thu, Aug 17, 2017 at 8:37 PM, Florian Fainelli <f.fainelli@gmail.com> wrote:
>> The following changes since commit 5771a8c08880cdca3bfb4a3fc6d309d6bba20877:
>>
>>   Linux v4.13-rc1 (2017-07-15 15:22:10 -0700)
>>
>> are available in the git repository at:
>>
>>   http://github.com/Broadcom/stblinux.git tags/arm-soc/for-4.14/drivers
>>
>> for you to fetch changes up to 7f95522be533c27a918fe388ae5d733344660ef2:
>>
>>   soc bcm: brcmstb: Add support for S2/S3/S5 suspend states (MIPS) (2017-07-28 16:57:03 -0700)
>>
>> ----------------------------------------------------------------
>> This pull request contains Broadcom ARM/ARM64 SoC drivers changes for 4.14,
>> please pull the following:
>>
>> - Markus adds support for the Broadcom STB DDR PHY frontend which supports
>>   dynamic firmware loading and offers the ability to respond with DRAM refresh
>>   rates. He also adds a proper documentation binding document for that peripheral
>>
> 
> I had not seen this driver before, but now I looked at it and have two small
> comments:
> 
> - I'd rather see this added to drivers/memory than drivers/soc. The distinction
>   is not always clear, but I think that's where most of the DDR memory interface
>   drivers are at the moment.

This driver does not control the SoC's memory interface though it does
talk to the frontend processor built into the DDR controller to first
load its firmware and then query it to get the DDR refresh rates. If you
feel like drivers/memory/broadcom/ is more appropriate I suppose we
could relocate the driver there.

> 
> - In a function called __write_firmware, I stumbled over this small
>   hunk and similar functions elsewhere in the driver:
> 
> +       /* Now copy it. */
> +       if (is_big_endian) {
> +               for (i = 0; i < size; i++)
> +                       writel_relaxed(be32_to_cpu(fw[i]), mem + i);
> +       } else {
> +               for (i = 0; i < size; i++)
> +                       writel_relaxed(fw[i], mem + i);
> +       }
> 
> This looks wrong to me, as the behavior is different between
> little-endian and big-endian kernels: the former will byteswap
> big-endian fw images but not little-endian images, while the
> latter will byte-swap both.
> 
> What is the expected behavior here?

So the is_big_endian flag actually refers to the endianess of the DPFE
CPU/firmware image here, so if I read this code correctly, we have the
following happening

LE kernel + BE DPFE: swapping from BE to LE during file read but not I/O
write (KO because resulting DPFE image is LE)
LE kernel + LE DPFE: no-swapping (OK)

BE kernel + BE DPFE: swapping to LE during I/O write not file read (KO,
because resulting DPFE image is LE)
BE kernel + LE DPFE: swapping to LE during I/O write not file read (OK)

Markus, does that sound like what is happening?

> 
> Both of my points should be easy to address, so I haven't
> pulled the branch yet, but expect that it will make it into 4.14
> without problems.
> 
>        Arnd
> 


-- 
Florian

[GIT PULL 6/6] Broadcom drivers changes for 4.14

[Arnd Bergmann]

On Sat, Aug 19, 2017 at 12:35 AM, Florian Fainelli <f.fainelli@gmail.com> wrote:
> On 08/18/2017 02:58 PM, Arnd Bergmann wrote:
>> On Thu, Aug 17, 2017 at 8:37 PM, Florian Fainelli <f.fainelli@gmail.com> wrote:
>>> The following changes since commit 5771a8c08880cdca3bfb4a3fc6d309d6bba20877:
>>>
>>>   Linux v4.13-rc1 (2017-07-15 15:22:10 -0700)
>>>
>>> are available in the git repository at:
>>>
>>>   http://github.com/Broadcom/stblinux.git tags/arm-soc/for-4.14/drivers
>>>
>>> for you to fetch changes up to 7f95522be533c27a918fe388ae5d733344660ef2:
>>>
>>>   soc bcm: brcmstb: Add support for S2/S3/S5 suspend states (MIPS) (2017-07-28 16:57:03 -0700)
>>>
>>> ----------------------------------------------------------------
>>> This pull request contains Broadcom ARM/ARM64 SoC drivers changes for 4.14,
>>> please pull the following:
>>>
>>> - Markus adds support for the Broadcom STB DDR PHY frontend which supports
>>>   dynamic firmware loading and offers the ability to respond with DRAM refresh
>>>   rates. He also adds a proper documentation binding document for that peripheral
>>>
>>
>> I had not seen this driver before, but now I looked at it and have two small
>> comments:
>>
>> - I'd rather see this added to drivers/memory than drivers/soc. The distinction
>>   is not always clear, but I think that's where most of the DDR memory interface
>>   drivers are at the moment.
>
> This driver does not control the SoC's memory interface though it does
> talk to the frontend processor built into the DDR controller to first
> load its firmware and then query it to get the DDR refresh rates. If you
> feel like drivers/memory/broadcom/ is more appropriate I suppose we
> could relocate the driver there.

Yes, I still think it makes sense to put it there, although it's not the only
possible choice. drivers/memory is a very broad category that groups
all kinds of things that are related to memory interfaces.

>> - In a function called __write_firmware, I stumbled over this small
>>   hunk and similar functions elsewhere in the driver:
>>
>> +       /* Now copy it. */
>> +       if (is_big_endian) {
>> +               for (i = 0; i < size; i++)
>> +                       writel_relaxed(be32_to_cpu(fw[i]), mem + i);
>> +       } else {
>> +               for (i = 0; i < size; i++)
>> +                       writel_relaxed(fw[i], mem + i);
>> +       }
>>
>> This looks wrong to me, as the behavior is different between
>> little-endian and big-endian kernels: the former will byteswap
>> big-endian fw images but not little-endian images, while the
>> latter will byte-swap both.
>>
>> What is the expected behavior here?
>
> So the is_big_endian flag actually refers to the endianess of the DPFE
> CPU/firmware image here, so if I read this code correctly, we have the
> following happening
>
> LE kernel + BE DPFE: swapping from BE to LE during file read but not I/O
> write (KO because resulting DPFE image is LE)
> LE kernel + LE DPFE: no-swapping (OK)
>
> BE kernel + BE DPFE: swapping to LE during I/O write not file read (KO,
> because resulting DPFE image is LE)
> BE kernel + LE DPFE: swapping to LE during I/O write not file read (OK)
>
> Markus, does that sound like what is happening?

I suspect it would be better to never swap while copying the image from
memory to I/O and always use memcpy_toio there, which performs
a byte stream copy. The information you then need really is not what
the endianess of the DPFE CPU is, but rather if it was stored as
byte-reversed in the file.

       Arnd

[GIT PULL 6/6] Broadcom drivers changes for 4.14

[Florian Fainelli]

On 08/19/2017 01:34 PM, Arnd Bergmann wrote:
> On Sat, Aug 19, 2017 at 12:35 AM, Florian Fainelli <f.fainelli@gmail.com> wrote:
>> On 08/18/2017 02:58 PM, Arnd Bergmann wrote:
>>> On Thu, Aug 17, 2017 at 8:37 PM, Florian Fainelli <f.fainelli@gmail.com> wrote:
>>>> The following changes since commit 5771a8c08880cdca3bfb4a3fc6d309d6bba20877:
>>>>
>>>>   Linux v4.13-rc1 (2017-07-15 15:22:10 -0700)
>>>>
>>>> are available in the git repository at:
>>>>
>>>>   http://github.com/Broadcom/stblinux.git tags/arm-soc/for-4.14/drivers
>>>>
>>>> for you to fetch changes up to 7f95522be533c27a918fe388ae5d733344660ef2:
>>>>
>>>>   soc bcm: brcmstb: Add support for S2/S3/S5 suspend states (MIPS) (2017-07-28 16:57:03 -0700)
>>>>
>>>> ----------------------------------------------------------------
>>>> This pull request contains Broadcom ARM/ARM64 SoC drivers changes for 4.14,
>>>> please pull the following:
>>>>
>>>> - Markus adds support for the Broadcom STB DDR PHY frontend which supports
>>>>   dynamic firmware loading and offers the ability to respond with DRAM refresh
>>>>   rates. He also adds a proper documentation binding document for that peripheral
>>>>
>>>
>>> I had not seen this driver before, but now I looked at it and have two small
>>> comments:
>>>
>>> - I'd rather see this added to drivers/memory than drivers/soc. The distinction
>>>   is not always clear, but I think that's where most of the DDR memory interface
>>>   drivers are at the moment.
>>
>> This driver does not control the SoC's memory interface though it does
>> talk to the frontend processor built into the DDR controller to first
>> load its firmware and then query it to get the DDR refresh rates. If you
>> feel like drivers/memory/broadcom/ is more appropriate I suppose we
>> could relocate the driver there.
> 
> Yes, I still think it makes sense to put it there, although it's not the only
> possible choice. drivers/memory is a very broad category that groups
> all kinds of things that are related to memory interfaces.

Alright, we'll move it there.

> 
>>> - In a function called __write_firmware, I stumbled over this small
>>>   hunk and similar functions elsewhere in the driver:
>>>
>>> +       /* Now copy it. */
>>> +       if (is_big_endian) {
>>> +               for (i = 0; i < size; i++)
>>> +                       writel_relaxed(be32_to_cpu(fw[i]), mem + i);
>>> +       } else {
>>> +               for (i = 0; i < size; i++)
>>> +                       writel_relaxed(fw[i], mem + i);
>>> +       }
>>>
>>> This looks wrong to me, as the behavior is different between
>>> little-endian and big-endian kernels: the former will byteswap
>>> big-endian fw images but not little-endian images, while the
>>> latter will byte-swap both.
>>>
>>> What is the expected behavior here?
>>
>> So the is_big_endian flag actually refers to the endianess of the DPFE
>> CPU/firmware image here, so if I read this code correctly, we have the
>> following happening
>>
>> LE kernel + BE DPFE: swapping from BE to LE during file read but not I/O
>> write (KO because resulting DPFE image is LE)
>> LE kernel + LE DPFE: no-swapping (OK)
>>
>> BE kernel + BE DPFE: swapping to LE during I/O write not file read (KO,
>> because resulting DPFE image is LE)
>> BE kernel + LE DPFE: swapping to LE during I/O write not file read (OK)
>>
>> Markus, does that sound like what is happening?
> 
> I suspect it would be better to never swap while copying the image from
> memory to I/O and always use memcpy_toio there, which performs
> a byte stream copy. The information you then need really is not what
> the endianess of the DPFE CPU is, but rather if it was stored as
> byte-reversed in the file.

I think you are right, it does not look like we need to swap and since
we are actually already checking the endianess of the file it should be
a lot simpler, we'll fix that too. Thanks!
-- 
Florian

[GIT PULL 1/6] Broadcom soc changes for 4.14

[Florian Fainelli]

On 08/17/2017 11:37 AM, Florian Fainelli wrote:
> The following changes since commit 5771a8c08880cdca3bfb4a3fc6d309d6bba20877:
> 
>   Linux v4.13-rc1 (2017-07-15 15:22:10 -0700)
> 
> are available in the git repository at:
> 
>   http://github.com/Broadcom/stblinux.git tags/arm-soc/for-4.14/soc
> 
> for you to fetch changes up to e831871597aaa1f650b83f96b61858907c203b76:
> 
>   Merge tag 'bcm2835-soc-next-2017-08-15' into soc/next (2017-08-16 18:14:49 -0700)
> 
> ----------------------------------------------------------------
> This pull request contains Broadcom ARM-based SoC/Kconfig changes for 4.14,
> please pull the following:
> 
> - Stefan moves the BCM2836 SMP bring-up code from the irqchip driver down to
>   where it belongs under arch/arm/mach-bcm/. This requires us to merge parts
>   of the devicetree/next branch because we depend on Eric's change that relocates
>   the bcm2836/37 Device Tree files as well as the "enable-method" being correctly
>   set in the Device Tree source files.
> 
> - Danilo removes the fixed clocks introduced earlier when we did not have a
>   CPRMAN clock provider and in the process removes the init_machine callback
>   since we no longer need it.
> 
> - Phil provides a fix for the SMP bring-up code to have a "sev" (and corresponding
>   barrier) instruction in order to wake-up secondary cores. Future Rasperry Pi
>   firmware(s) will depend on this.
> 
> ----------------------------------------------------------------

Copying what Arnd was writing on IRC this morning, Eric, Stefan, can you
implement what Arnd recommends and I will pull again or cherry-pick
(whatever you prefer) thanks! Arnd, how quickly should we give you a new
PR with those changes?

10:07 < arnd> [florian], anholt, maz: I looked at the
arm-soc/for-4.14/soc pull request again now, and wonder if we can do a
little better than  that

10:08 < arnd> it seems you have pulled in the DT branch before the move
of the bcm2836_smp_ops from drivers/irqchip to arch/arm/mach-bcm, to
hide an incompatible DT binding change: in the old code, no
 enable-method was needed, but now it is

10:09 < arnd> clearly we want the enable-method to be there, but it
would be good if old dts files could keep working, in particular as
there are probably lots of people that hack their dts files to add
  random peripherals, and we don't want to force them to update their
dtb with every kernel change

10:11 < arnd> how about we add a .smp_init handler to
DT_MACHINE_START(BCM2835, ...) to keep it working with the old DT?

10:12 < arnd> that would also get rid of the branch dependency as an
added bonus, but avoiding the boot breakage is more important of course

10:13 < arnd> Stefan Wahren did the patch, but he's either not on this
channel, or I don't know his nick

10:30 < arnd> on a related note, I see that the match table for the
machine descriptor doesn't list bcm2837, and the bcm2837.dtsi file
doesn't list itself as compatible with bcm2836, so that would have to be
   added too to make it actually work

> Danilo Krummrich (1):
>       clk: bcm2835: remove remains from stub clk driver
> 
> Eric Anholt (2):
>       ARM: dts: bcm283x: Move the BCM2837 DT contents from arm64 to arm.
>       Merge tag 'bcm2835-dt-next-2017-08-15' into HEAD
> 
> Florian Fainelli (3):
>       ARM: dts: BCM53573: Add Broadcom BCM947189ACDBMR board support
>       Merge tag 'bcm2835-dt-next-2017-08-07' into devicetree/next
>       Merge tag 'bcm2835-soc-next-2017-08-15' into soc/next
> 
> Jon Mason (3):
>       ARM: dts: NSP: Add dma-coherent to relevant DT entries
>       ARM: dts: NSP: Rearrage USB entries
>       ARM: dts: NSP: Add USB3 and USB3 PHY to NSP
> 
> Phil Elwell (1):
>       ARM: bcm2836: Send event when onlining other cores
> 
> Rafa? Mi?ecki (2):
>       ARM: dts: BCM5301X: Specify USB ports for each controller
>       ARM: dts: BCM5301X: Specify USB ports for USB LEDs of few devices
> 
> Stefan Wahren (6):
>       ARM: bcm283x: Define UART pinmuxing on board level
>       dt-bindings: bcm: Add Raspberry Pi Zero W
>       ARM: dts: bcm2835: Add Raspberry Pi Zero W
>       dt-bindings: arm: add SMP enable-method for BCM2836
>       ARM: dts: bcm283x: Add 32-bit enable method for SMP
>       irqchip: bcm2836: Move SMP startup code to arch/arm
> 
>  .../devicetree/bindings/arm/bcm/brcm,bcm2835.txt   |   4 +
>  Documentation/devicetree/bindings/arm/cpus.txt     |   1 +
>  arch/arm/boot/dts/Makefile                         |   6 +-
>  arch/arm/boot/dts/bcm-nsp.dtsi                     |  59 ++++++---
>  arch/arm/boot/dts/bcm2835-rpi-a-plus.dts           |   6 +
>  arch/arm/boot/dts/bcm2835-rpi-a.dts                |   6 +
>  arch/arm/boot/dts/bcm2835-rpi-b-plus.dts           |   6 +
>  arch/arm/boot/dts/bcm2835-rpi-b-rev2.dts           |   6 +
>  arch/arm/boot/dts/bcm2835-rpi-b.dts                |   6 +
>  arch/arm/boot/dts/bcm2835-rpi-zero-w.dts           | 139 +++++++++++++++++++++
>  arch/arm/boot/dts/bcm2835-rpi-zero.dts             |   6 +
>  arch/arm/boot/dts/bcm2835-rpi.dtsi                 |   2 +-
>  arch/arm/boot/dts/bcm2836-rpi-2-b.dts              |   6 +
>  arch/arm/boot/dts/bcm2836.dtsi                     |   1 +
>  arch/arm/boot/dts/bcm2837-rpi-3-b.dts              |  52 +++++++-
>  .../dts/broadcom => arm/boot/dts}/bcm2837.dtsi     |   1 +
>  arch/arm/boot/dts/bcm4708-buffalo-wzr-1750dhp.dts  |   4 +
>  arch/arm/boot/dts/bcm4708-netgear-r6250.dts        |   3 +
>  arch/arm/boot/dts/bcm4708-smartrg-sr400ac.dts      |   6 +
>  arch/arm/boot/dts/bcm47081-tplink-archer-c5-v2.dts |   4 +
>  arch/arm/boot/dts/bcm4709-tplink-archer-c9-v1.dts  |   5 +
>  arch/arm/boot/dts/bcm47094-dlink-dir-885l.dts      |   3 +
>  arch/arm/boot/dts/bcm47094-luxul-xwr-3100.dts      |   3 +
>  arch/arm/boot/dts/bcm5301x.dtsi                    |  34 +++++
>  arch/arm/boot/dts/bcm947189acdbmr.dts              |  97 ++++++++++++++
>  arch/arm/boot/dts/bcm958522er.dts                  |   8 ++
>  arch/arm/boot/dts/bcm958525er.dts                  |   8 ++
>  arch/arm/boot/dts/bcm958525xmc.dts                 |   8 ++
>  arch/arm/boot/dts/bcm958622hr.dts                  |   8 ++
>  arch/arm/boot/dts/bcm958623hr.dts                  |   8 ++
>  arch/arm/boot/dts/bcm958625hr.dts                  |   8 ++
>  arch/arm/boot/dts/bcm958625k.dts                   |   8 ++
>  arch/arm/mach-bcm/Makefile                         |   5 +
>  arch/arm/mach-bcm/board_bcm2835.c                  |   7 --
>  arch/arm/mach-bcm/platsmp.c                        |  38 ++++++
>  arch/arm64/boot/dts/broadcom/bcm2835-rpi.dtsi      |   1 -
>  arch/arm64/boot/dts/broadcom/bcm2837-rpi-3-b.dts   |  42 +------
>  .../boot/dts/broadcom/bcm283x-rpi-smsc9514.dtsi    |   1 -
>  .../boot/dts/broadcom/bcm283x-rpi-usb-host.dtsi    |   1 -
>  arch/arm64/boot/dts/broadcom/bcm283x.dtsi          |   1 -
>  drivers/clk/bcm/clk-bcm2835-aux.c                  |   1 -
>  drivers/clk/bcm/clk-bcm2835.c                      |  30 -----
>  drivers/irqchip/irq-bcm2836.c                      |  79 +-----------
>  include/linux/clk/bcm2835.h                        |  24 ----
>  include/linux/irqchip/irq-bcm2836.h                |  70 +++++++++++
>  45 files changed, 620 insertions(+), 202 deletions(-)
>  create mode 100644 arch/arm/boot/dts/bcm2835-rpi-zero-w.dts
>  rename arch/{arm64/boot/dts/broadcom => arm/boot/dts}/bcm2837.dtsi (96%)
>  create mode 100644 arch/arm/boot/dts/bcm947189acdbmr.dts
>  delete mode 120000 arch/arm64/boot/dts/broadcom/bcm2835-rpi.dtsi
>  delete mode 120000 arch/arm64/boot/dts/broadcom/bcm283x-rpi-smsc9514.dtsi
>  delete mode 120000 arch/arm64/boot/dts/broadcom/bcm283x-rpi-usb-host.dtsi
>  delete mode 120000 arch/arm64/boot/dts/broadcom/bcm283x.dtsi
>  delete mode 100644 include/linux/clk/bcm2835.h
>  create mode 100644 include/linux/irqchip/irq-bcm2836.h
> 


-- 
Florian

[GIT PULL 1/6] Broadcom soc changes for 4.14

[Stefan Wahren]

Hi,

> Florian Fainelli <f.fainelli@gmail.com> hat am 22. August 2017 um 00:16 geschrieben:
> 
> 
> On 08/17/2017 11:37 AM, Florian Fainelli wrote:
> 
> Copying what Arnd was writing on IRC this morning, Eric, Stefan, can you
> implement what Arnd recommends and I will pull again or cherry-pick
> (whatever you prefer) thanks! Arnd, how quickly should we give you a new
> PR with those changes?
> 
> 10:07 < arnd> [florian], anholt, maz: I looked at the
> arm-soc/for-4.14/soc pull request again now, and wonder if we can do a
> little better than  that
> 
> 10:08 < arnd> it seems you have pulled in the DT branch before the move
> of the bcm2836_smp_ops from drivers/irqchip to arch/arm/mach-bcm, to
> hide an incompatible DT binding change: in the old code, no
>  enable-method was needed, but now it is
> 
> 10:09 < arnd> clearly we want the enable-method to be there, but it
> would be good if old dts files could keep working, in particular as
> there are probably lots of people that hack their dts files to add
>   random peripherals, and we don't want to force them to update their
> dtb with every kernel change
> 
> 10:11 < arnd> how about we add a .smp_init handler to
> DT_MACHINE_START(BCM2835, ...) to keep it working with the old DT?
> 
> 10:12 < arnd> that would also get rid of the branch dependency as an
> added bonus, but avoiding the boot breakage is more important of course

i already had a discussion with Eric about the case the dts changes are missing and i wasn't able see a boot breakage ("only" a SMP breakage which is still a regression).

> 
> 10:13 < arnd> Stefan Wahren did the patch, but he's either not on this
> channel, or I don't know his nick
> 
> 10:30 < arnd> on a related note, I see that the match table for the
> machine descriptor doesn't list bcm2837, and the bcm2837.dtsi file
> doesn't list itself as compatible with bcm2836, so that would have to be
>    added too to make it actually work
> 

sorry i don't have much time today and i'm not sure how to implement the smp_init.

Here is my draft (untested) which has a linker error (arch/arm/mach-bcm/board_bcm2835.o:(.arch.info.init+0x34): Undefined reference on `bcm2836_smp_ops). Does it goes in the right direction?

diff --git a/arch/arm/mach-bcm/board_bcm2835.c b/arch/arm/mach-bcm/board_bcm2835.c
index 24af33f..4f90f1f 100644
--- a/arch/arm/mach-bcm/board_bcm2835.c
+++ b/arch/arm/mach-bcm/board_bcm2835.c
@@ -19,16 +19,21 @@
 #include <asm/mach/arch.h>
 #include <asm/mach/map.h>
 
+#include "platsmp.h"
+
 static const char * const bcm2835_compat[] = {
 #ifdef CONFIG_ARCH_MULTI_V6
 	"brcm,bcm2835",
 #endif
 #ifdef CONFIG_ARCH_MULTI_V7
 	"brcm,bcm2836",
+	"brcm,bcm2837",
 #endif
 	NULL
 };
 
 DT_MACHINE_START(BCM2835, "BCM2835")
-	.dt_compat = bcm2835_compat
+	.dt_compat = bcm2835_compat,
+	.smp = smp_ops(bcm2836_smp_ops),
+	.smp_init = smp_init_ops(bcm2836_smp_init_ops),
 MACHINE_END
diff --git a/arch/arm/mach-bcm/platsmp.c b/arch/arm/mach-bcm/platsmp.c
index 7811160..c47c79a 100644
--- a/arch/arm/mach-bcm/platsmp.c
+++ b/arch/arm/mach-bcm/platsmp.c
@@ -343,3 +343,8 @@ static const struct smp_operations bcm2836_smp_ops __initconst = {
 	.smp_boot_secondary	= bcm2836_boot_secondary,
 };
 CPU_METHOD_OF_DECLARE(bcm_smp_bcm2836, "brcm,bcm2836-smp", &bcm2836_smp_ops);
+
+bool __init bcm2836_smp_init_ops(void) {
+	smp_set_ops(&bcm2836_smp_ops);
+	return true;
+}
diff --git a/arch/arm/mach-bcm/platsmp.h b/arch/arm/mach-bcm/platsmp.h
new file mode 100644
index 0000000..50c0ad3
--- /dev/null
+++ b/arch/arm/mach-bcm/platsmp.h
@@ -0,0 +1,4 @@
+
+bool bcm2836_smp_init_ops(void);
+
+extern const struct smp_operations bcm2836_smp_ops;

> -- 
> Florian

[GIT PULL 1/6] Broadcom soc changes for 4.14

[Arnd Bergmann]

On Tue, Aug 22, 2017 at 6:50 PM, Stefan Wahren <stefan.wahren@i2se.com> wrote:
>> Florian Fainelli <f.fainelli@gmail.com> hat am 22. August 2017 um 00:16 geschrieben:
>> On 08/17/2017 11:37 AM, Florian Fainelli wrote:
>>
>> 10:12 < arnd> that would also get rid of the branch dependency as an
>> added bonus, but avoiding the boot breakage is more important of course
>
> i already had a discussion with Eric about the case the dts changes are missing and i wasn't able see a boot breakage ("only" a SMP breakage which is still a regression).

Yes, that's what I meant.

>> 10:13 < arnd> Stefan Wahren did the patch, but he's either not on this
>> channel, or I don't know his nick
>>
>> 10:30 < arnd> on a related note, I see that the match table for the
>> machine descriptor doesn't list bcm2837, and the bcm2837.dtsi file
>> doesn't list itself as compatible with bcm2836, so that would have to be
>>    added too to make it actually work
>>
>
> sorry i don't have much time today and i'm not sure how to implement the smp_init.
>
> Here is my draft (untested) which has a linker error (arch/arm/mach-bcm/board_bcm2835.o:(.arch.info.init+0x34): Undefined reference on `bcm2836_smp_ops). Does it goes in the right direction?

Looks good to me.

>  DT_MACHINE_START(BCM2835, "BCM2835")
> -       .dt_compat = bcm2835_compat
> +       .dt_compat = bcm2835_compat,
> +       .smp = smp_ops(bcm2836_smp_ops),
> +       .smp_init = smp_init_ops(bcm2836_smp_init_ops),

One of the two should actually be sufficient here. Setting the .smp pointer
is shorter so if that works, we can leave out the init function completely.

       Arnd

[GIT PULL 1/6 V2] Broadcom soc changes for 4.14

[Florian Fainelli]

The following changes since commit 5771a8c08880cdca3bfb4a3fc6d309d6bba20877:

  Linux v4.13-rc1 (2017-07-15 15:22:10 -0700)

are available in the git repository at:

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

for you to fetch changes up to c9351923600e073083fc378c870c593cf98dd551:

  Merge tag 'bcm2835-soc-next-2017-08-24' into soc/next (2017-08-24 11:47:29 -0700)

----------------------------------------------------------------
This pull request contains Broadcom ARM-based SoC arch/ changes for 4.14,
please pull the following:

- Danilo removes the clock provider driver stubs which are no longer needed
  now that we have a proper CPRMAN clock provider driver

- Stefan moves the SMP startup code for BCM2836 from the interrupt controller
  driver down to where it belongs in the architecture code, this was requested
  by Marc Zyngier before comitting any fixes to that code

- Phil provides a fix for a future Raspberry Pi firmware which will make the
  secondary cores wait for an event and therefore requires the CPU onlining
  other cores to send such event (along with the appropriate barrier)

----------------------------------------------------------------
Danilo Krummrich (1):
      clk: bcm2835: remove remains from stub clk driver

Florian Fainelli (1):
      Merge tag 'bcm2835-soc-next-2017-08-24' into soc/next

Phil Elwell (1):
      ARM: bcm2836: Send event when onlining other cores

Stefan Wahren (1):
      irqchip: bcm2836: Move SMP startup code to arch/arm (v2)

 arch/arm/mach-bcm/Makefile          |  5 +++
 arch/arm/mach-bcm/board_bcm2835.c   | 11 ++----
 arch/arm/mach-bcm/platsmp.c         | 38 ++++++++++++++++++
 arch/arm/mach-bcm/platsmp.h         | 10 +++++
 drivers/clk/bcm/clk-bcm2835-aux.c   |  1 -
 drivers/clk/bcm/clk-bcm2835.c       | 30 --------------
 drivers/irqchip/irq-bcm2836.c       | 79 +------------------------------------
 include/linux/clk/bcm2835.h         | 24 -----------
 include/linux/irqchip/irq-bcm2836.h | 70 ++++++++++++++++++++++++++++++++
 9 files changed, 129 insertions(+), 139 deletions(-)
 create mode 100644 arch/arm/mach-bcm/platsmp.h
 delete mode 100644 include/linux/clk/bcm2835.h
 create mode 100644 include/linux/irqchip/irq-bcm2836.h

[GIT PULL 6/6 V2] Broadcom drivers changes for 4.14

[Florian Fainelli]

The following changes since commit 5771a8c08880cdca3bfb4a3fc6d309d6bba20877:

  Linux v4.13-rc1 (2017-07-15 15:22:10 -0700)

are available in the git repository at:

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

for you to fetch changes up to ed70bd0aa574d4922382ead47cd370174e31cb0e:

  soc bcm: brcmstb: Add support for S2/S3/S5 suspend states (MIPS) (2017-08-24 17:49:43 -0700)

----------------------------------------------------------------
This pull request contains Broadcom ARM/ARM64 SoC drivers changes for 4.14,
please pull the following:

- Markus adds support for the Broadcom STB DDR PHY frontend which supports
  dynamic firmware loading and offers the ability to respond with DRAM refresh
  rates. He also adds a proper documentation binding document for that
  peripheral

- Brian adds support for S2/S3/S5 system suspend/resume modes on ARM-based SoCs
  which is not new but had been lingering for a long time.

- Justin adds S2/S3 system suspend/resume modes on MIPS-based SoCs which is a
  bit new newer and builds on top of the ARM-based support.

- Florian adds Device Tree binding documents for both ARM and MIPS based systems
  describing the necessary nodes for S2/S3/S5 on these SoCs.

----------------------------------------------------------------
Brian Norris (1):
      soc: bcm: brcmstb: Add support for S2/S3/S5 suspend states (ARM)

Florian Fainelli (2):
      dt-bindings: ARM: brcmstb: Update Broadcom STB Power Management binding
      dt-bindings: Document MIPS Broadcom STB power management nodes

Justin Chen (1):
      soc bcm: brcmstb: Add support for S2/S3/S5 suspend states (MIPS)

Markus Mayer (2):
      dt-bindings: Add bindings for Broadcom STB DRAM Sensors
      memory: brcmstb: Add driver for DPFE

 .../devicetree/bindings/arm/bcm/brcm,brcmstb.txt   |   6 +-
 .../bindings/memory-controllers/brcm,dpfe-cpu.txt  |  27 +
 .../devicetree/bindings/mips/brcm/soc.txt          | 153 ++++
 MAINTAINERS                                        |   8 +
 drivers/memory/Makefile                            |   1 +
 drivers/memory/brcmstb_dpfe.c                      | 701 ++++++++++++++++++
 drivers/soc/bcm/Kconfig                            |   2 +
 drivers/soc/bcm/brcmstb/Kconfig                    |   9 +
 drivers/soc/bcm/brcmstb/Makefile                   |   1 +
 drivers/soc/bcm/brcmstb/pm/Makefile                |   3 +
 drivers/soc/bcm/brcmstb/pm/aon_defs.h              | 113 +++
 drivers/soc/bcm/brcmstb/pm/pm-arm.c                | 822 +++++++++++++++++++++
 drivers/soc/bcm/brcmstb/pm/pm-mips.c               | 461 ++++++++++++
 drivers/soc/bcm/brcmstb/pm/pm.h                    |  89 +++
 drivers/soc/bcm/brcmstb/pm/s2-arm.S                |  76 ++
 drivers/soc/bcm/brcmstb/pm/s2-mips.S               | 200 +++++
 drivers/soc/bcm/brcmstb/pm/s3-mips.S               | 146 ++++
 17 files changed, 2817 insertions(+), 1 deletion(-)
 create mode 100644 Documentation/devicetree/bindings/memory-controllers/brcm,dpfe-cpu.txt
 create mode 100644 drivers/memory/brcmstb_dpfe.c
 create mode 100644 drivers/soc/bcm/brcmstb/Kconfig
 create mode 100644 drivers/soc/bcm/brcmstb/pm/Makefile
 create mode 100644 drivers/soc/bcm/brcmstb/pm/aon_defs.h
 create mode 100644 drivers/soc/bcm/brcmstb/pm/pm-arm.c
 create mode 100644 drivers/soc/bcm/brcmstb/pm/pm-mips.c
 create mode 100644 drivers/soc/bcm/brcmstb/pm/pm.h
 create mode 100644 drivers/soc/bcm/brcmstb/pm/s2-arm.S
 create mode 100644 drivers/soc/bcm/brcmstb/pm/s2-mips.S
 create mode 100644 drivers/soc/bcm/brcmstb/pm/s3-mips.S

[GIT PULL 6/6 V2] Broadcom drivers changes for 4.14

[Olof Johansson]

Hi,

On Thu, Aug 24, 2017 at 5:56 PM, Florian Fainelli <f.fainelli@gmail.com> wrote:
> The following changes since commit 5771a8c08880cdca3bfb4a3fc6d309d6bba20877:
>
>   Linux v4.13-rc1 (2017-07-15 15:22:10 -0700)
>
> are available in the git repository at:
>
>   http://github.com/Broadcom/stblinux.git tags/arm-soc/for-4.14/drivers
>
> for you to fetch changes up to ed70bd0aa574d4922382ead47cd370174e31cb0e:
>
>   soc bcm: brcmstb: Add support for S2/S3/S5 suspend states (MIPS) (2017-08-24 17:49:43 -0700)

Per discussion on IRC earlier today -- I had missed this updated pull
request. Since it's been sitting in -next for a while through your
tree, I've queued it up as next/late now and we'll try to get it
merged later in the merge window.


-Olof

[GIT PULL 1/6 V2] Broadcom soc changes for 4.14

[Florian Fainelli]

On August 24, 2017 12:43:26 PM PDT, Florian Fainelli <f.fainelli@gmail.com> wrote:
>The following changes since commit
>5771a8c08880cdca3bfb4a3fc6d309d6bba20877:
>
>  Linux v4.13-rc1 (2017-07-15 15:22:10 -0700)
>
>are available in the git repository at:
>
>  http://github.com/Broadcom/stblinux.git tags/arm-soc/for-4.14/soc
>
>for you to fetch changes up to
>c9351923600e073083fc378c870c593cf98dd551:
>
>Merge tag 'bcm2835-soc-next-2017-08-24' into soc/next (2017-08-24
>11:47:29 -0700)
>
>----------------------------------------------------------------
>This pull request contains Broadcom ARM-based SoC arch/ changes for
>4.14,
>please pull the following:
>
>- Danilo removes the clock provider driver stubs which are no longer
>needed
>  now that we have a proper CPRMAN clock provider driver
>
>- Stefan moves the SMP startup code for BCM2836 from the interrupt
>controller
>driver down to where it belongs in the architecture code, this was
>requested
>  by Marc Zyngier before comitting any fixes to that code
>
>- Phil provides a fix for a future Raspberry Pi firmware which will
>make the
>secondary cores wait for an event and therefore requires the CPU
>onlining
>  other cores to send such event (along with the appropriate barrier)

Olof, Arnd, we talked about this on IRC a few weeks ago, can you take this in next/late? Thank you!

-- 
Florian