[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <154632658.xpTMZOjgxT@phil>
Date: Sun, 30 Dec 2018 18:22:00 +0100
From: Heiko Stuebner <heiko@...ech.de>
To: Johan Jonker <jbx6244@...il.com>
Cc: hjc@...k-chips.com, airlied@...ux.ie, robh+dt@...nel.org,
mark.rutland@....com, mturquette@...libre.com, sboyd@...nel.org,
dri-devel@...ts.freedesktop.org, devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
linux-rockchip@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-clk@...r.kernel.org
Subject: Re: [PATCH v2 3/7] drm: rockchip: vop: add rk3066 vop definitions
Hi Johan,
Am Samstag, 29. Dezember 2018, 14:33:14 CET schrieb Johan Jonker:
> From: Mark Yao <mark.yao@...k-chips.com>
>
> This patch adds the rk3066 VOP definitions.
>
> The VOP or LCD Controller serves as interface between
> framebuffer memory and a display device (LCD panel or TV set).
>
> This SOC has two symmetrical LCDC's for a dual panel application.
>
> A LCDC has 5 display layers.
> Only 3 are used here.
>
> - Video layer 0 (Win0)
> - Video layer 1 (Win1)
> - OSD layer (Win2)
Patch itself looks good, we'll need to wait a bit to give Rob a chance
to look at the (simple) dt-binding change and I'll drop the paragraph
about the display layers when applying.
Looking at the rk3066-manual, the lcdcs really only have 3 fully usable
layers + the special cursor layer which is right now not really usable in
a drm context, so the above paragraph is misleading, so I'll just drop it.
Heiko
> Win0 and Win1 are exchangeable.
> Maximum resolution is 1920x1080.
>
> The LCDC0 output is connected to:
> - LCDC0 IO (without IOMUX)
> - HDMI TX video input
>
> The LCDC1 output is connected to:
> - LCDC1 IO (with IOMUX)
> - HDMI TX video input
>
> The HDMI TX input can switch between LCDC0 and LCDC1.
>
> Signed-off-by: Mark Yao <mark.yao@...k-chips.com>
> Signed-off-by: Johan Jonker <jbx6244@...il.com>
Powered by blists - more mailing lists