From: Yakir Yang <ykk@rock-chips.com>
To: Heiko Stuebner <heiko@sntech.de>,
Kumar Gala <galak@codeaurora.org>,
Rob Herring <robh+dt@kernel.org>, Olof Johansson <olof@lixom.net>,
Jianqun Xu <jay.xu@rock-chips.com>,
Pawel Moll <pawel.moll@arm.com>
Cc: mark.yao@rock-chips.com, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
Yakir Yang <ykk@rock-chips.com>
Subject: [PATCH 0/3] Add the eDP/VOP device node for rk3399
Date: Mon, 23 May 2016 21:10:56 +0800 [thread overview]
Message-ID: <1464009056-32158-1-git-send-email-ykk@rock-chips.com> (raw)
This thread is rely on Mark's VOP thread[1] and Yakir's eDP thread[2].
[1]: https://lkml.org/lkml/2016/4/20/36
[2]: https://patchwork.freedesktop.org/patch/83406/
Mark Yao (1):
arm64: dts: rockchip: add VOP and VOP iommu node for rk3399
Yakir Yang (2):
arm64: dts: rockchip: add eDP device node for rk3399
arm64: dts: rockchip: add backlight support for rk3399 evb board
arch/arm64/boot/dts/rockchip/rk3399-evb.dts | 40 ++++++++++
arch/arm64/boot/dts/rockchip/rk3399.dtsi | 110 ++++++++++++++++++++++++++++
2 files changed, 150 insertions(+)
--
1.9.1
next reply other threads:[~2016-05-23 13:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-23 13:10 Yakir Yang [this message]
2016-05-23 13:11 ` [PATCH 1/3] arm64: dts: rockchip: add VOP and VOP iommu node for rk3399 Yakir Yang
[not found] ` <1464009070-32215-1-git-send-email-ykk-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2016-05-23 13:18 ` Heiko Stuebner
2016-05-23 13:26 ` Yakir Yang
2016-05-23 13:11 ` [PATCH 2/3] arm64: dts: rockchip: add eDP device " Yakir Yang
2016-05-23 13:11 ` [PATCH 3/3] arm64: dts: rockchip: add backlight support for rk3399 evb board Yakir Yang
-- strict thread matches above, loose matches on Subject: below --
2016-05-23 13:33 [PATCH 0/3] Add the eDP/VOP device node for rk3399 Yakir 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=1464009056-32158-1-git-send-email-ykk@rock-chips.com \
--to=ykk@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=heiko@sntech.de \
--cc=jay.xu@rock-chips.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mark.yao@rock-chips.com \
--cc=olof@lixom.net \
--cc=pawel.moll@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).