Linux SOC development
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: soc@kernel.org
Cc: "Pierre Gondois" <pierre.gondois@arm.com>,
	"William Zhang" <william.zhang@broadcom.com>,
	"Florian Fainelli" <f.fainelli@gmail.com>,
	"Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>,
	"Rafał Miłecki" <rafal@milecki.pl>,
	linux-arm-kernel@lists.infradead.org, arnd@arndb.de,
	olof@lixom.net, khilman@kernel.org,
	bcm-kernel-feedback-list@broadcom.com
Subject: [GIT PULL 2/3] Broadcom devicetree-arm64 changes for 6.2
Date: Tue, 29 Nov 2022 11:17:54 -0800	[thread overview]
Message-ID: <20221129191755.542584-2-f.fainelli@gmail.com> (raw)
In-Reply-To: <20221129191755.542584-1-f.fainelli@gmail.com>

The following changes since commit 9abf2313adc1ca1b6180c508c25f22f9395cc780:

  Linux 6.1-rc1 (2022-10-16 15:36:24 -0700)

are available in the Git repository at:

  https://github.com/Broadcom/stblinux.git tags/arm-soc/for-6.2/devicetree-arm64

for you to fetch changes up to e567e58d6819adc002c57b81e16b88da24d3b4aa:

  arm64: dts: Update cache properties for broadcom (2022-11-28 15:37:41 -0800)

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

- Rafal describes the timer/watchdog block for the BCM4908 and BCM6858
  SoCs

- Krzysztof corrects invalid "reg" properties for the memory nodes that
  were off by one digit

- Pierre updates a number of cache Device Tree node properties to be
  schema compliant

----------------------------------------------------------------
Krzysztof Kozlowski (1):
      arm64: dts: broadcom: trim addresses to 8 digits

Pierre Gondois (1):
      arm64: dts: Update cache properties for broadcom

Rafał Miłecki (2):
      arm64: dts: broadcom: bcmbca: bcm4908: add TWD block timer
      arm64: dts: broadcom: bcmbca: bcm6858: add TWD block

 arch/arm64/boot/dts/broadcom/bcmbca/bcm4908.dtsi    |  6 ++++++
 arch/arm64/boot/dts/broadcom/bcmbca/bcm4912.dtsi    |  1 +
 arch/arm64/boot/dts/broadcom/bcmbca/bcm63146.dtsi   |  1 +
 arch/arm64/boot/dts/broadcom/bcmbca/bcm63158.dtsi   |  1 +
 arch/arm64/boot/dts/broadcom/bcmbca/bcm6813.dtsi    |  1 +
 arch/arm64/boot/dts/broadcom/bcmbca/bcm6856.dtsi    |  1 +
 arch/arm64/boot/dts/broadcom/bcmbca/bcm6858.dtsi    | 20 ++++++++++++++++++++
 arch/arm64/boot/dts/broadcom/northstar2/ns2-svk.dts |  2 +-
 arch/arm64/boot/dts/broadcom/northstar2/ns2-xmc.dts |  2 +-
 arch/arm64/boot/dts/broadcom/northstar2/ns2.dtsi    |  1 +
 arch/arm64/boot/dts/broadcom/stingray/stingray.dtsi |  4 ++++
 11 files changed, 38 insertions(+), 2 deletions(-)

  reply	other threads:[~2022-11-29 19:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-29 19:17 [GIT PULL 1/3] Broadcom devicetree changes for 6.2 Florian Fainelli
2022-11-29 19:17 ` Florian Fainelli [this message]
2022-11-29 19:17 ` [GIT PULL 3/3] Broadcom drivers " Florian Fainelli
2022-11-30 17:11 ` [GIT PULL 1/3] Broadcom devicetree " patchwork-bot+linux-soc

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20221129191755.542584-2-f.fainelli@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=arnd@arndb.de \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=khilman@kernel.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=olof@lixom.net \
    --cc=pierre.gondois@arm.com \
    --cc=rafal@milecki.pl \
    --cc=soc@kernel.org \
    --cc=william.zhang@broadcom.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox