From: Inki Dae <inki.dae@samsung.com>
To: Rahul Sharma <rahul.sharma@samsung.com>
Cc: kgene.kim@samsung.com, linux-samsung-soc@vger.kernel.org,
joshi@samsung.com, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 3/5 v2] drm/exynos: allow mulitple layer updates per vsync for mixer
Date: Tue, 24 Jun 2014 14:21:30 +0900 [thread overview]
Message-ID: <53A90ADA.2040306@samsung.com> (raw)
In-Reply-To: <1403501545-16482-4-git-send-email-rahul.sharma@samsung.com>
On 2014년 06월 23일 14:32, Rahul Sharma wrote:
> Allowing only one layer update per vsync can cause issues
> while there are update available for both layers. There is
> a good amount of possibility to loose updates if we allow
> single update per vsync.
>
> Signed-off-by: Rahul Sharma <rahul.sharma@samsung.com>
> ---
> drivers/gpu/drm/exynos/exynos_mixer.c | 7 +------
> 1 file changed, 1 insertion(+), 6 deletions(-)
>
> diff --git a/drivers/gpu/drm/exynos/exynos_mixer.c b/drivers/gpu/drm/exynos/exynos_mixer.c
> index d359501..6773b03 100644
> --- a/drivers/gpu/drm/exynos/exynos_mixer.c
> +++ b/drivers/gpu/drm/exynos/exynos_mixer.c
> @@ -511,13 +511,8 @@ static void vp_video_buffer(struct mixer_context *ctx, int win)
> static void mixer_layer_update(struct mixer_context *ctx)
> {
> struct mixer_resources *res = &ctx->mixer_res;
> - u32 val;
> -
> - val = mixer_reg_read(res, MXR_CFG);
>
> - /* allow one update per vsync only */
> - if (!(val & MXR_CFG_LAYER_UPDATE_COUNT_MASK))
> - mixer_reg_writemask(res, MXR_CFG, ~0, MXR_CFG_LAYER_UPDATE);
> + mixer_reg_writemask(res, MXR_CFG, ~0, MXR_CFG_LAYER_UPDATE);
Rahul, it looks good to me and ok as is. But above codes don't consider
Exynos4 series. In case of Exynos4xxx SoC,
MXR_CFG_LAYER_UPDATE_COUNT_MASK and MXR_CFG_LAYER_UPDATE of MIXER_CFG
register are reserved fields. So can you work that patch to be
considered for Exynos4xxx SoC? That patch would be additional one.
Anyway, will apply it as is, and I will wait for the additional patch.
Thanks,
Inki Dae
> }
>
> static void mixer_graph_buffer(struct mixer_context *ctx, int win)
>
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2014-06-24 5:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-23 5:32 [PATCH 0/5 v2] drm/exynos: fix for misc issues related to exynos mixer Rahul Sharma
2014-06-23 5:32 ` [PATCH 1/5 v2] drm/exynos: set power state variable after enabling clocks and power Rahul Sharma
2014-06-23 5:32 ` [PATCH 2/5 v2] drm/exynos: stop mixer before gating clocks during poweroff Rahul Sharma
2014-06-23 5:32 ` [PATCH 3/5 v2] drm/exynos: allow mulitple layer updates per vsync for mixer Rahul Sharma
2014-06-24 5:21 ` Inki Dae [this message]
2014-06-24 11:38 ` Andreas Färber
2014-06-24 14:50 ` Inki Dae
2014-06-25 10:42 ` Rahul Sharma
2014-06-25 11:57 ` Inki Dae
2014-06-23 5:32 ` [PATCH 4/5 v2] drm/exynos: soft reset mixer before reconfigure after power-on Rahul Sharma
2014-06-23 5:32 ` [PATCH 5/5 v2] drm/exynos: enable vsync interrupt while waiting for vblank Rahul Sharma
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=53A90ADA.2040306@samsung.com \
--to=inki.dae@samsung.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=joshi@samsung.com \
--cc=kgene.kim@samsung.com \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=rahul.sharma@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.