From: Tom Rini <trini@konsulko.com>
To: nick.hawkins@hpe.com
Cc: verdun@hpe.com, u-boot@lists.denx.de
Subject: Re: [PATCH v1 6/9] ARM: dts: Add device tree files for hpe gxp soc
Date: Wed, 1 Jun 2022 10:24:14 -0400 [thread overview]
Message-ID: <20220601142414.GG25375@bill-the-cat> (raw)
In-Reply-To: <20220526185548.14104-6-nick.hawkins@hpe.com>
[-- Attachment #1: Type: text/plain, Size: 951 bytes --]
On Thu, May 26, 2022 at 01:55:45PM -0500, nick.hawkins@hpe.com wrote:
> From: Nick Hawkins <nick.hawkins@hpe.com>
>
> 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 <nick.hawkins@hpe.com>
> ---
> 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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2022-06-01 14:24 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-26 18:55 [PATCH v1 1/9] ARM: hpe: gxp: add core support nick.hawkins
2022-05-26 18:55 ` [PATCH v1 2/9] timer: gxp: Add HPE GXP timer support nick.hawkins
2022-05-26 18:55 ` [PATCH v1 3/9] board: hpe: gxp: add HPE GXP soc support nick.hawkins
2022-06-01 14:24 ` Tom Rini
2022-05-26 18:55 ` [PATCH v1 4/9] dt-bindings: arm: hpe: add GXP Support nick.hawkins
2022-05-26 18:55 ` [PATCH v1 5/9] dt-bindings: timer: Add hpe gxp timer nick.hawkins
2022-05-26 18:55 ` [PATCH v1 6/9] ARM: dts: Add device tree files for hpe gxp soc nick.hawkins
2022-06-01 14:24 ` Tom Rini [this message]
2022-06-01 14:50 ` Hawkins, Nick
2022-06-01 15:28 ` Tom Rini
2022-06-02 20:56 ` Hawkins, Nick
2022-06-02 20:56 ` Hawkins, Nick
2022-06-03 13:23 ` Tom Rini
2022-06-03 15:35 ` Hawkins, Nick
2022-06-03 16:24 ` Tom Rini
2022-05-26 18:55 ` [PATCH v1 7/9] configs: gxp: add core support nick.hawkins
2022-06-01 14:24 ` Tom Rini
2022-06-02 14:46 ` Hawkins, Nick
2022-06-02 14:50 ` Tom Rini
2022-05-26 18:55 ` [PATCH v1 8/9] configs: gxp: add gxp_defconfig nick.hawkins
2022-05-26 18:55 ` [PATCH v1 9/9] MAINTAINERS: Introduce HPE GXP Architecture 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=20220601142414.GG25375@bill-the-cat \
--to=trini@konsulko.com \
--cc=nick.hawkins@hpe.com \
--cc=u-boot@lists.denx.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox