From: Joonyoung Shim <jy0922.shim@samsung.com>
To: Rob Clark <robdclark@gmail.com>
Cc: Inki Dae <inki.dae@samsung.com>,
kyungmin.park@samsung.com, sw0312.kim@samsung.com,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 5/5] drm/exynos: Add plane support with fimd
Date: Tue, 13 Dec 2011 09:13:41 +0900 [thread overview]
Message-ID: <4EE698B5.5050406@samsung.com> (raw)
In-Reply-To: <CAF6AEGvLQ4_w=utnNLN3nae5DjYB+Tv+dM159AsTe6r9f3sO=g@mail.gmail.com>
On 12/13/2011 07:48 AM, Rob Clark wrote:
> On Fri, Dec 9, 2011 at 4:59 AM, Inki Dae<inki.dae@samsung.com> wrote:
>> +static int
>> +exynos_update_plane(struct drm_plane *plane, struct drm_crtc *crtc,
>> + struct drm_framebuffer *fb, int crtc_x, int crtc_y,
>> + unsigned int crtc_w, unsigned int crtc_h,
>> + uint32_t src_x, uint32_t src_y,
>> + uint32_t src_w, uint32_t src_h)
>> +{
>> + struct exynos_plane *exynos_plane =
>> + container_of(plane, struct exynos_plane, base);
>> + struct exynos_drm_overlay *overlay =&exynos_plane->overlay;
>> + struct exynos_drm_crtc_pos pos;
>> + int ret;
>> +
>> + DRM_DEBUG_KMS("[%d] %s\n", __LINE__, __func__);
>> +
>> + memset(&pos, 0, sizeof(struct exynos_drm_crtc_pos));
>> + pos.crtc_x = crtc_x;
>> + pos.crtc_y = crtc_y;
>> + pos.crtc_w = crtc_w;
>> + pos.crtc_h = crtc_h;
>> +
>> + pos.fb_x = src_x;
>> + pos.fb_y = src_y;
> also, I think src_x/src_y should be interpreted at 16.16/Q16 fixed
> point. But elsewhere were I see fb_x/y used it, it doesn't appear to
> be interpreted this way.
Right, this will be fixed.
Thanks.
> Also, I *think* that comment was meant to apply to src_h/src_w
> (Jesse?), but you seem to ignore these parameters..
>
> BR,
> -R
>
>
>> +
>> + /* TODO: scale feature */
>> + ret = exynos_drm_overlay_update(overlay, fb,&crtc->mode,&pos);
>> + if (ret< 0)
>> + return ret;
>> +
>> + exynos_drm_fn_encoder(crtc, overlay,
>> + exynos_drm_encoder_crtc_mode_set);
>> + exynos_drm_fn_encoder(crtc,&overlay->zpos,
>> + exynos_drm_encoder_crtc_plane_commit);
>> +
>> + exynos_plane->enabled = true;
>> +
>> + return 0;
>> +}
>> +
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/dri-devel
>
prev parent reply other threads:[~2011-12-13 0:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-09 8:23 [PATCH 0/2] update exynos drm driver Inki Dae
2011-12-09 8:23 ` [PATCH 1/2] drm/exynos: updated crtc and encoder dpms framework Inki Dae
2011-12-09 8:23 ` [PATCH 2/2] drm/exynos: add runtime pm feature for fimd Inki Dae
2011-12-09 10:59 ` [PATCH 0/5] update new features Inki Dae
2011-12-09 10:59 ` [PATCH 1/5] drm/exynos: Fix compile errors Inki Dae
2011-12-09 10:59 ` [PATCH 2/5] drm/exynos: Use struct drm_mode_fb_cmd2 Inki Dae
2011-12-09 10:59 ` [PATCH 3/5] drm/exynos: updated crtc and encoder dpms framework Inki Dae
2011-12-09 10:59 ` [PATCH 4/5] drm/exynos: add runtime pm feature for fimd Inki Dae
2011-12-09 10:59 ` [PATCH 5/5] drm/exynos: Add plane support with fimd Inki Dae
2011-12-12 21:59 ` Rob Clark
2011-12-13 0:41 ` Joonyoung Shim
2011-12-13 0:48 ` Rob Clark
2011-12-13 2:39 ` Inki Dae
2011-12-13 2:55 ` Rob Clark
2011-12-12 22:48 ` Rob Clark
2011-12-13 0:13 ` Joonyoung Shim [this message]
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=4EE698B5.5050406@samsung.com \
--to=jy0922.shim@samsung.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=inki.dae@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=robdclark@gmail.com \
--cc=sw0312.kim@samsung.com \
/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