From: Dinh Nguyen <dinguyen@kernel.org>
To: matthew.gerlach@linux.intel.com, robh+dt@kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
krzysztof.kozlowski+dt@linaro.org
Subject: Re: [PATCH v4 0/3] Add device tree for Intel n6000
Date: Thu, 12 May 2022 09:41:56 -0500 [thread overview]
Message-ID: <98d7e84c-086a-794f-019d-849bcc2570c9@kernel.org> (raw)
In-Reply-To: <20220508142624.491045-1-matthew.gerlach@linux.intel.com>
On 5/8/22 09:26, matthew.gerlach@linux.intel.com wrote:
> From: Matthew Gerlach <matthew.gerlach@linux.intel.com>
>
> This patch set adds a device tree for the Hard Processor System (HPS)
> on an Agilex based Intel n6000 board.
>
> Patch 1 defines the device tree binding for the HPS Copy Engine IP
> used to copy a bootable image from host memory to HPS DDR.
>
> Patch 2 defines the binding for the Intel n6000 board itself.
>
> Patch 3 adds the device tree for the n6000 board.
>
> Changelog v3 -> v4:
> - move binding yaml from soc to soc/intel
>
> Changelog v2 -> v3:
> - remove unused label
> - move from misc to soc
> - remove 0x from #address-cells/#size-cells values
> - change hps_cp_eng@0 to dma-controller@0
> - remote inaccurate 'items:' tag
> - added Acked-by
> - add unit number to memory node
> - remove spi node with unaccepted compatible value
>
> Changelog v1 -> v2:
> - add dt binding for copy enging
> - add dt binding for n6000 board
> - fix copy engine node name
> - fix compatible field for copy engine
> - remove redundant status field
> - add compatibility field for the board
> - fix SPDX
> - fix how osc1 clock frequency is set
>
> Matthew Gerlach (3):
> dt-bindings: soc: add bindings for Intel HPS Copy Engine
> dt-bindings: intel: add binding for Intel n6000
> arm64: dts: intel: add device tree for n6000
>
> .../bindings/arm/intel,socfpga.yaml | 1 +
> .../soc/intel/intel,hps-copy-engine.yaml | 51 ++++++++++++++
> arch/arm64/boot/dts/intel/Makefile | 3 +-
> .../boot/dts/intel/socfpga_agilex_n6000.dts | 66 +++++++++++++++++++
> 4 files changed, 120 insertions(+), 1 deletion(-)
> create mode 100644 Documentation/devicetree/bindings/soc/intel/intel,hps-copy-engine.yaml
> create mode 100644 arch/arm64/boot/dts/intel/socfpga_agilex_n6000.dts
>
Applied!
Thanks,
Dinh
next prev parent reply other threads:[~2022-05-12 14:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-08 14:26 matthew.gerlach
2022-05-08 14:26 ` [PATCH v4 1/3] dt-bindings: soc: add bindings for Intel HPS Copy Engine matthew.gerlach
2022-05-09 7:22 ` Krzysztof Kozlowski
2022-05-10 14:16 ` matthew.gerlach
2022-05-10 19:15 ` Rob Herring
2022-05-10 22:23 ` matthew.gerlach
2022-05-18 15:00 ` Rob Herring
2022-05-10 19:17 ` Rob Herring
2022-05-10 22:26 ` matthew.gerlach
2022-05-08 14:26 ` [PATCH v4 2/3] dt-bindings: intel: add binding for Intel n6000 matthew.gerlach
2022-05-08 14:26 ` [PATCH v4 3/3] arm64: dts: intel: add device tree for n6000 matthew.gerlach
2022-05-09 7:23 ` Krzysztof Kozlowski
2022-05-10 14:17 ` matthew.gerlach
2022-05-10 19:22 ` Rob Herring
2022-05-10 22:28 ` matthew.gerlach
2022-05-12 14:41 ` Dinh Nguyen [this message]
2022-05-12 15:18 ` [PATCH v4 0/3] Add device tree for Intel n6000 matthew.gerlach
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=98d7e84c-086a-794f-019d-849bcc2570c9@kernel.org \
--to=dinguyen@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.gerlach@linux.intel.com \
--cc=robh+dt@kernel.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
all inboxes | Powered by JetHome®