[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20150210144351.GA14171@gradator.net>
Date: Tue, 10 Feb 2015 15:43:51 +0100
From: Sylvain Rochet <sylvain.rochet@...secur.com>
To: Boris Brezillon <boris.brezillon@...e-electrons.com>
Cc: David Airlie <airlied@...ux.ie>, dri-devel@...ts.freedesktop.org,
Nicolas Ferre <nicolas.ferre@...el.com>,
Jean-Christophe Plagniol-Villard <plagnioj@...osoft.com>,
Alexandre Belloni <alexandre.belloni@...e-electrons.com>,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
Daniel Vetter <daniel@...ll.ch>
Subject: Re: [PATCH 1/2] drm: atmel-hlcdc: Add PM suspend/resume support
Hello Boris,
On Tue, Feb 10, 2015 at 03:05:57PM +0100, Boris Brezillon wrote:
> On Tue, 10 Feb 2015 14:40:45 +0100
> Sylvain Rochet <sylvain.rochet@...secur.com> wrote:
> > +
> > +static SIMPLE_DEV_PM_OPS(atmel_hlcdc_dc_drm_pm_ops,
> > + atmel_hlcdc_dc_drm_suspend, atmel_hlcdc_dc_drm_resume);
> > +
>
> Do we really need to register both SIMPLE_DEV_PM_OPS and drm_driver
> suspend/resume functions.
> I thought the suspend/resume callbacks were called by DRM core code
> as part of the PM class specific operations.
> However, exynos driver seems to do the same, so this might well be
> required.
Looks like we need, if I comment out SIMPLE_DEV_PM_OPS ops registration
we don't suspend or resume anymore. I guess drm_driver suspend/resume
functions are only used for PM runtime support, which we don't support
yet, at least we added the basic requirements to add PM runtime support
at some point in the future.
Anyway, even without PM runtime support we need to suspend and resume
this device, other DRM drivers do this as well.
Sylvain
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists