public inbox for linux-crypto@vger.kernel.org
 help / color / mirror / Atom feed
From: William Zhang <william.zhang@broadcom.com>
To: Linux ARM List <linux-arm-kernel@lists.infradead.org>
Cc: joel.peshkin@broadcom.com, kursad.oney@broadcom.com,
	f.fainelli@gmail.com, anand.gore@broadcom.com,
	"Broadcom Kernel List" <bcm-kernel-feedback-list@broadcom.com>,
	philippe.reynes@softathome.com, dan.beygelman@broadcom.com,
	"William Zhang" <william.zhang@broadcom.com>,
	"Al Cooper" <alcooperx@gmail.com>,
	"Andre Przywara" <andre.przywara@arm.com>,
	"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
	"Ard Biesheuvel" <ardb@kernel.org>,
	"Arnd Bergmann" <arnd@arndb.de>,
	"Cai Huoqing" <cai.huoqing@linux.dev>,
	"Conor Dooley" <conor.dooley@microchip.com>,
	"Damien Le Moal" <damien.lemoal@opensource.wdc.com>,
	"Dmitry Osipenko" <digetx@gmail.com>,
	"Eugen Hristev" <eugen.hristev@microchip.com>,
	"Geert Uytterhoeven" <geert+renesas@glider.be>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Herbert Xu" <herbert@gondor.apana.org.au>,
	"Jan Dabros" <jsd@semihalf.com>,
	"Jarkko Nikula" <jarkko.nikula@linux.intel.com>,
	"Jie Deng" <jie.deng@intel.com>,
	"Jiri Slaby" <jirislaby@kernel.org>,
	"Joel Stanley" <joel@jms.id.au>,
	"Kavyasree Kotagiri" <kavyasree.kotagiri@microchip.com>,
	"Kishon Vijay Abraham I" <kishon@ti.com>,
	"Krzysztof Kozlowski" <krzk@kernel.org>,
	"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
	"Lukas Bulwahn" <lukas.bulwahn@gmail.com>,
	"Mark Brown" <broonie@kernel.org>,
	"Matt Mackall" <mpm@selenic.com>,
	"Michael Turquette" <mturquette@baylibre.com>,
	"Michael Walle" <michael@walle.cc>,
	"Nathan Chancellor" <nathan@kernel.org>,
	"Nicolas Ferre" <nicolas.ferre@microchip.com>,
	"Olof Johansson" <olof@lixom.net>,
	"Rafał Miłecki" <rafal@milecki.pl>, "Ray Jui" <rjui@broadcom.com>,
	"Rob Herring" <robh+dt@kernel.org>,
	"Rob Herring" <robh@kernel.org>,
	"Russell King" <linux@armlinux.org.uk>,
	"Sam Protsenko" <semen.protsenko@linaro.org>,
	"Scott Branden" <sbranden@broadcom.com>,
	"Stephan Gerhold" <stephan@gerhold.net>,
	"Stephen Boyd" <sboyd@kernel.org>,
	"Sunil Goutham" <sgoutham@marvell.com>,
	"Sven Peter" <sven@svenpeter.dev>,
	"Thierry Reding" <treding@nvidia.com>,
	"Thomas Bogendoerfer" <tsbogend@alpha.franken.de>,
	"Tyrone Ting" <kfting@nuvoton.com>,
	"Vinod Koul" <vkoul@kernel.org>, "Wolfram Sang" <wsa@kernel.org>,
	devicetree@vger.kernel.org, linux-clk@vger.kernel.org,
	linux-crypto@vger.kernel.org, linux-i2c@vger.kernel.org,
	linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-phy@lists.infradead.org, linux-serial@vger.kernel.org,
	linux-spi@vger.kernel.org, soc@kernel.org
Subject: [PATCH 0/9] arm: bcmbca: Move BCM63138 SoC support under ARCH_BCMBCA
Date: Tue,  5 Jul 2022 10:26:04 -0700	[thread overview]
Message-ID: <20220705172613.21152-1-william.zhang@broadcom.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1932 bytes --]

Now that Broadcom Broadband arch ARCH_BCMBCA is in the kernel, this change
migrates the existing broadband chip BCM63138 support to ARCH_BCMBCA. It also
delete the old ARCH_BCM_63XX config as no other chip uses it.

Verified on BCM963138REF board with ramdisk boot.


