From: Suniel Mahesh <sunil@amarulasolutions.com>
To: kever.yang@rock-chips.com, philipp.tomsich@theobroma-systems.com,
sjg@chromium.org
Cc: linux-rockchip@lists.infradead.org, u-boot@lists.denx.de,
jagan@amarulasolutions.com, sunil@amarulasolutions.com,
Michael Trimarchi <michael@amarulasolutions.com>,
linux-amarula@amarulasolutions.com
Subject: [PATCH v2 5/7] arm64: dts: rockchip: px30: Add Engicam C.TOUCH 2.0
Date: Mon, 14 Sep 2020 21:06:32 +0530 [thread overview]
Message-ID: <20200914153634.18121-6-sunil@amarulasolutions.com> (raw)
In-Reply-To: <20200914153634.18121-1-sunil@amarulasolutions.com>
From: Jagan Teki <jagan@amarulasolutions.com>
Engicam C.TOUCH 2.0 is an EDIMM compliant general purpose
carrier board with capacitive touch interface.
Genaral features:
- TFT 10.1" industrial, 1280x800 LVDS display
- Ethernet 10/100
- Wifi/BT
- USB Type A/OTG
- Audio Out
- CAN
- LVDS panel connector
SOM's like PX30.Core needs to mount on top of this Carrier board
for creating complete PX30.Core C.TOUCH 2.0 board.
Add support for it.
Signed-off-by: Jagan Teki <jagan@amarulasolutions.com>
Signed-off-by: Michael Trimarchi <michael@amarulasolutions.com>
---
Changes for v2:
- Add more content in patch description to describe the board capabilities
- Add Michael Trimarchi as one of the contributors
- Add additional copyright
arch/arm/dts/px30-engicam-ctouch2.dtsi | 8 ++++++++
1 file changed, 8 insertions(+)
create mode 100644 arch/arm/dts/px30-engicam-ctouch2.dtsi
diff --git a/arch/arm/dts/px30-engicam-ctouch2.dtsi b/arch/arm/dts/px30-engicam-ctouch2.dtsi
new file mode 100644
index 0000000000..58425b1e55
--- /dev/null
+++ b/arch/arm/dts/px30-engicam-ctouch2.dtsi
@@ -0,0 +1,8 @@
+// SPDX-License-Identifier: (GPL-2.0+ OR MIT)
+/*
+ * Copyright (c) 2020 Engicam srl
+ * Copyright (c) 2020 Amarula Solutions
+ * Copyright (c) 2020 Amarula Solutions(India)
+ */
+
+#include "px30-engicam-common.dtsi"
--
2.17.1
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2020-09-14 15:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-14 15:36 [PATCH v2 0/7] rockchip: Add Engicam PX30.Core support Suniel Mahesh
2020-09-14 15:36 ` [PATCH v2 1/7] arm64: dts: rockchip: px30: Add Engicam EDIMM2.2 Starter Kit Suniel Mahesh
2020-09-14 15:36 ` [PATCH v2 2/7] arm64: dts: rockchip: Add Engicam PX30.Core SOM Suniel Mahesh
2020-09-14 15:36 ` [PATCH v2 3/7] rockchip: px30: Add EVB_PX30 Kconfig help Suniel Mahesh
2020-09-14 15:36 ` [PATCH v2 4/7] rockchip: Add Engicam PX30.Core EDIMM2.2 Starter Kit Suniel Mahesh
2020-09-14 15:36 ` Suniel Mahesh [this message]
2020-09-14 15:36 ` [PATCH v2 6/7] rockchip: Add Engicam PX30.Core C.TOUCH 2.0 Suniel Mahesh
2020-09-14 15:36 ` [PATCH v2 7/7] doc: rockchip: Document Rockchip miniloader flashing Suniel Mahesh
2020-09-28 2:39 ` [PATCH v2 0/7] rockchip: Add Engicam PX30.Core support Kever Yang
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=20200914153634.18121-6-sunil@amarulasolutions.com \
--to=sunil@amarulasolutions.com \
--cc=jagan@amarulasolutions.com \
--cc=kever.yang@rock-chips.com \
--cc=linux-amarula@amarulasolutions.com \
--cc=linux-rockchip@lists.infradead.org \
--cc=michael@amarulasolutions.com \
--cc=philipp.tomsich@theobroma-systems.com \
--cc=sjg@chromium.org \
--cc=u-boot@lists.denx.de \
/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).