From: Nick Hawkins <nick.hawkins@hpe.com>
Add the HPE GSC ARM64 BMC SoC compatibles to the existing
hpe,gxp.yaml binding.
The initial board compatible is hpe,gsc-dl340gen12 for the DL340 Gen12
server platform.
Add the arm64 DTS path to the existing ARM/HPE GXP MAINTAINERS entry,
renamed to ARM/HPE GXP/GSC ARCHITECTURE.
Signed-off-by: Nick Hawkins <nick.hawkins@hpe.com>
---
Documentation/devicetree/bindings/arm/hpe,gxp.yaml | 7 ++++++-
MAINTAINERS | 3 ++-
2 files changed, 8 insertions(+), 2 deletions(-)
diff --git a/Documentation/devicetree/bindings/arm/hpe,gxp.yaml b/Documentation/devicetree/bindings/arm/hpe,gxp.yaml
index 224bbcb93f95..6f057cd58571 100644
--- a/Documentation/devicetree/bindings/arm/hpe,gxp.yaml
+++ b/Documentation/devicetree/bindings/arm/hpe,gxp.yaml
@@ -4,7 +4,7 @@
$id: http://devicetree.org/schemas/arm/hpe,gxp.yaml#
$schema: http://devicetree.org/meta-schemas/core.yaml#
-title: HPE BMC GXP platforms
+title: HPE BMC GXP and GSC platforms
maintainers:
- Nick Hawkins <nick.hawkins@hpe.com>
@@ -18,6 +18,11 @@ properties:
- enum:
- hpe,gxp-dl360gen10
- const: hpe,gxp
+ - description: GSC Based Boards
+ items:
+ - enum:
+ - hpe,gsc-dl340gen12
+ - const: hpe,gsc
required:
- compatible
diff --git a/MAINTAINERS b/MAINTAINERS
index 2265e2c9bfbe..80c66de5e342 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -2859,7 +2859,7 @@ T: git git://git.kernel.org/pub/scm/linux/kernel/git/kristoffer/linux-hpc.git
F: arch/arm/mach-sa1100/include/mach/jornada720.h
F: arch/arm/mach-sa1100/jornada720.c
-ARM/HPE GXP ARCHITECTURE
+ARM/HPE GXP/GSC ARCHITECTURE
M: Jean-Marie Verdun <verdun@hpe.com>
M: Nick Hawkins <nick.hawkins@hpe.com>
S: Maintained
@@ -2870,6 +2870,7 @@ F: Documentation/devicetree/bindings/spi/hpe,gxp-spifi.yaml
F: Documentation/devicetree/bindings/timer/hpe,gxp-timer.yaml
F: Documentation/hwmon/gxp-fan-ctrl.rst
F: arch/arm/boot/dts/hpe/
+F: arch/arm64/boot/dts/hpe/
F: drivers/clocksource/timer-gxp.c
F: drivers/hwmon/gxp-fan-ctrl.c
F: drivers/i2c/busses/i2c-gxp.c
--
2.34.1On Fri, Mar 27, 2026 at 12:44:43PM -0500, nick.hawkins@hpe.com wrote: > From: Nick Hawkins <nick.hawkins@hpe.com> > > Add the HPE GSC ARM64 BMC SoC compatibles to the existing > hpe,gxp.yaml binding. > > The initial board compatible is hpe,gsc-dl340gen12 for the DL340 Gen12 > server platform. > > Add the arm64 DTS path to the existing ARM/HPE GXP MAINTAINERS entry, > renamed to ARM/HPE GXP/GSC ARCHITECTURE. > > Signed-off-by: Nick Hawkins <nick.hawkins@hpe.com> > --- > Documentation/devicetree/bindings/arm/hpe,gxp.yaml | 7 ++++++- > MAINTAINERS | 3 ++- > 2 files changed, 8 insertions(+), 2 deletions(-) > > diff --git a/Documentation/devicetree/bindings/arm/hpe,gxp.yaml b/Documentation/devicetree/bindings/arm/hpe,gxp.yaml > index 224bbcb93f95..6f057cd58571 100644 > --- a/Documentation/devicetree/bindings/arm/hpe,gxp.yaml > +++ b/Documentation/devicetree/bindings/arm/hpe,gxp.yaml > @@ -4,7 +4,7 @@ > $id: http://devicetree.org/schemas/arm/hpe,gxp.yaml# > $schema: http://devicetree.org/meta-schemas/core.yaml# > > -title: HPE BMC GXP platforms > +title: HPE BMC GXP and GSC platforms > > maintainers: > - Nick Hawkins <nick.hawkins@hpe.com> > @@ -18,6 +18,11 @@ properties: > - enum: > - hpe,gxp-dl360gen10 > - const: hpe,gxp > + - description: GSC Based Boards > + items: > + - enum: > + - hpe,gsc-dl340gen12 > + - const: hpe,gsc What sort of ordering are you going to use in this file? Usual choice is the fallback compatible, but I see you have chosen something else. That is fine, just keep that else sorting in the future instead of adding to the end. Best regards, Krzysztof
Hi Krzysztof Kozlowski,
> > maintainers:
> > - Nick Hawkins <nick.hawkins@hpe.com>
> > @@ -18,6 +18,11 @@ properties:
> > - enum:
> > - hpe,gxp-dl360gen10
> > - const: hpe,gxp
> > + - description: GSC Based Boards
> > + items:
> > + - enum:
> > + - hpe,gsc-dl340gen12
> > + - const: hpe,gsc
> What sort of ordering are you going to use in this file? Usual choice is
> the fallback compatible, but I see you have chosen something else. That
> is fine, just keep that else sorting in the future instead of adding to
> the end.
Thank you for the feedback, just to confirm are you looking for me
to do something like this?:
- description: GSC Based Boards
items:
- enum:
- hpe,gsc-dl340gen12
- const: hpe,gsc
- description: GXP Based Boards
items:
- enum:
- hpe,gxp-dl360gen10
- const: hpe,gxp
That way we have the newest first and going forward if there is
something newer we add it to the top of the list rather than
the bottom?
Thanks,
-Nick Hawkins
On 30/03/2026 16:53, Hawkins, Nick wrote: > Hi Krzysztof Kozlowski, > >>> maintainers: >>> - Nick Hawkins <nick.hawkins@hpe.com> >>> @@ -18,6 +18,11 @@ properties: >>> - enum: >>> - hpe,gxp-dl360gen10 >>> - const: hpe,gxp >>> + - description: GSC Based Boards >>> + items: >>> + - enum: >>> + - hpe,gsc-dl340gen12 >>> + - const: hpe,gsc > >> What sort of ordering are you going to use in this file? Usual choice is >> the fallback compatible, but I see you have chosen something else. That >> is fine, just keep that else sorting in the future instead of adding to >> the end. > > Thank you for the feedback, just to confirm are you looking for me > to do something like this?: > > - description: GSC Based Boards > items: > - enum: > - hpe,gsc-dl340gen12 > - const: hpe,gsc > - description: GXP Based Boards > items: > - enum: > - hpe,gxp-dl360gen10 > - const: hpe,gxp Yes, that's the typical/usual way. > > That way we have the newest first and going forward if there is Usual order is the alphanumerical. > something newer we add it to the top of the list rather than > the bottom? If you want to order by date of release of the SoC, that's fine. I think Allwinner does it. It's pretty non obvious because the chips are upstreamed different time than released, so it is difficult for people knot knowing the release dates. Just don't use the rule of "add at the beginning" or "at the end". Best regards, Krzysztof
© 2016 - 2026 Red Hat, Inc.