From: Heiko Stuebner <heiko@sntech.de>
To: Rob Herring <robh+dt@kernel.org>,
Jagan Teki <jagan@amarulasolutions.com>
Cc: Suniel Mahesh <sunil@amarulasolutions.com>,
Michael Trimarchi <michael@amarulasolutions.com>,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-amarula <linux-amarula@amarulasolutions.com>,
Jagan Teki <jagan@amarulasolutions.com>
Subject: Re: [PATCH v4 0/7] arm64: dts: rockchip: Add Engicam PX30.Core
Date: Mon, 09 Nov 2020 00:15:23 +0100 [thread overview]
Message-ID: <2320954.tcIoyGMtcG@phil> (raw)
In-Reply-To: <20200929083217.25406-1-jagan@amarulasolutions.com>
Hi,
Am Dienstag, 29. September 2020, 10:32:10 CET schrieb Jagan Teki:
> PX30.Core is an EDIMM SOM based on Rockchip PX30 from Engicam.
>
> PX30.Core needs to mount on top of Engicam baseboards for creating
> complete platform boards.
>
> Possible baseboards are,
> - EDIMM2.2 Starter Kit
> - C.TOUCH 2.0 Carrier Board
>
> Changes for v4:
> - collect Rob A-b
> Changes for v3:
> - resolved Johan comments about sorting node properties
> - add copyright to Amarula Solutions
> - update px30 dtsi author
> Changes for v2:
> - include C.TOUCH 2.0 carrier board
> - skip 10" OF LCD as it requires separate dts with panel support.
>
> Note: These baseboards can be used for i.MX8 SOM's as well. So having
> baseboard on respective SoC seems to be easy rather than making it
> common across all.
>
> Any inputs?
> Jagan.
>
> Jagan Teki (6):
> dt-bindings: arm: rockchip: Add Engicam PX30.Core EDIMM2.2 Starter Kit
> arm64: dts: rockchip: px30: Add Engicam EDIMM2.2 Starter Kit
> arm64: dts: rockchip: Add Engicam PX30.Core EDIMM2.2 Starter Kit
> dt-bindings: arm: rockchip: Add Engicam PX30.Core C.TOUCH 2.0
> arm64: dts: rockchip: px30: Add Engicam C.TOUCH 2.0
> arm64: dts: rockchip: Add Engicam PX30.Core C.TOUCH 2.0
>
> Michael Trimarchi (1):
> arm64: dts: rockchip: Add Engicam PX30.Core SOM
I've applied the patches for 5.11 with some changes:
(1) engicam,px30-px30-core became engicam,px30-core
(2) px30-px30-core.dtsi became px30-engicam-px30-core.dtsi
That double px30 is unnecessary and confusing in compatibles
and the px30-core thingy needed something less generic, as that is
not px30-specific but specific to the engicam boards.
Heiko
next prev parent reply other threads:[~2020-11-08 23:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-29 8:32 [PATCH v4 0/7] arm64: dts: rockchip: Add Engicam PX30.Core Jagan Teki
2020-09-29 8:32 ` [PATCH v4 1/7] dt-bindings: arm: rockchip: Add Engicam PX30.Core EDIMM2.2 Starter Kit Jagan Teki
2020-09-29 8:32 ` [PATCH v4 2/7] arm64: dts: rockchip: px30: Add Engicam " Jagan Teki
2020-09-29 8:32 ` [PATCH v4 3/7] arm64: dts: rockchip: Add Engicam PX30.Core SOM Jagan Teki
2020-09-29 8:32 ` [PATCH v4 4/7] arm64: dts: rockchip: Add Engicam PX30.Core EDIMM2.2 Starter Kit Jagan Teki
2020-09-29 8:32 ` [PATCH v4 5/7] dt-bindings: arm: rockchip: Add Engicam PX30.Core C.TOUCH 2.0 Jagan Teki
2020-09-29 8:32 ` [PATCH v4 6/7] arm64: dts: rockchip: px30: Add Engicam " Jagan Teki
2020-09-29 8:32 ` [PATCH v4 7/7] arm64: dts: rockchip: Add Engicam PX30.Core " Jagan Teki
2020-10-21 18:57 ` [PATCH v4 0/7] arm64: dts: rockchip: Add Engicam PX30.Core Jagan Teki
2020-11-04 19:54 ` Jagan Teki
2020-11-04 21:55 ` Heiko Stübner
2020-11-08 23:15 ` Heiko Stuebner [this message]
2020-11-09 18:18 ` Jagan Teki
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=2320954.tcIoyGMtcG@phil \
--to=heiko@sntech.de \
--cc=devicetree@vger.kernel.org \
--cc=jagan@amarulasolutions.com \
--cc=linux-amarula@amarulasolutions.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=michael@amarulasolutions.com \
--cc=robh+dt@kernel.org \
--cc=sunil@amarulasolutions.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).