linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: djw@t-chip.com.cn
To: linux-rockchip@lists.infradead.org
Cc: "Wayne Chou" <zxf@t-chip.com.cn>,
	"Kongxin Deng" <dkx@t-chip.com.cn>,
	"Levin Du" <djw@t-chip.com.cn>,
	"Heiko Stuebner" <heiko@sntech.de>,
	"Chen-Yu Tsai" <wens@csie.org>,
	"David Bauer" <mail@david-bauer.net>,
	"Jagan Teki" <jagan@amarulasolutions.com>,
	"Jensen Huang" <jensenhuang@friendlyarm.com>,
	"Johan Jonker" <jbx6244@gmail.com>,
	"Krzysztof Kozlowski" <krzk@kernel.org>,
	"Liang Chen" <cl@rock-chips.com>,
	"Marty Jones" <mj8263788@gmail.com>,
	"Rob Herring" <robh+dt@kernel.org>,
	"Uwe Kleine-König" <uwe@kleine-koenig.org>,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: [PATCH v0 0/2] Add support for Firefly ROC-RK3399-PC-PLUS
Date: Mon, 28 Jun 2021 11:54:00 +0800	[thread overview]
Message-ID: <20210628035402.16812-1-djw@t-chip.com.cn> (raw)

From: Levin Du <djw@t-chip.com.cn>


Hi all, this is an attemp to add Firefly ROC-RK3399-PC-PLUS to the mainline
kernel.

ROC-RK3399-PC-PLUS is the board inside the portable Firefly Station P1 Geek
PC. As a redesign after the ROC-RK3399-PC, it uses DC-12V as power input
and spares a USB 3 host port. It is also equipped with a USB WiFi chip and
audio codec without the mezzanine board.

Many thanks to the Linux people!


Levin Du (2):
  dt-bindings: add doc for Firefly ROC-RK3399-PC-PLUS
  arm64: dts: rockchip: add support for Firefly ROC-RK3399-PC-PLUS

 .../devicetree/bindings/arm/rockchip.yaml     |   6 +
 arch/arm64/boot/dts/rockchip/Makefile         |   1 +
 .../boot/dts/rockchip/rk3399-roc-pc-plus.dts  | 223 ++++++++++++++++++
 3 files changed, 230 insertions(+)
 create mode 100644 arch/arm64/boot/dts/rockchip/rk3399-roc-pc-plus.dts

--
2.23.0.37.g745f6812895b




_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

             reply	other threads:[~2021-06-28  3:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-28  3:54 djw [this message]
2021-06-28  3:54 ` [PATCH v0 1/2] dt-bindings: add doc for Firefly ROC-RK3399-PC-PLUS djw
2021-07-14 20:52   ` Rob Herring
2021-06-28  3:54 ` [PATCH v0 2/2] arm64: dts: rockchip: add support " djw
2021-06-29  9:15   ` Levin
2021-06-29  9:30     ` Heiko Stübner
2021-06-29  9:32       ` Heiko Stübner
2021-06-30  6:49         ` Levin
2021-07-15 22:42 ` [PATCH v0 0/2] Add " Heiko Stuebner

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=20210628035402.16812-1-djw@t-chip.com.cn \
    --to=djw@t-chip.com.cn \
    --cc=cl@rock-chips.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dkx@t-chip.com.cn \
    --cc=heiko@sntech.de \
    --cc=jagan@amarulasolutions.com \
    --cc=jbx6244@gmail.com \
    --cc=jensenhuang@friendlyarm.com \
    --cc=krzk@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=mail@david-bauer.net \
    --cc=mj8263788@gmail.com \
    --cc=robh+dt@kernel.org \
    --cc=uwe@kleine-koenig.org \
    --cc=wens@csie.org \
    --cc=zxf@t-chip.com.cn \
    /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).