From: Philipp Zabel <p.zabel@pengutronix.de>
To: Stefan Agner <stefan@agner.ch>,
Leonard Crestez <leonard.crestez@nxp.com>
Cc: Marek Vasut <marex@denx.de>, Anson Huang <Anson.Huang@nxp.com>,
David Airlie <airlied@linux.ie>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
Robert Chiras <robert.chiras@nxp.com>,
linux-imx@nxp.com, kernel@pengutronix.de,
Fabio Estevam <fabio.estevam@nxp.com>,
Shawn Guo <shawnguo@kernel.org>,
Lucas Stach <l.stach@pengutronix.de>
Subject: Re: [PATCH v2] drm/mxsfb: Fix runtime PM for unpowering lcdif block
Date: Thu, 02 Aug 2018 13:40:10 +0200 [thread overview]
Message-ID: <1533210010.3516.21.camel@pengutronix.de> (raw)
In-Reply-To: <053a788e297c5b54baa80d03586da53d@agner.ch>
Hi Stefan,
On Wed, 2018-08-01 at 12:00 +0200, Stefan Agner wrote:
[...]
> > @@ -307,14 +335,15 @@ void mxsfb_plane_atomic_update(struct
> > mxsfb_drm_private *mxsfb,
> > drm_crtc_send_vblank_event(crtc, event);
> > }
> > }
> > spin_unlock_irq(&crtc->dev->event_lock);
> >
> > - if (!fb)
> > + if (!mxsfb->enabled)
> > return;
> >
>
> I think this is the wrong thing to do.
>
> The simple KMS helper callback ->update() is called by the
> ->atomic_update() callback of drm_plane_helper_funcs.
>
> And the documentation of atomic_update() states:
> https://01.org/linuxgraphics/gfx-docs/drm/gpu/drm-kms-helpers.html#c.drm_plane_helper_funcs
>
> "Note that the power state of the display pipe when this function is
> called depends upon the exact helpers and calling sequence the driver
> has picked. See drm_atomic_helper_commit_planes() for a discussion of
> the tradeoffs and variants of plane commit helpers."
>
> The documentation of drm_atomic_helper_commit_planes() then has more
> information:
> https://01.org/linuxgraphics/gfx-docs/drm/gpu/drm-kms-helpers.html#c.drm_atomic_helper_commit_planes
>
> Bottom line, we should be using drm_atomic_helper_commit_tail_rpm() for
> runtime pm...
>
> So adding something like:
>
> static const struct drm_mode_config_helper_funcs
> mxsfb_drm_mode_config_helpers = {
> .atomic_commit_tail = drm_atomic_helper_commit_tail_rpm,
> };
>
> And add something like this in mxsfb_load:
>
> drm->mode_config.funcs = &mxsfb_mode_config_funcs;
> + dev->mode_config.helper_private = &mxsfb_drm_mode_config_helpers;
> ...
>
> Should make the stack not calling update while the pipe is disabled.
>
> With that you do not have to keep state locally and can always apply the
> new state in ->enable().
Yes, thank you for the explanation. That is exactly what I would have
expected.
regards
Philipp
prev parent reply other threads:[~2018-08-02 11:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-17 10:48 Leonard Crestez
2018-07-31 11:16 ` Leonard Crestez
2018-07-31 11:54 ` Philipp Zabel
2018-07-31 12:17 ` Leonard Crestez
2018-08-02 10:17 ` Philipp Zabel
2018-08-02 11:06 ` Stefan Agner
2018-08-02 11:39 ` Leonard Crestez
2018-08-01 10:00 ` Stefan Agner
2018-08-02 11:40 ` Philipp Zabel [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=1533210010.3516.21.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=Anson.Huang@nxp.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=fabio.estevam@nxp.com \
--cc=kernel@pengutronix.de \
--cc=l.stach@pengutronix.de \
--cc=leonard.crestez@nxp.com \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marex@denx.de \
--cc=robert.chiras@nxp.com \
--cc=shawnguo@kernel.org \
--cc=stefan@agner.ch \
/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
all inboxes | Powered by JetHome®