From: Heiko Stuebner <heiko@sntech.de>
To: hjc@rock-chips.com
Cc: linux-rockchip@lists.infradead.org, seanpaul@chromium.org,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: [PATCH v8 0/3] Add support rockchip RGB output interface
Date: Thu, 30 Aug 2018 23:12:04 +0200 [thread overview]
Message-ID: <20180830211207.10480-1-heiko@sntech.de> (raw)
This patches add support rockchip RGB output, Some Rockchip CRTCs, like
rv1108 and px30 can directly output parallel and serial RGB data to panel
or to conversion chip.
So add a feature-bit for vops to mark the ability for these direct outputs
and add an internal encoder in that case, that can attach to bridge chips
or panels.
Hi Sandy,
while reviewing my own code in patch1, I found that it was missing
correct put calls for node and pdev and also made it behave better
if no device is present.
While we don't need that right now, it makes it possible to
distinguish between subdriver, external bridge or no device later
on if needed.
I've also updated the documentation of the function a bit, so that
people looking at it can grasp it hopefully easier :-)
And finally I've dropped the Review tag from Mark. He isn't at
Rockchip for a while now and the driver did change over time a bit.
So if you have time, please take a final look at it.
Thanks
Heiko
Heiko Stuebner (1):
drm/rockchip: add function to check if endpoint is a subdriver
Sandy Huang (2):
drm/rockchip: Add support for Rockchip Soc RGB output interface
drm/rockchip: Add directly output rgb feature for px30
drivers/gpu/drm/rockchip/Kconfig | 11 ++
drivers/gpu/drm/rockchip/Makefile | 1 +
drivers/gpu/drm/rockchip/rockchip_drm_drv.c | 48 ++++++
drivers/gpu/drm/rockchip/rockchip_drm_drv.h | 1 +
drivers/gpu/drm/rockchip/rockchip_drm_vop.c | 16 ++
drivers/gpu/drm/rockchip/rockchip_drm_vop.h | 1 +
drivers/gpu/drm/rockchip/rockchip_rgb.c | 173 ++++++++++++++++++++
drivers/gpu/drm/rockchip/rockchip_rgb.h | 20 +++
drivers/gpu/drm/rockchip/rockchip_vop_reg.c | 2 +
9 files changed, 273 insertions(+)
create mode 100644 drivers/gpu/drm/rockchip/rockchip_rgb.c
create mode 100644 drivers/gpu/drm/rockchip/rockchip_rgb.h
--
2.17.0
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2018-08-30 21:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-30 21:12 Heiko Stuebner [this message]
2018-08-30 21:12 ` [PATCH v8 1/3] drm/rockchip: add function to check if endpoint is a subdriver Heiko Stuebner
2018-08-31 1:41 ` Sandy Huang
2018-08-30 21:12 ` [PATCH v8 2/3] drm/rockchip: Add support for Rockchip Soc RGB output interface Heiko Stuebner
[not found] ` <20180830211207.10480-3-heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>
2019-01-18 0:40 ` [v8, " Thomas Gleixner
[not found] ` <alpine.DEB.2.21.1901180131510.1647-ecDvlHI5BZPZikZi3RtOZ1XZhhPuCNm+@public.gmane.org>
2019-01-18 12:34 ` Heiko Stuebner
2019-01-24 11:41 ` sandy.huang
2018-08-30 21:12 ` [PATCH v8 3/3] drm/rockchip: Add directly output rgb feature for px30 Heiko Stuebner
2018-09-05 11:05 ` [PATCH v8 0/3] Add support rockchip RGB output interface 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=20180830211207.10480-1-heiko@sntech.de \
--to=heiko@sntech.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=hjc@rock-chips.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=seanpaul@chromium.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