From: Jagan Teki <jagan@amarulasolutions.com>
To: Kever Yang <kever.yang@rock-chips.com>
Cc: u-boot@lists.denx.de, linux-amarula@amarulasolutions.com,
Jagan Teki <jagan@amarulasolutions.com>
Subject: [PATCH 0/4] arm64: dts: rockchip: px30: Linux-5.14-rc3 Sync
Date: Wed, 4 Aug 2021 14:35:47 +0530 [thread overview]
Message-ID: <20210804090551.90819-1-jagan@amarulasolutions.com> (raw)
Series sync Linux-5.14-rc3 devicetree files for px30 SoC.
Any inputs?
Jagan.
Jagan Teki (4):
arm64: dts: rockchip: px30: Sync Linux PX30.Core files
arm64: dts: rockchip: px30: Move dmc into -u-boot.dtsi
arm64: dts: rockchip: px30: Sync Linux-5.14-rc3 dts(i)
engicam: px30: Add Engicam PX30.Core C.TOUCH 2.0 10.1" OF
arch/arm/dts/Makefile | 5 +-
arch/arm/dts/px30-engicam-common.dtsi | 90 +++++++
arch/arm/dts/px30-engicam-ctouch2.dtsi | 22 ++
arch/arm/dts/px30-engicam-edimm2.2.dtsi | 59 +++++
.../px30-engicam-px30-core-ctouch2-of10.dts | 77 ++++++
...dts => px30-engicam-px30-core-ctouch2.dts} | 4 +-
.../dts/px30-engicam-px30-core-edimm2.2.dts | 43 ++++
arch/arm/dts/px30-engicam-px30-core.dtsi | 241 ++++++++++++++++++
arch/arm/dts/px30-evb.dts | 91 +++++--
arch/arm/dts/px30-px30-core-edimm2.2.dts | 21 --
arch/arm/dts/px30-u-boot.dtsi | 10 +-
arch/arm/dts/px30.dtsi | 183 ++++++++-----
arch/arm/dts/rk3326-odroid-go2-u-boot.dtsi | 10 +-
arch/arm/mach-rockchip/px30/Kconfig | 8 +
board/engicam/px30_core/MAINTAINERS | 6 +
configs/px30-core-ctouch2-of10-px30_defconfig | 107 ++++++++
configs/px30-core-ctouch2-px30_defconfig | 4 +-
configs/px30-core-edimm2.2-px30_defconfig | 4 +-
18 files changed, 861 insertions(+), 124 deletions(-)
create mode 100644 arch/arm/dts/px30-engicam-px30-core-ctouch2-of10.dts
rename arch/arm/dts/{px30-px30-core-ctouch2.dts => px30-engicam-px30-core-ctouch2.dts} (80%)
create mode 100644 arch/arm/dts/px30-engicam-px30-core-edimm2.2.dts
create mode 100644 arch/arm/dts/px30-engicam-px30-core.dtsi
delete mode 100644 arch/arm/dts/px30-px30-core-edimm2.2.dts
create mode 100644 configs/px30-core-ctouch2-of10-px30_defconfig
--
2.25.1
next reply other threads:[~2021-08-04 9:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-04 9:05 Jagan Teki [this message]
2021-08-04 9:05 ` [PATCH 1/4] arm64: dts: rockchip: px30: Sync Linux PX30.Core files Jagan Teki
2021-08-04 9:05 ` [PATCH 2/4] arm64: dts: rockchip: px30: Move dmc into -u-boot.dtsi Jagan Teki
2021-08-04 9:05 ` [PATCH 3/4] arm64: dts: rockchip: px30: Sync Linux-5.14-rc3 dts(i) Jagan Teki
2021-08-04 9:05 ` [PATCH 4/4] engicam: px30: Add Engicam PX30.Core C.TOUCH 2.0 10.1" OF Jagan Teki
2021-10-08 21:10 ` [PATCH 0/4] arm64: dts: rockchip: px30: Linux-5.14-rc3 Sync Jagan Teki
2021-10-09 14:52 ` 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=20210804090551.90819-1-jagan@amarulasolutions.com \
--to=jagan@amarulasolutions.com \
--cc=kever.yang@rock-chips.com \
--cc=linux-amarula@amarulasolutions.com \
--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