From: "Paweł Anikiel" <pan@semihalf.com> To: robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org, dinguyen@kernel.org Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, amstan@chromium.org, upstream@semihalf.com, "Paweł Anikiel" <pan@semihalf.com> Subject: [PATCH v4 0/5] Add Chameleon v3 devicetree Date: Fri, 3 Jun 2022 11:23:49 +0200 [thread overview] Message-ID: <20220603092354.141927-1-pan@semihalf.com> (raw) The Google Chameleon v3 is a board made for testing both video and audio interfaces of external devices. It acts as a base board for the Mercury+ AA1 module. socfpga_arria10_mercury_aa1.dtsi and socfpga_arria10_chameleonv3.dts have also been sent to u-boot: https://lists.denx.de/pipermail/u-boot/2022-May/485107.html https://lists.denx.de/pipermail/u-boot/2022-May/485111.html v4 changes: - remove enclustra,mercury-aa1 from Arria 10 boards in dt-bindings v3 changes: - make seperate group for Chameleon v3 in dt-bindings - add blank line after copyright header v2 changes: - split first patch into three - move sdmmc-ecc node to socfpga_arria10.dtsi (instead of removing it entirely) - use generic names for dts node names - keep the enclustra,mercury-aa1 compatible Paweł Anikiel (5): ARM: dts: socfpga: Change Mercury+ AA1 dts to dtsi ARM: dts: socfpga: Move sdmmc-ecc node to Arria 10 dts ARM: dts: socfpga: Add atsha204a node to Mercury+ AA1 dts ARM: dts: socfpga: Add Google Chameleon v3 devicetree dt-bindings: altera: Add Chameleon v3 board .../devicetree/bindings/arm/altera.yaml | 9 +- arch/arm/boot/dts/Makefile | 2 +- arch/arm/boot/dts/socfpga_arria10.dtsi | 10 +++ .../boot/dts/socfpga_arria10_chameleonv3.dts | 90 +++++++++++++++++++ ...1.dts => socfpga_arria10_mercury_aa1.dtsi} | 48 ++-------- 5 files changed, 117 insertions(+), 42 deletions(-) create mode 100644 arch/arm/boot/dts/socfpga_arria10_chameleonv3.dts rename arch/arm/boot/dts/{socfpga_arria10_mercury_aa1.dts => socfpga_arria10_mercury_aa1.dtsi} (70%) -- 2.36.1.255.ge46751e96f-goog
WARNING: multiple messages have this Message-ID (diff)
From: "Paweł Anikiel" <pan@semihalf.com> To: robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org, dinguyen@kernel.org Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, amstan@chromium.org, upstream@semihalf.com, "Paweł Anikiel" <pan@semihalf.com> Subject: [PATCH v4 0/5] Add Chameleon v3 devicetree Date: Fri, 3 Jun 2022 11:23:49 +0200 [thread overview] Message-ID: <20220603092354.141927-1-pan@semihalf.com> (raw) The Google Chameleon v3 is a board made for testing both video and audio interfaces of external devices. It acts as a base board for the Mercury+ AA1 module. socfpga_arria10_mercury_aa1.dtsi and socfpga_arria10_chameleonv3.dts have also been sent to u-boot: https://lists.denx.de/pipermail/u-boot/2022-May/485107.html https://lists.denx.de/pipermail/u-boot/2022-May/485111.html v4 changes: - remove enclustra,mercury-aa1 from Arria 10 boards in dt-bindings v3 changes: - make seperate group for Chameleon v3 in dt-bindings - add blank line after copyright header v2 changes: - split first patch into three - move sdmmc-ecc node to socfpga_arria10.dtsi (instead of removing it entirely) - use generic names for dts node names - keep the enclustra,mercury-aa1 compatible Paweł Anikiel (5): ARM: dts: socfpga: Change Mercury+ AA1 dts to dtsi ARM: dts: socfpga: Move sdmmc-ecc node to Arria 10 dts ARM: dts: socfpga: Add atsha204a node to Mercury+ AA1 dts ARM: dts: socfpga: Add Google Chameleon v3 devicetree dt-bindings: altera: Add Chameleon v3 board .../devicetree/bindings/arm/altera.yaml | 9 +- arch/arm/boot/dts/Makefile | 2 +- arch/arm/boot/dts/socfpga_arria10.dtsi | 10 +++ .../boot/dts/socfpga_arria10_chameleonv3.dts | 90 +++++++++++++++++++ ...1.dts => socfpga_arria10_mercury_aa1.dtsi} | 48 ++-------- 5 files changed, 117 insertions(+), 42 deletions(-) create mode 100644 arch/arm/boot/dts/socfpga_arria10_chameleonv3.dts rename arch/arm/boot/dts/{socfpga_arria10_mercury_aa1.dts => socfpga_arria10_mercury_aa1.dtsi} (70%) -- 2.36.1.255.ge46751e96f-goog _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2022-06-03 9:24 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-03 9:23 Paweł Anikiel [this message] 2022-06-03 9:23 ` [PATCH v4 0/5] Add Chameleon v3 devicetree Paweł Anikiel 2022-06-03 9:23 ` [PATCH v4 1/5] ARM: dts: socfpga: Change Mercury+ AA1 dts to dtsi Paweł Anikiel 2022-06-03 9:23 ` Paweł Anikiel 2022-06-03 9:23 ` [PATCH v4 2/5] ARM: dts: socfpga: Move sdmmc-ecc node to Arria 10 dts Paweł Anikiel 2022-06-03 9:23 ` Paweł Anikiel 2022-06-03 9:23 ` [PATCH v4 3/5] ARM: dts: socfpga: Add atsha204a node to Mercury+ AA1 dts Paweł Anikiel 2022-06-03 9:23 ` Paweł Anikiel 2022-06-03 9:23 ` [PATCH v4 4/5] ARM: dts: socfpga: Add Google Chameleon v3 devicetree Paweł Anikiel 2022-06-03 9:23 ` Paweł Anikiel 2022-06-03 9:23 ` [PATCH v4 5/5] dt-bindings: altera: Add Chameleon v3 board Paweł Anikiel 2022-06-03 9:23 ` Paweł Anikiel 2022-06-03 10:18 ` Krzysztof Kozlowski 2022-06-03 10:18 ` Krzysztof Kozlowski 2022-06-14 15:47 ` [PATCH v4 0/5] Add Chameleon v3 devicetree Dinh Nguyen 2022-06-14 15:47 ` Dinh Nguyen
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=20220603092354.141927-1-pan@semihalf.com \ --to=pan@semihalf.com \ --cc=amstan@chromium.org \ --cc=devicetree@vger.kernel.org \ --cc=dinguyen@kernel.org \ --cc=krzysztof.kozlowski+dt@linaro.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=robh+dt@kernel.org \ --cc=upstream@semihalf.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: linkBe 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.