From: Vincent ABRIOU <vincent.abriou@st.com>
To: Emil Velikov <emil.l.velikov@gmail.com>
Cc: Benjamin Gaignard <benjamin.gaignard@linaro.org>,
Vincent ABRIOU <vincent.abriou@st.com>,
Fabien DESSENNE <fabien.dessenne@st.com>,
ML dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH] drm/sti: load HQVDP firmware the first time HQVDP's plane is used
Date: Wed, 4 Nov 2015 10:17:26 +0100 [thread overview]
Message-ID: <5639CD26.7000609@st.com> (raw)
In-Reply-To: <CACvgo53hui00oHxvH6m1_qvMS7z+Twpk1bdCL6gwqSjn7V16wA@mail.gmail.com>
Hi Emil,
On 11/03/2015 03:55 PM, Emil Velikov wrote:
> Hi Vincent,
>
> On 2 November 2015 at 10:05, Vincent Abriou <vincent.abriou@st.com> wrote:
>> @@ -754,6 +901,9 @@ static void sti_hqvdp_atomic_update(struct drm_plane *drm_plane,
>> sti_hqvdp_update_hvsrc(HVSRC_VERT, scale_v, &cmd->hvsrc);
>>
>> if (first_prepare) {
>> + /* Start HQVDP XP70 coprocessor */
>> + sti_hqvdp_start_xp70(hqvdp);
>> +
> Shouldn't one check for things such as this (and
> sti_hqvdp_check_hw_scaling, amongst other things) in atomic_check() ?
> Mostl/all other drivers seems to do so. After all drm core check()s
> and if everything/state is ok then calls update().
>
Thanks to highlight me this point.
Atomic has been newly introduced in our sti driver and we updated our
driver in a straightforward way to make it work with atomic leaving
aside such point.
I will trig a rework for this for the next update of our driver taking
into account atomic_check for planes management.
Regards
Vincent
> Regards,
> Emil
>
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2015-11-04 9:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-02 10:05 [PATCH] drm/sti: load HQVDP firmware the first time HQVDP's plane is used Vincent Abriou
2015-11-03 14:55 ` Emil Velikov
2015-11-04 9:17 ` Vincent ABRIOU [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=5639CD26.7000609@st.com \
--to=vincent.abriou@st.com \
--cc=benjamin.gaignard@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=emil.l.velikov@gmail.com \
--cc=fabien.dessenne@st.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.