From: nick.hawkins@hpe.com
To: verdun@hpe.com, nick.hawkins@hpe.com, robh+dt@kernel.org,
daniel.lezcano@linaro.org, tglx@linutronix.de,
gregkh@linuxfoundation.org, wim@linux-watchdog.org,
linux@roeck-us.net, linux@armlinux.org.uk, arnd@arndb.de,
olof@lixom.net, joel@jms.id.au, soc@kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org, linux-watchdog@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 00/11] ARM: Introduce HPE GXP Architecture
Date: Wed, 20 Apr 2022 10:01:14 -0500 [thread overview]
Message-ID: <20220420150114.47356-1-nick.hawkins@hpe.com> (raw)
From: Nick Hawkins <nick.hawkins@hpe.com>
Changes since v3:
*Completely redid the dtsi file to represent architecture
*Reduced device tree size
*Rewrote the timer driver to start the watchdog driver due
to similar register region
*Made adjustments to timer
*Made adjustments to watchdog
*Changed gxp.yaml to hpe,gxp.yaml with changes
*Updated Maintainers to represent new file names
*Added hpe bindings to generic-ehci and generic-ohci
*Fixed clock architecture to be accurate
Changes since v2:
*Reduced size of changes, put them into patchset format
Changes since v1:
*Fixed compiler warnings
The GXP is the HPE BMC SoC that is used in the majority
of HPE Generation 10 servers. Traditionally the asic will
last multiple generations of server before being replaced.
Info about SoC:
HPE GXP is the name of the HPE Soc. This SoC is used to implement
many BMC features at HPE. It supports ARMv7 architecture based on
the Cortex A9 core. It is capable of using an AXI bus to which
a memory controller is attached. It has multiple SPI interfaces
to connect boot flash and BIOS flash. It uses a 10/100/1000 MAC
for network connectivity. It has multiple i2c engines to drive
connectivity with a host infrastructure. The initial patches
enable the watchdog and timer enabling the host to be able to
boot. Based on feedback from the device tree gxp-timer now
creates a gxp-wdt child because of similar register region.
Nick Hawkins (11):
arch: arm: mach-hpe: Introduce the HPE GXP architecture
arch: arm: configs: multi_v7_defconfig
drivers: wdt: Introduce HPE GXP SoC Watchdog
clocksource/drivers: Add HPE GXP timer
dt-bindings: timer: Add HPE GXP Timer Binding
dt-bindings: watchdog: Add HPE GXP Watchdog timer binding
dt-bindings: arm: Add HPE GXP Binding
dt-bindings: usb: generic-echi: Add HPE GXP echi binding
dt-bindings: usb: generic-ochi: Add HPE GXP ochi binding
arch: arm: boot: dts: Introduce HPE GXP Device tree
maintainers: Introduce HPE GXP Architecture
.../devicetree/bindings/arm/hpe,gxp.yaml | 22 +++
.../bindings/timer/hpe,gxp-timer.yaml | 49 +++++
.../devicetree/bindings/usb/generic-ehci.yaml | 1 +
.../devicetree/bindings/usb/generic-ohci.yaml | 1 +
.../bindings/watchdog/hpe,gxp-wdt.yaml | 30 +++
MAINTAINERS | 13 ++
arch/arm/Kconfig | 2 +
arch/arm/Makefile | 1 +
arch/arm/boot/dts/Makefile | 2 +
arch/arm/boot/dts/hpe-bmc-dl360gen10.dts | 13 ++
arch/arm/boot/dts/hpe-gxp.dtsi | 128 ++++++++++++
arch/arm/configs/multi_v7_defconfig | 3 +
arch/arm/mach-hpe/Kconfig | 17 ++
arch/arm/mach-hpe/Makefile | 1 +
arch/arm/mach-hpe/gxp.c | 16 ++
drivers/clocksource/Kconfig | 8 +
drivers/clocksource/Makefile | 1 +
drivers/clocksource/timer-gxp.c | 183 ++++++++++++++++++
drivers/watchdog/Kconfig | 8 +
drivers/watchdog/Makefile | 1 +
drivers/watchdog/gxp-wdt.c | 166 ++++++++++++++++
21 files changed, 666 insertions(+)
create mode 100644 Documentation/devicetree/bindings/arm/hpe,gxp.yaml
create mode 100644 Documentation/devicetree/bindings/timer/hpe,gxp-timer.yaml
create mode 100644 Documentation/devicetree/bindings/watchdog/hpe,gxp-wdt.yaml
create mode 100644 arch/arm/boot/dts/hpe-bmc-dl360gen10.dts
create mode 100644 arch/arm/boot/dts/hpe-gxp.dtsi
create mode 100644 arch/arm/mach-hpe/Kconfig
create mode 100644 arch/arm/mach-hpe/Makefile
create mode 100644 arch/arm/mach-hpe/gxp.c
create mode 100644 drivers/clocksource/timer-gxp.c
create mode 100644 drivers/watchdog/gxp-wdt.c
--
2.17.1
reply other threads:[~2022-04-20 15:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220420150114.47356-1-nick.hawkins@hpe.com \
--to=nick.hawkins@hpe.com \
--cc=arnd@arndb.de \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=joel@jms.id.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=linux@roeck-us.net \
--cc=olof@lixom.net \
--cc=robh+dt@kernel.org \
--cc=soc@kernel.org \
--cc=tglx@linutronix.de \
--cc=verdun@hpe.com \
--cc=wim@linux-watchdog.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;
as well as URLs for NNTP newsgroup(s).