From: nick.hawkins@hpe.com
To: soc@kernel.org, arnd@arndb.de, verdun@hpe.com,
nick.hawkins@hpe.com, krzysztof.kozlowski+dt@linaro.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH v1 0/1] ARM: Correct HPE GXP Register ranges
Date: Mon, 30 Jan 2023 16:00:55 -0600 [thread overview]
Message-ID: <20230130220056.14349-1-nick.hawkins@hpe.com> (raw)
From: Nick Hawkins <nick.hawkins@hpe.com>
The GXP SoC has a large range of registers. This patch will expand the
registers available to SoC by modifying its device tree file. Initially
this change was planned to be part of a larger set but feedback
indicated it should be submitted separately. In the device tree file
there is a large gap in the ranges of registers available because they
are reserved.
Nick Hawkins (1):
ARM: dts: hpe: Correct GXP register ranges
arch/arm/boot/dts/hpe-gxp.dtsi | 41 +++++++++++++++++-----------------
1 file changed, 20 insertions(+), 21 deletions(-)
--
2.17.1
WARNING: multiple messages have this Message-ID (diff)
From: nick.hawkins@hpe.com
To: soc@kernel.org, arnd@arndb.de, verdun@hpe.com,
nick.hawkins@hpe.com, krzysztof.kozlowski+dt@linaro.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH v1 0/1] ARM: Correct HPE GXP Register ranges
Date: Mon, 30 Jan 2023 16:00:55 -0600 [thread overview]
Message-ID: <20230130220056.14349-1-nick.hawkins@hpe.com> (raw)
From: Nick Hawkins <nick.hawkins@hpe.com>
The GXP SoC has a large range of registers. This patch will expand the
registers available to SoC by modifying its device tree file. Initially
this change was planned to be part of a larger set but feedback
indicated it should be submitted separately. In the device tree file
there is a large gap in the ranges of registers available because they
are reserved.
Nick Hawkins (1):
ARM: dts: hpe: Correct GXP register ranges
arch/arm/boot/dts/hpe-gxp.dtsi | 41 +++++++++++++++++-----------------
1 file changed, 20 insertions(+), 21 deletions(-)
--
2.17.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2023-01-30 22:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 22:00 nick.hawkins [this message]
2023-01-30 22:00 ` [PATCH v1 0/1] ARM: Correct HPE GXP Register ranges nick.hawkins
2023-01-30 22:00 ` [PATCH v1 1/1] ARM: dts: hpe: Correct GXP register ranges nick.hawkins
2023-01-30 22:00 ` nick.hawkins
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=20230130220056.14349-1-nick.hawkins@hpe.com \
--to=nick.hawkins@hpe.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=soc@kernel.org \
--cc=verdun@hpe.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.