From: sylvain.rochet@finsecur.com (Sylvain Rochet)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv2 1/2] drm: atmel-hlcdc: Add PM suspend/resume support
Date: Sun, 22 Feb 2015 19:03:25 +0100 [thread overview]
Message-ID: <20150222180325.GA18233@gradator.net> (raw)
In-Reply-To: <54E30E2B.5070407@samsung.com>
Hello Andrzej,
On Tue, Feb 17, 2015 at 10:47:23AM +0100, Andrzej Hajda wrote:
> On 02/12/2015 09:49 PM, Sylvain Rochet wrote:
> > +static int atmel_hlcdc_dc_resume(struct drm_device *dev)
> > +{
> > + struct drm_crtc *crtc;
> > +
> > + drm_modeset_lock_all(dev);
> > +
> > + list_for_each_entry(crtc, &dev->mode_config.crtc_list, head) {
> > + struct drm_crtc_helper_funcs *crtc_funcs = crtc->helper_private;
> > + crtc_funcs->enable(crtc);
>
> What about crtc's which were disabled before suspend, they will be
> enabled here unconditionally.
Indeed, fixed in v3.
> > struct atmel_hlcdc_dc *dc = dev->dev_private;
> > @@ -488,6 +518,8 @@ static struct drm_driver atmel_hlcdc_dc_driver = {
> > .driver_features = DRIVER_HAVE_IRQ | DRIVER_GEM | DRIVER_MODESET,
> > .preclose = atmel_hlcdc_dc_preclose,
> > .lastclose = atmel_hlcdc_dc_lastclose,
> > + .suspend = atmel_hlcdc_dc_suspend,
> > + .resume = atmel_hlcdc_dc_resume,
>
> These callbacks are obsolete and should not be used, additionally core
> don't call them if drm_device have DRIVER_MODESET flag.
Oh!, that might explain the struggle I had understanding when they were
actually called. Removed in v3.
> > +#ifdef CONFIG_PM
> > +static int atmel_hlcdc_dc_drm_suspend(struct device *dev)
> > +{
> > + struct drm_device *drm_dev = dev_get_drvdata(dev);
> > + pm_message_t message;
> > +
> > + if (pm_runtime_suspended(dev) || !drm_dev)
>
> Nitpick, !drm_dev is always false, is not?
I guess so, platform_set_drvdata() is called during probe so it can't be
null here. Removed in v3.
> > + return 0;
> > +
> > + message.event = PM_EVENT_SUSPEND;
> > + return atmel_hlcdc_dc_suspend(drm_dev, message);
>
> If you remove obsolete callbacks you can move suspend code here,
> the same for resume.
>
> > +}
> > +
> > +static int atmel_hlcdc_dc_drm_resume(struct device *dev)
> > +{
> > + struct drm_device *drm_dev = dev_get_drvdata(dev);
> > +
> > + if (pm_runtime_suspended(dev) || !drm_dev)
> > + return 0;
> > +
> > + return atmel_hlcdc_dc_resume(drm_dev);
>
> Ditto x2
Indeed, merged in v3.
Thank you very much for this review ! :)
Sylvain
next prev parent reply other threads:[~2015-02-22 18:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-12 20:49 [PATCHv2 0/2] drm: atmel-hlcdc: PM support Sylvain Rochet
2015-02-12 20:49 ` [PATCHv2 1/2] drm: atmel-hlcdc: Add PM suspend/resume support Sylvain Rochet
2015-02-17 9:47 ` Andrzej Hajda
2015-02-22 18:03 ` Sylvain Rochet [this message]
2015-02-12 20:49 ` [PATCHv2 2/2] drm: atmel-hlcdc: Add pinctrl PM select sleep, default state in CRTC suspend/resume Sylvain Rochet
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=20150222180325.GA18233@gradator.net \
--to=sylvain.rochet@finsecur.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).