From: Boris Brezillon <boris.brezillon@bootlin.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: David Airlie <airlied@linux.ie>,
Liviu Dudau <Liviu.Dudau@arm.com>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v2 2/8] drm/connector: Pass a drm_connector_state to ->atomic_commit()
Date: Mon, 2 Jul 2018 11:49:11 +0200 [thread overview]
Message-ID: <20180702114911.71f7492f@bbrezillon> (raw)
In-Reply-To: <20180702075146.GC13978@phenom.ffwll.local>
On Mon, 2 Jul 2018 09:51:46 +0200
Daniel Vetter <daniel@ffwll.ch> wrote:
> On Fri, Jun 29, 2018 at 12:37:10PM +0100, Liviu Dudau wrote:
> > On Fri, Jun 29, 2018 at 01:17:15PM +0200, Boris Brezillon wrote:
> > > Other atomic hooks are passed state objects, let's change this one to
> > > be consistent.
> > >
> > > Signed-off-by: Boris Brezillon <boris.brezillon@bootlin.com>
> > > ---
> > > drivers/gpu/drm/drm_atomic_helper.c | 2 +-
> > > include/drm/drm_modeset_helper_vtables.h | 4 +++-
> > > 2 files changed, 4 insertions(+), 2 deletions(-)
> > >
> > > diff --git a/drivers/gpu/drm/drm_atomic_helper.c b/drivers/gpu/drm/drm_atomic_helper.c
> > > index 17baf5057132..69063bcf2334 100644
> > > --- a/drivers/gpu/drm/drm_atomic_helper.c
> > > +++ b/drivers/gpu/drm/drm_atomic_helper.c
> > > @@ -1187,7 +1187,7 @@ static void drm_atomic_helper_commit_writebacks(struct drm_device *dev,
> > >
> > > if (new_conn_state->writeback_job && new_conn_state->writeback_job->fb) {
> > > WARN_ON(connector->connector_type != DRM_MODE_CONNECTOR_WRITEBACK);
> > > - funcs->atomic_commit(connector, new_conn_state->writeback_job);
> > > + funcs->atomic_commit(connector, new_conn_state);
> >
> > Forgot to add: I think it is worth adding a check here that the hook has
> > been implemented by the driver, AFAIK it is not a mandatory hook, even
> > for writeback enabled drivers.
I'm just curious, from where do you queue the writeback job if you don't
have a connector->atomic_commit() hook implemented? AFAICT, the
encoder->enable() method is only called when the encoder is being
enabled, and not every time you update the FB_ID prop of the writeback
connector. Am I missing something?
>
> Either way this should be documented in the hook (atm it says nothing
> about whether it's mandatory/optional and for whom).
I'm fine making this hook optional. I'll update the code and the doc in
a separate commit.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-07-02 9:49 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-29 11:17 [PATCH v2 0/8] drm/vc4: Add support for the transposer IP Boris Brezillon
2018-06-29 11:17 ` [PATCH v2 1/8] drm/atomic: Avoid connector to writeback_connector casts Boris Brezillon
2018-07-02 7:49 ` Daniel Vetter
2018-06-29 11:17 ` [PATCH v2 2/8] drm/connector: Pass a drm_connector_state to ->atomic_commit() Boris Brezillon
2018-06-29 11:23 ` Liviu Dudau
2018-06-29 11:37 ` Liviu Dudau
2018-07-02 7:51 ` Daniel Vetter
2018-07-02 9:49 ` Boris Brezillon [this message]
2018-07-02 11:14 ` Liviu Dudau
2018-07-02 11:58 ` Boris Brezillon
2018-06-29 11:17 ` [PATCH v2 3/8] drm/vc4: Use wait_for_flip_done() instead of wait_for_vblanks() Boris Brezillon
2018-06-29 20:19 ` Eric Anholt
2018-06-29 11:17 ` [PATCH v2 4/8] drm/crtc: Add a generic infrastructure to fake VBLANK events Boris Brezillon
2018-06-29 11:38 ` Liviu Dudau
2018-07-02 8:02 ` Daniel Vetter
2018-07-02 8:14 ` Boris Brezillon
2018-07-02 8:37 ` Daniel Vetter
2018-07-02 9:01 ` Boris Brezillon
2018-07-02 8:40 ` Daniel Vetter
2018-07-02 8:46 ` Boris Brezillon
2018-06-29 11:17 ` [PATCH v2 5/8] drm/atomic: Call drm_atomic_helper_fake_vblank() from the generic commit_tail() helpers Boris Brezillon
2018-06-29 11:38 ` Liviu Dudau
2018-07-02 7:54 ` Daniel Vetter
2018-07-02 7:57 ` Daniel Vetter
2018-07-02 7:59 ` Boris Brezillon
2018-07-02 7:58 ` Boris Brezillon
2018-06-29 11:17 ` [PATCH v2 6/8] drm/vc4: Call drm_atomic_helper_fake_vblank() in the commit path Boris Brezillon
2018-06-29 20:27 ` Eric Anholt
2018-06-29 11:17 ` [PATCH v2 7/8] drm/vc4: Add support for the transposer block Boris Brezillon
2018-06-29 20:35 ` Eric Anholt
2018-07-02 10:19 ` Boris Brezillon
2018-06-29 11:17 ` [PATCH v2 8/8] ARM: dts: bcm283x: Add Transposer block Boris Brezillon
2018-06-29 20:27 ` Eric Anholt
2018-06-29 11:17 ` [PATCH v2 0/8] drm/vc4: Add support for the transposer IP Boris Brezillon
2018-06-29 11:40 ` Liviu Dudau
2018-07-02 10:21 ` Boris Brezillon
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=20180702114911.71f7492f@bbrezillon \
--to=boris.brezillon@bootlin.com \
--cc=Liviu.Dudau@arm.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
/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