[0/7] Broadcom SoC updates for 5.20

Message ID	20220711164451.3542127-1-f.fainelli@gmail.com
Headers	show Return-Path: <linux-arm-kernel-bounces+incoming-imx=patchwork.ozlabs.org@lists.infradead.org> From: Florian Fainelli <f.fainelli@gmail.com> To: soc@kernel.org Cc: Florian Fainelli <f.fainelli@gmail.com>, William Zhang <william.zhang@broadcom.com>, Peter Robinson <pbrobinson@gmail.com>, Nicolas Saenz Julienne <nsaenz@kernel.org>, Stefan Wahren <stefan.wahren@i2se.com>, Javier Martinez Canillas <javierm@redhat.com>, linux-arm-kernel@lists.infradead.org, arnd@arndb.de, olof@lixom.net, khilman@kernel.org, bcm-kernel-feedback-list@broadcom.com Subject: [PATCH 0/7] Broadcom SoC updates for 5.20 Date: Mon, 11 Jul 2022 09:44:44 -0700 Message-Id: <20220711164451.3542127-1-f.fainelli@gmail.com> MIME-Version: 1.0 preview: Hi Arnd, Olof, The highlights of the pull requests are: - William and Anand add support for a large number of Broadband Carrier Access (BCA) DSL/PON/Wi-Fi router chips under the ARCH_BCMBCA umbrella and we expect to see more activity in the future on these [...] Content analysis details: (-0.2 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at https://www.dnswl.org/, no trust [2607:f8b0:4864:20:0:0:0:62b listed in] [list.dnswl.org] -0.0 SPF_PASS SPF: sender matches SPF record 0.0 SPF_HELO_NONE SPF: HELO does not publish an SPF Record 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider [f.fainelli[at]gmail.com] -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID_EF Message has a valid DKIM or DK signature from envelope-from domain Precedence: list Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" <linux-arm-kernel-bounces@lists.infradead.org> Errors-To: linux-arm-kernel-bounces+incoming-imx=patchwork.ozlabs.org@lists.infradead.org
Series	Broadcom SoC updates for 5.20 \| expand [0/7] Broadcom SoC updates for 5.20 [GIT,PULL,1/7] Broadcom defconfig changes for 5.20 [GIT,PULL,2/7] Broadcom defconfig-arm64 changes for 5.20 [GIT,PULL,3/7] Broadcom devicetree changes for 5.20 [GIT,PULL,4/7] Broadcom devicetree-arm64 changes for 5.20 [GIT,PULL,5/7] Broadcom drivers changes for 5.20 [GIT,PULL,6/7] Broadcom maintainers changes for 5.20 [GIT,PULL,7/7] Broadcom soc changes for 5.20

Message ID

20220711164451.3542127-1-f.fainelli@gmail.com

Headers

From: Florian Fainelli <f.fainelli@gmail.com>
To: soc@kernel.org
Cc: Florian Fainelli <f.fainelli@gmail.com>,
	William Zhang <william.zhang@broadcom.com>,
	Peter Robinson <pbrobinson@gmail.com>,
	Nicolas Saenz Julienne <nsaenz@kernel.org>,
	Stefan Wahren <stefan.wahren@i2se.com>,
	Javier Martinez Canillas <javierm@redhat.com>,
	linux-arm-kernel@lists.infradead.org,
	arnd@arndb.de,
	olof@lixom.net,
	khilman@kernel.org,
	bcm-kernel-feedback-list@broadcom.com
Subject: [PATCH 0/7] Broadcom SoC updates for 5.20
Date: Mon, 11 Jul 2022 09:44:44 -0700
Message-Id: <20220711164451.3542127-1-f.fainelli@gmail.com>
MIME-Version: 1.0
Precedence: list
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: "linux-arm-kernel" <linux-arm-kernel-bounces@lists.infradead.org>
Errors-To: 
 linux-arm-kernel-bounces+incoming-imx=patchwork.ozlabs.org@lists.infradead.org

Series

Broadcom SoC updates for 5.20 | expand

Message

Florian Fainelli July 11, 2022, 4:44 p.m. UTC

Hi Arnd, Olof,

The highlights of the pull requests are:

- William and Anand add support for a large number of Broadband Carrier
  Access (BCA) DSL/PON/Wi-Fi router chips under the ARCH_BCMBCA umbrella
  and we expect to see more activity in the future on these chips.

- Peter, Nicolas and Stefan add support for the V3D GPU on the Raspberry
  Pi 4 (BCM2711)

You will meet the following conflict which was identified in linux-next:

https://lore.kernel.org/lkml/20220711095520.4fad4c97@canb.auug.org.au/

which can be resolved by removing arch/arm/mach-bcm/bcm63xx.c

Thanks to these changes having soaked in linux-next for a couple of
weeks, we do not expect other merge conflicts or problems.

Thank you!