devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matheus Castello <matheus@castello.eng.br>
To: manivannan.sadhasivam@linaro.org, afaerber@suse.de,
	mark.rutland@arm.com, robh+dt@kernel.org
Cc: edgar.righi@lsitec.org.br, igor.lima@lsitec.org.br,
	helen.koike@collabora.com, linux-arm-kernel@lists.infradead.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-actions@lists.infradead.org,
	Matheus Castello <matheus@castello.eng.br>
Subject: [PATCH v7 0/4] Add Caninos Loucos Labrador CoM and Base Board Device Tree
Date: Mon, 21 Sep 2020 23:42:58 -0300	[thread overview]
Message-ID: <20200922024302.205062-1-matheus@castello.eng.br> (raw)

I'm adding to the series the new Labrador v3, since it uses the same vendor
prefix. Thanks Andreas, Mani and Rob for your time reviewing it.

Changes since v6:
- Add new caninos,labrador-v3 CoM and caninos,labrador-base-m2 base board
- Improve Model description

Changes since v5:
(Suggested by Andreas Färber)
- Put caninos,labrador-v2 as const one level down

Matheus Castello (4):
  dt-bindings: Add vendor prefix for Caninos Loucos
  dt-bindings: arm: actions: Document Caninos Loucos Labrador
  ARM: dts: Add Caninos Loucos Labrador v2
  arm64: dts: Add Caninos Loucos Labrador v3

 .../devicetree/bindings/arm/actions.yaml      |  10 ++
 .../devicetree/bindings/vendor-prefixes.yaml  |   2 +
 arch/arm/boot/dts/Makefile                    |   1 +
 .../arm/boot/dts/owl-s500-labrador-base-m.dts |  35 +++++
 arch/arm/boot/dts/owl-s500-labrador-v2.dtsi   |  22 ++++
 arch/arm64/boot/dts/actions/Makefile          |   2 +
 .../dts/actions/s700-labrador-base-m2.dts     |  34 +++++
 .../boot/dts/actions/s700-labrador-v3.dtsi    | 122 ++++++++++++++++++
 8 files changed, 228 insertions(+)
 create mode 100644 arch/arm/boot/dts/owl-s500-labrador-base-m.dts
 create mode 100644 arch/arm/boot/dts/owl-s500-labrador-v2.dtsi
 create mode 100644 arch/arm64/boot/dts/actions/s700-labrador-base-m2.dts
 create mode 100644 arch/arm64/boot/dts/actions/s700-labrador-v3.dtsi

--
2.28.0


             reply	other threads:[~2020-09-22  3:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-22  2:42 Matheus Castello [this message]
2020-09-22  2:42 ` [PATCH v7 1/4] dt-bindings: Add vendor prefix for Caninos Loucos Matheus Castello
2020-09-22  6:25   ` Manivannan Sadhasivam
2020-09-22  8:14   ` Manivannan Sadhasivam
2020-09-22  2:43 ` [PATCH v7 2/4] dt-bindings: arm: actions: Document Caninos Loucos Labrador Matheus Castello
2020-09-22  6:27   ` Manivannan Sadhasivam
2020-09-22  2:43 ` [PATCH v7 3/4] ARM: dts: Add Caninos Loucos Labrador v2 Matheus Castello
2020-09-22  6:27   ` Manivannan Sadhasivam
2020-09-22  2:43 ` [PATCH v7 4/4] arm64: dts: Add Caninos Loucos Labrador v3 Matheus Castello
2020-09-22  6:14   ` Manivannan Sadhasivam
2020-09-22  8:32     ` Arnd Bergmann
2020-09-22 10:26       ` Catalin Marinas
2020-10-15 23:57         ` Matheus Castello

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=20200922024302.205062-1-matheus@castello.eng.br \
    --to=matheus@castello.eng.br \
    --cc=afaerber@suse.de \
    --cc=devicetree@vger.kernel.org \
    --cc=edgar.righi@lsitec.org.br \
    --cc=helen.koike@collabora.com \
    --cc=igor.lima@lsitec.org.br \
    --cc=linux-actions@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=mark.rutland@arm.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;
as well as URLs for NNTP newsgroup(s).