William Zhang (9):
  dt-bindings: arm: add BCM63138 SoC
  ARM: dts: Move BCM963138DVT board dts to ARCH_BCMBCA
  ARM: dts: update dts files for bcmbca SoC BCM63138
  ARM: dts: Add BCM63138 generic board dts
  arm: bcmbca: Replace ARCH_BCM_63XX with ARCH_BCMBCA
  arm: bcmbca: Move BCM63138 ARCH_BCM_63XX config to ARCH_BCMBCA
  arm: bcmbca: Add BCMBCA sub platforms
  MAINTAINERS: Move BCM63138 to bcmbca arch entry
  ARM: multi_v7_defconfig: Update configs for BCM63138

 .../bindings/arm/bcm/brcm,bcmbca.yaml         |  8 +++
 MAINTAINERS                                   | 10 +--
 arch/arm/Kconfig.debug                        |  2 +-
 arch/arm/boot/dts/Makefile                    |  4 +-
 arch/arm/boot/dts/bcm63138.dtsi               | 18 +++---
 arch/arm/boot/dts/bcm963138.dts               | 26 ++++++++
 arch/arm/boot/dts/bcm963138dvt.dts            |  8 +--
 arch/arm/configs/multi_v7_defconfig           |  4 +-
 arch/arm/mach-bcm/Kconfig                     | 61 +++++++++++++------
 arch/arm/mach-bcm/Makefile                    |  7 +--
 arch/arm/mach-bcm/bcm63xx.c                   | 17 ------
 drivers/ata/Kconfig                           |  2 +-
 drivers/char/hw_random/Kconfig                |  2 +-
 drivers/clk/bcm/Kconfig                       |  4 +-
 drivers/i2c/busses/Kconfig                    |  2 +-
 drivers/phy/broadcom/Kconfig                  |  2 +-
 drivers/spi/Kconfig                           |  2 +-
 drivers/tty/serial/Kconfig                    |  4 +-
 18 files changed, 108 insertions(+), 75 deletions(-)
 create mode 100644 arch/arm/boot/dts/bcm963138.dts
 delete mode 100644 arch/arm/mach-bcm/bcm63xx.c

-- 
2.34.1


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4212 bytes --]

             reply	other threads:[~2022-07-05 17:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-05 17:26 William Zhang [this message]
2022-07-05 17:26 ` [PATCH 5/9] arm: bcmbca: Replace ARCH_BCM_63XX with ARCH_BCMBCA William Zhang
2022-07-05 19:10   ` Wolfram Sang
2022-07-06  3:45   ` Damien Le Moal
2022-07-06 16:52   ` Vinod Koul

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=20220705172613.21152-1-william.zhang@broadcom.com \
    --to=william.zhang@broadcom.com \
    --cc=alcooperx@gmail.com \
    --cc=anand.gore@broadcom.com \
    --cc=andre.przywara@arm.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=ardb@kernel.org \
    --cc=arnd@arndb.de \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=broonie@kernel.org \
    --cc=cai.huoqing@linux.dev \
    --cc=conor.dooley@microchip.com \
    --cc=damien.lemoal@opensource.wdc.com \
    --cc=dan.beygelman@broadcom.com \
    --cc=devicetree@vger.kernel.org \
    --cc=digetx@gmail.com \
    --cc=eugen.hristev@microchip.com \
    --cc=f.fainelli@gmail.com \
    --cc=geert+renesas@glider.be \
    --cc=gregkh@linuxfoundation.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=jarkko.nikula@linux.intel.com \
    --cc=jie.deng@intel.com \
    --cc=jirislaby@kernel.org \
    --cc=joel.peshkin@broadcom.com \
    --cc=joel@jms.id.au \
    --cc=jsd@semihalf.com \
    --cc=kavyasree.kotagiri@microchip.com \
    --cc=kfting@nuvoton.com \
    --cc=kishon@ti.com \
    --cc=krzk@kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=kursad.oney@broadcom.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-phy@lists.infradead.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=lukas.bulwahn@gmail.com \
    --cc=michael@walle.cc \
    --cc=mpm@selenic.com \
    --cc=mturquette@baylibre.com \
    --cc=nathan@kernel.org \
    --cc=nicolas.ferre@microchip.com \
    --cc=olof@lixom.net \
    --cc=philippe.reynes@softathome.com \
    --cc=rafal@milecki.pl \
    --cc=rjui@broadcom.com \
    --cc=robh+dt@kernel.org \
    --cc=robh@kernel.org \
    --cc=sboyd@kernel.org \
    --cc=sbranden@broadcom.com \
    --cc=semen.protsenko@linaro.org \
    --cc=sgoutham@marvell.com \
    --cc=soc@kernel.org \
    --cc=stephan@gerhold.net \
    --cc=sven@svenpeter.dev \
    --cc=treding@nvidia.com \
    --cc=tsbogend@alpha.franken.de \
    --cc=vkoul@kernel.org \
    --cc=wsa@kernel.org \
    /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