Re: [PATCH v2 1/5] drm/rockchip: Add basic drm driver

From: yaozq
Date: Thu Sep 18 2014 - 22:04:14 EST


On 2014å09æ18æ 22:53, Daniel Vetter wrote:
On Thu, Sep 18, 2014 at 04:52:14PM +0200, Daniel Vetter wrote:
On Thu, Sep 18, 2014 at 05:36:31PM +0800, Mark yao wrote:
This patch adds the basic structure of a DRM Driver for Rockchip Socs.

Signed-off-by: Mark yao <mark.yao@xxxxxxxxxxxxxx>
---
Changes in v2:
- use the component framework to defer main drm driver probe
until all VOP devices have been probed.
- use dma-mapping API with ARM_DMA_USE_IOMMU, create dma mapping by
master device and each vop device can shared the drm dma mapping.
- use drm_crtc_init_with_planes and drm_universal_plane_init.
- remove unnecessary middle layers.
- add cursor set, move funcs to rockchip drm crtc.
- use vop reset at first init
- reference framebuffer when used and unreference when swap out vop

+static const struct drm_crtc_funcs rockchip_crtc_funcs = {
+ .set_config = drm_crtc_helper_set_config,
+ .page_flip = rockchip_drm_crtc_page_flip,
+ .destroy = rockchip_drm_crtc_destroy,
+ .cursor_set = vop_crtc_cursor_set,
+ .cursor_move = vop_crtc_cursor_move,
If you expose your cursor plane as a universal you don't need to implement
these two cursor functions at all. Actually the core never calls them, see
drm_mode_cursor_universal. So if you want to expose cursors, please use
universal cursor plane support (like i915).

In general that's how new drivers should expose cursors since without
universal planes support cursors will not be supported with the atomic
ioctl. Since your cursor code just calls the relevant plane functions that
should even simplify your driver ;-)
Actually you already initialize with cursor universal planes, so all this
code can simply be removed.
-Daniel
I see, drm_mode_cursor_universal is nice, I would test and use it.
-Mark

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/