From: Inki Dae <inki.dae@samsung.com>
To: Rahul Sharma <rahul.sharma@samsung.com>
Cc: "Kukjin Kim" <kgene.kim@samsung.com>,
linux-samsung-soc <linux-samsung-soc@vger.kernel.org>,
"Andreas Färber" <afaerber@suse.de>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"sunil joshi" <joshi@samsung.com>
Subject: Re: [PATCH 3/5 v2] drm/exynos: allow mulitple layer updates per vsync for mixer
Date: Wed, 25 Jun 2014 20:57:30 +0900 [thread overview]
Message-ID: <53AAB92A.4070208@samsung.com> (raw)
In-Reply-To: <CAPdUM4OLCjCW-wiUEaN90eSjkNxJi--c4ThBb7fyKy_K2H_R9w@mail.gmail.com>
On 2014년 06월 25일 19:42, Rahul Sharma wrote:
> Thanks Inki,
>
> One more thing. mixer_layer_update is only called on for mixer version;
> MXR_VER_16_0_33_0, MXR_VER_128_0_0_184. This condition
> should have taken care of Exynos4 scenarios. What you say?
>
There was my missing point. :) Already considered. ignore my comment.
Thanks,
Inki Dae
> Regards,
> Rahul Sharma.
>
> On 24 June 2014 20:20, Inki Dae <inki.dae@samsung.com> wrote:
>> 2014-06-24 20:38 GMT+09:00 Andreas Färber <afaerber@suse.de>:
>>> Am 24.06.2014 07:21, schrieb Inki Dae:
>>>> 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.
>>>
>>> If it's not too late, could you fix up "multiple" in the subject? :)
>>
>> Corrected. :)
>>
>> Thanks,
>> Inki Dae
>>
>>>
>>> Cheers,
>>> Andreas
>>>
>>> --
>>> SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
>>> GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
_______________________________________________
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-25 11:57 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
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 [this message]
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=53AAB92A.4070208@samsung.com \
--to=inki.dae@samsung.com \
--cc=afaerber@suse.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox