From: Dinh Nguyen <dinguyen@kernel.org>
To: "Paweł Anikiel" <pan@semihalf.com>,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, amstan@chromium.org,
upstream@semihalf.com
Subject: Re: [PATCH v4 0/5] Add Chameleon v3 devicetree
Date: Tue, 14 Jun 2022 10:47:05 -0500 [thread overview]
Message-ID: <dbbcb0a4-e777-db84-b3cd-0a3659dd5092@kernel.org> (raw)
In-Reply-To: <20220603092354.141927-1-pan@semihalf.com>
On 6/3/22 04:23, Paweł Anikiel wrote:
> 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%)
>
Whole series applied!
Thanks,
Dinh
prev parent reply other threads:[~2022-06-14 15:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
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 ` [PATCH v4 2/5] ARM: dts: socfpga: Move sdmmc-ecc node to Arria 10 dts 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 ` [PATCH v4 4/5] ARM: dts: socfpga: Add Google Chameleon v3 devicetree Paweł Anikiel
2022-06-03 9:23 ` [PATCH v4 5/5] dt-bindings: altera: Add Chameleon v3 board Paweł Anikiel
2022-06-03 10:18 ` Krzysztof Kozlowski
2022-06-14 15:47 ` 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=dbbcb0a4-e777-db84-b3cd-0a3659dd5092@kernel.org \
--to=dinguyen@kernel.org \
--cc=amstan@chromium.org \
--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=pan@semihalf.com \
--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: 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;
as well as URLs for NNTP newsgroup(s).