From: Dinh Nguyen <dinguyen@kernel.org>
To: Petko Manolov <petko.manolov@konsulko.com>, linux-kernel@vger.kernel.org
Cc: devicetree@vger.kernel.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, arnemaximilian.richter@draeger.com,
martynas.grybauskas@draeger.com
Subject: Re: [PATCH v7 3/3] arm: dts: altera: add Draeger M48 CPU Module
Date: Mon, 28 Sep 2026 09:18:03 -0500 [thread overview]
Message-ID: <ff085338-6310-42ac-8023-bdf6d48ad103@kernel.org> (raw)
In-Reply-To: <20260921090735.3174292-4-petko.manolov@konsulko.com>
On 9/21/26 04:07, Petko Manolov wrote:
> M48 is a heterogeneous board made by Draeger that is based on two
> independent cpus, that are monitoring each other. One of them is
> imx6, the other is Altera SoCFPGA Cyclone 5. The latter is booting
> independently off qspi.
>
> This one adds the DT for the Altera SoCFPGA part of M48.
>
> Signed-off-by: Petko Manolov <petko.manolov@konsulko.com>
> ---
> arch/arm/boot/dts/intel/socfpga/Makefile | 1 +
> .../socfpga/socfpga_cyclone5_draeger_m48.dts | 123 ++++++++++++++++++
> 2 files changed, 124 insertions(+)
> create mode 100644 arch/arm/boot/dts/intel/socfpga/socfpga_cyclone5_draeger_m48.dts
>
> diff --git a/arch/arm/boot/dts/intel/socfpga/Makefile b/arch/arm/boot/dts/intel/socfpga/Makefile
> index 8df0976da01c..cdcea11abdfa 100644
> --- a/arch/arm/boot/dts/intel/socfpga/Makefile
> +++ b/arch/arm/boot/dts/intel/socfpga/Makefile
> @@ -11,6 +11,7 @@ dtb-$(CONFIG_ARCH_INTEL_SOCFPGA) += \
> socfpga_arria10_mercury_aa1_st1_emmc.dtb \
> socfpga_arria10_mercury_aa1_st1_qspi.dtb \
> socfpga_arria10_mercury_aa1_st1_sdmmc.dtb \
> + socfpga_cyclone5_draeger_m48.dtb \
> socfpga_cyclone5_mercury_sa1_pe1_emmc.dtb \
> socfpga_cyclone5_mercury_sa1_pe1_qspi.dtb \
> socfpga_cyclone5_mercury_sa1_pe1_sdmmc.dtb \
> diff --git a/arch/arm/boot/dts/intel/socfpga/socfpga_cyclone5_draeger_m48.dts b/arch/arm/boot/dts/intel/socfpga/socfpga_cyclone5_draeger_m48.dts
> new file mode 100644
> index 000000000000..dae809c02adb
> --- /dev/null
> +++ b/arch/arm/boot/dts/intel/socfpga/socfpga_cyclone5_draeger_m48.dts
> @@ -0,0 +1,123 @@
> +// SPDX-License-Identifier: GPL-2.0+
> +/*
> + * (C) Copyright 2020 Draeger and Licensors, info@draeger.com
> + */
> +#include "socfpga_cyclone5.dtsi"
> +
> +/ {
> + model = "Draeger M48 Cyclone V SoC";
> + compatible = "draeger,m48", "altr,socfpga-cyclone5", "altr,socfpga";
> +
> + chosen {
> + stdout-path = "serial0:115200n8";
> + };
> +
> + memory@0 {
> + name = "memory";
> + device_type = "memory";
> + reg = <0x0 0x40000000>;
> + };
> +
> + aliases {
> + /* this allow the ethaddr uboot environmnet variable contents
> + * to be added to the gmac0 device tree blob.
> + */
> + ethernet0 = &gmac0;
> + };
> +
> + soc {
> + gpio3: gpio@ff202000 {
> + #address-cells = <1>;
> + #size-cells = <0>;
> + compatible = "snps,dw-apb-gpio";
> + reg = <0xff202000 0x20>;
> +
> + portd: gpio-controller@0 {
> + compatible = "snps,dw-apb-gpio-port";
> + gpio-controller;
> + #gpio-cells = <2>;
> + snps,nr-gpios = <2>;
> + reg = <0>;
> + };
> + };
> +
> + gpio4: gpio@ff202020 {
Any chance you can point me the where you got this information for gpio3
and gpio4?
According to all my documentations, the Cyclone5 SoCFPGA has 3 GPIO
ports, and those are already mapped in the DTSI. The address space that
you have specified here is for FPGA bridge. Which leads me to believe
that this GPIO is in the FPGA.
Thanks,
Dinh
prev parent reply other threads:[~2026-09-28 14:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 9:07 [PATCH v7 0/3] arm: dts: altera: add Draeger M48 CPU board Petko Manolov
2026-09-21 9:07 ` [PATCH v7 1/3] dt-bindings: vendor-prefixes: add Draeger AG Petko Manolov
2026-09-21 9:07 ` [PATCH v7 2/3] dt-bindings: arm: altera: add Draeger M48 dual-cpu board Petko Manolov
2026-09-28 5:53 ` Krzysztof Kozlowski
2026-09-21 9:07 ` [PATCH v7 3/3] arm: dts: altera: add Draeger M48 CPU Module Petko Manolov
2026-09-28 14:18 ` Dinh Nguyen [this message]
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=ff085338-6310-42ac-8023-bdf6d48ad103@kernel.org \
--to=dinguyen@kernel.org \
--cc=arnemaximilian.richter@draeger.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martynas.grybauskas@draeger.com \
--cc=petko.manolov@konsulko.com \
--cc=robh@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®