Re: [PATCH v1 6/9] ARM: dts: Add device tree files for hpe gxp soc
On Fri, Jun 03, 2022 at 03:35:51PM +, Hawkins, Nick wrote: > > > You will need to post a sync periodically. Every Linux release (full, not > > -rc) would be great, every couple is fine. > > If there are changes I need in the device tree for u-boot that are not > currently in Linux do they need to be in Linux first? Or is that what > the usage of appending "-u-boot.dtsi" is for? So, we have attributes such as "u-boot,dm-spl" that are still in the process of being upstreamed. Those do not go in the dts that is sent to Linux but instead a -u-boot.dtsi file. It might be most helpful for you to pick another ARMv7 platform you're familiar with that also has one of those and explore. -- Tom signature.asc Description: PGP signature
RE: [PATCH v1 6/9] ARM: dts: Add device tree files for hpe gxp soc
> You will need to post a sync periodically. Every Linux release (full, not > -rc) would be great, every couple is fine. If there are changes I need in the device tree for u-boot that are not currently in Linux do they need to be in Linux first? Or is that what the usage of appending "-u-boot.dtsi" is for? Thanks for the help, -Nick Hawkins
Re: [PATCH v1 6/9] ARM: dts: Add device tree files for hpe gxp soc
On Thu, Jun 02, 2022 at 08:56:59PM +, Hawkins, Nick wrote: > > > -Original Message- > From: Hawkins, Nick > Sent: Thursday, June 2, 2022 3:56 PM > To: Tom Rini > Cc: Verdun, Jean-Marie ; u-boot@lists.denx.de > Subject: RE: [PATCH v1 6/9] ARM: dts: Add device tree files for hpe gxp soc > > > > > The dts files need to be in linux-next (or similar) upstream before we > > > > start taking them in to Linux, and then re-synced periodically. > > > > > > Hi Tom, > > > > > > When you say taking them into Linux do you mean these files for U-Boot > > > would go into Torvalds Linux? Ideally we would like to have the one from > > > Torvalds Linux come into U-boot. Our DTS files are currently here at > > > Linux-next: > > > > > > https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/arch/arm/boot/dts > > > Correct, we want to use those files as-is, and then only append to them via > > a "-u-boot.dtsi" file. > > Hi Tom, > > I accidently hit return. Will I need to manually merge these files from Linux > or will someone else do that? You will need to post a sync periodically. Every Linux release (full, not -rc) would be great, every couple is fine. -- Tom signature.asc Description: PGP signature
RE: [PATCH v1 6/9] ARM: dts: Add device tree files for hpe gxp soc
-Original Message- From: Hawkins, Nick Sent: Thursday, June 2, 2022 3:56 PM To: Tom Rini Cc: Verdun, Jean-Marie ; u-boot@lists.denx.de Subject: RE: [PATCH v1 6/9] ARM: dts: Add device tree files for hpe gxp soc > > > The dts files need to be in linux-next (or similar) upstream before we > > > start taking them in to Linux, and then re-synced periodically. > > > > Hi Tom, > > > > When you say taking them into Linux do you mean these files for U-Boot > > would go into Torvalds Linux? Ideally we would like to have the one from > > Torvalds Linux come into U-boot. Our DTS files are currently here at > > Linux-next: > > > > https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/arch/arm/boot/dts > Correct, we want to use those files as-is, and then only append to them via a > "-u-boot.dtsi" file. Hi Tom, I accidently hit return. Will I need to manually merge these files from Linux or will someone else do that? Thanks, -Nick Hawkins
RE: [PATCH v1 6/9] ARM: dts: Add device tree files for hpe gxp soc
> > > The dts files need to be in linux-next (or similar) upstream before we > > > start taking them in to Linux, and then re-synced periodically. > > > > Hi Tom, > > > > When you say taking them into Linux do you mean these files for U-Boot > > would go into Torvalds Linux? Ideally we would like to have the one from > > Torvalds Linux come into U-boot. Our DTS files are currently here at > > Linux-next: > > > > https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/arch/arm/boot/dts > Correct, we want to use those files as-is, and then only append to them via a > "-u-boot.dtsi" file. Hi Tom,
Re: [PATCH v1 6/9] ARM: dts: Add device tree files for hpe gxp soc
On Wed, Jun 01, 2022 at 02:50:26PM +, Hawkins, Nick wrote: > > > > > > > The HPE SoC is new to linux. A basic device tree layout with minimum > > > required for linux to boot including a timer and watchdog support has > > > been created. > > > > > > The dts file is empty at this point but will be updated in subsequent > > > updates as board specific features are enabled. > > > > > > Signed-off-by: Nick Hawkins > > > --- > > > arch/arm/dts/Makefile | 2 + > > > arch/arm/dts/hpe-bmc-dl360gen10.dts | 26 > > > arch/arm/dts/hpe-gxp.dtsi | 95 + > > > 3 files changed, 123 insertions(+) > > > create mode 100644 arch/arm/dts/hpe-bmc-dl360gen10.dts > > > create mode 100644 arch/arm/dts/hpe-gxp.dtsi > > > The dts files need to be in linux-next (or similar) upstream before we > > start taking them in to Linux, and then re-synced periodically. > > Hi Tom, > > When you say taking them into Linux do you mean these files for U-Boot would > go into Torvalds Linux? Ideally we would like to have the one from Torvalds > Linux come into U-boot. Our DTS files are currently here at Linux-next: > > https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/arch/arm/boot/dts Correct, we want to use those files as-is, and then only append to them via a "-u-boot.dtsi" file. -- Tom signature.asc Description: PGP signature
RE: [PATCH v1 6/9] ARM: dts: Add device tree files for hpe gxp soc
> > > > The HPE SoC is new to linux. A basic device tree layout with minimum > > required for linux to boot including a timer and watchdog support has > > been created. > > > > The dts file is empty at this point but will be updated in subsequent > > updates as board specific features are enabled. > > > > Signed-off-by: Nick Hawkins > > --- > > arch/arm/dts/Makefile | 2 + > > arch/arm/dts/hpe-bmc-dl360gen10.dts | 26 > > arch/arm/dts/hpe-gxp.dtsi | 95 + > > 3 files changed, 123 insertions(+) > > create mode 100644 arch/arm/dts/hpe-bmc-dl360gen10.dts > > create mode 100644 arch/arm/dts/hpe-gxp.dtsi > The dts files need to be in linux-next (or similar) upstream before we start > taking them in to Linux, and then re-synced periodically. Hi Tom, When you say taking them into Linux do you mean these files for U-Boot would go into Torvalds Linux? Ideally we would like to have the one from Torvalds Linux come into U-boot. Our DTS files are currently here at Linux-next: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/arch/arm/boot/dts Thank you for all the feedback you have provided on this and the other patches. I will start working on them. -Nick
Re: [PATCH v1 6/9] ARM: dts: Add device tree files for hpe gxp soc
On Thu, May 26, 2022 at 01:55:45PM -0500, nick.hawk...@hpe.com wrote: > From: Nick Hawkins > > The HPE SoC is new to linux. A basic device tree layout with minimum > required for linux to boot including a timer and watchdog support has > been created. > > The dts file is empty at this point but will be updated in subsequent > updates as board specific features are enabled. > > Signed-off-by: Nick Hawkins > --- > arch/arm/dts/Makefile | 2 + > arch/arm/dts/hpe-bmc-dl360gen10.dts | 26 > arch/arm/dts/hpe-gxp.dtsi | 95 + > 3 files changed, 123 insertions(+) > create mode 100644 arch/arm/dts/hpe-bmc-dl360gen10.dts > create mode 100644 arch/arm/dts/hpe-gxp.dtsi The dts files need to be in linux-next (or similar) upstream before we start taking them in to Linux, and then re-synced periodically. -- Tom signature.asc Description: PGP signature
[PATCH v1 6/9] ARM: dts: Add device tree files for hpe gxp soc
From: Nick Hawkins
The HPE SoC is new to linux. A basic device tree layout with minimum
required for linux to boot including a timer and watchdog support has
been created.
The dts file is empty at this point but will be updated in subsequent
updates as board specific features are enabled.
Signed-off-by: Nick Hawkins
---
arch/arm/dts/Makefile | 2 +
arch/arm/dts/hpe-bmc-dl360gen10.dts | 26
arch/arm/dts/hpe-gxp.dtsi | 95 +
3 files changed, 123 insertions(+)
create mode 100644 arch/arm/dts/hpe-bmc-dl360gen10.dts
create mode 100644 arch/arm/dts/hpe-gxp.dtsi
diff --git a/arch/arm/dts/Makefile b/arch/arm/dts/Makefile
index 83630af4f6..6223998eb7 100644
--- a/arch/arm/dts/Makefile
+++ b/arch/arm/dts/Makefile
@@ -1213,6 +1213,8 @@ dtb-$(CONFIG_TARGET_POMELO) += phytium-pomelo.dtb
dtb-$(CONFIG_TARGET_PRESIDIO_ASIC) += ca-presidio-engboard.dtb
+dtb-$(CONFIG_TARGET_GXP) += hpe-bmc-dl360gen10.dts
+
dtb-$(CONFIG_TARGET_IMX8MM_CL_IOT_GATE) += imx8mm-cl-iot-gate.dtb \
imx8mm-cl-iot-gate-ied.dtbo \
imx8mm-cl-iot-gate-ied-adc0.dtbo \
diff --git a/arch/arm/dts/hpe-bmc-dl360gen10.dts
b/arch/arm/dts/hpe-bmc-dl360gen10.dts
new file mode 100644
index 00..3a7382ce40
--- /dev/null
+++ b/arch/arm/dts/hpe-bmc-dl360gen10.dts
@@ -0,0 +1,26 @@
+// SPDX-License-Identifier: GPL-2.0
+/*
+ * Device Tree file for HPE DL360Gen10
+ */
+
+/include/ "hpe-gxp.dtsi"
+
+/ {
+ #address-cells = <1>;
+ #size-cells = <1>;
+ compatible = "hpe,gxp-dl360gen10", "hpe,gxp";
+ model = "Hewlett Packard Enterprise ProLiant dl360 Gen10";
+
+ aliases {
+ serial0 =
+ };
+
+ chosen {
+ stdout-path = "serial0:115200n8";
+ };
+
+ memory@4000 {
+ device_type = "memory";
+ reg = <0x4000 0x2000>;
+ };
+};
diff --git a/arch/arm/dts/hpe-gxp.dtsi b/arch/arm/dts/hpe-gxp.dtsi
new file mode 100644
index 00..fbf817ee04
--- /dev/null
+++ b/arch/arm/dts/hpe-gxp.dtsi
@@ -0,0 +1,95 @@
+// SPDX-License-Identifier: GPL-2.0
+/*
+ * Device Tree file for HPE GXP
+ */
+
+/dts-v1/;
+/ {
+ model = "Hewlett Packard Enterprise GXP BMC";
+ compatible = "hpe,gxp";
+ #address-cells = <1>;
+ #size-cells = <1>;
+
+ cpus {
+ #address-cells = <1>;
+ #size-cells = <0>;
+
+ cpu@0 {
+ compatible = "arm,cortex-a9";
+ reg = <0>;
+ device_type = "cpu";
+ next-level-cache = <>;
+ };
+ };
+
+ clocks {
+ pll: clock-0 {
+ compatible = "fixed-clock";
+ #clock-cells = <0>;
+ clock-frequency = <16>;
+ };
+
+ iopclk: clock-1 {
+ compatible = "fixed-factor-clock";
+ #clock-cells = <0>;
+ clock-div = <4>;
+ clock-mult = <1>;
+ clocks = <>;
+ };
+ };
+
+ axi {
+ compatible = "simple-bus";
+ #address-cells = <1>;
+ #size-cells = <1>;
+ ranges;
+ dma-ranges;
+
+ L2: cache-controller@b004 {
+ compatible = "arm,pl310-cache";
+ reg = <0xb004 0x1000>;
+ cache-unified;
+ cache-level = <2>;
+ };
+
+ ahb@c000 {
+ compatible = "simple-bus";
+ #address-cells = <1>;
+ #size-cells = <1>;
+ ranges = <0x0 0xc000 0x3000>;
+ dma-ranges;
+
+ vic0: interrupt-controller@eff {
+ compatible = "arm,pl192-vic";
+ reg = <0xeff 0x1000>;
+ interrupt-controller;
+ #interrupt-cells = <1>;
+ };
+
+ vic1: interrupt-controller@80f0 {
+ compatible = "arm,pl192-vic";
+ reg = <0x80f0 0x1000>;
+ interrupt-controller;
+ #interrupt-cells = <1>;
+ };
+
+ uartc: serial@f0 {
+ compatible = "ns16550a";
+ reg = <0xf0 0x8>;
+ interrupts = <19>;
+ interrupt-parent = <>;
+ clock-frequency = <1846153>;
+ reg-shift = <0>;
+ };
+
+
