From: Andrzej Hajda <a.hajda@samsung.com>
To: Inki Dae <inki.dae@samsung.com>, dri-devel@lists.freedesktop.org
Cc: airlied@linux.ie, linux-samsung-soc@vger.kernel.org
Subject: Re: [PATCH v2 0/7] drm/exynos: add pm runtime support
Date: Tue, 03 Nov 2015 14:24:14 +0100 [thread overview]
Message-ID: <5638B57E.9070702@samsung.com> (raw)
In-Reply-To: <1446547629-12521-1-git-send-email-inki.dae@samsung.com>
Hi Inki,
On 11/03/2015 11:47 AM, Inki Dae wrote:
> This patch series adds pm runtime support for Exynos drm.
>
> Originally, this patch was posted by Gustavo but there was no any
> answer about some comments. So I rebased this patch series on top of
> exynos-drm-next, removed unnecessary patches and modified wrong macro.
I have sent comment to original patchset[1], but for some strange reasons
it went only to mailing lists.
My concerns were as follows:
- exynos_drm has already pm_runtime support via exynos_drm_drv pm ops,
why should we add per component support?
- component suspend sequence is non deterministic, but in case of
video pipelines, specification often requires fixed order,
- the patchset adds implicit dependency on PM_SLEEP.
Current solution should work correctly and it was OK last time I have tested it.
I am not sure about atomic requirements, are there special ones?
There are other issues with current solution, rather easy to solve:
- it assumes that exynos-drm device will be suspended first - it should be true,
as it is created at the end and suspend order is reverse to creation order, but
I am not sure if we can rely on it - some solution is to add pm callbacks to
all components, and from those callbacks call one centralized pm routine,
- suspend/resume callbacks theoretically can be called during component
master initialization/deinitailization it could be racy,
- exynos_drm_sys_suspend/resume calls exynos_drm_suspend/resume
for historical reasons, these function can be merged together.
[1]: http://permalink.gmane.org/gmane.linux.kernel.samsung-soc/48395
Regards
Andrzej
>
> Changelog v2:
> - Remove patch 5 and 6.
> . commit callback are already removed so isn't required anymore.
> - Remove patch 8 which makes dp clock enabled directly from FIMD.
> . Really not mendatory for FIMD uses DP, and it could be different
> according to Board.
> - Modified CONFIG_PM_SLEEP to CONFIG_PM.
> . In case of runtime pm, CONFIG_PM macro should be used instead of
> CONFIG_PM_SLEEP.
>
> Gustavo Padovan (7):
> drm/exynos: do not start enabling DP at bind() phase
> drm/exynos: add pm_runtime to DP
> drm/exynos: add pm_runtime to HDMI
> drm/exynos: add pm_runtime to Mixer
> drm/exynos: add pm_runtime to FIMD
> drm/exynos: add pm_runtime to DECON 5433
> drm/exynos: add pm_runtime to DECON 7
>
> drivers/gpu/drm/exynos/exynos5433_drm_decon.c | 54 ++++++---
> drivers/gpu/drm/exynos/exynos7_drm_decon.c | 125 +++++++++----------
> drivers/gpu/drm/exynos/exynos_dp_core.c | 165 +++++++++++++++++++-------
> drivers/gpu/drm/exynos/exynos_dp_core.h | 1 +
> drivers/gpu/drm/exynos/exynos_drm_fimd.c | 91 ++++++--------
> drivers/gpu/drm/exynos/exynos_hdmi.c | 56 ++++++---
> drivers/gpu/drm/exynos/exynos_mixer.c | 125 ++++++++++---------
> 7 files changed, 352 insertions(+), 265 deletions(-)
>
next prev parent reply other threads:[~2015-11-03 13:24 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-03 10:47 [PATCH v2 0/7] drm/exynos: add pm runtime support Inki Dae
2015-11-03 10:47 ` [PATCH v2 1/7] drm/exynos: do not start enabling DP at bind() phase Inki Dae
2015-11-03 10:47 ` [PATCH v2 2/7] drm/exynos: add pm_runtime to DP Inki Dae
2015-11-03 10:47 ` [PATCH v2 3/7] drm/exynos: add pm_runtime to HDMI Inki Dae
2015-11-03 10:47 ` [PATCH v2 4/7] drm/exynos: add pm_runtime to Mixer Inki Dae
2015-11-03 10:47 ` [PATCH v2 5/7] drm/exynos: add pm_runtime to FIMD Inki Dae
2015-11-03 10:47 ` [PATCH v2 6/7] drm/exynos: add pm_runtime to DECON 5433 Inki Dae
2015-11-03 10:47 ` [PATCH v2 7/7] drm/exynos: add pm_runtime to DECON 7 Inki Dae
2015-11-03 13:24 ` Andrzej Hajda [this message]
2015-11-03 15:38 ` [PATCH v2 0/7] drm/exynos: add pm runtime support Inki Dae
2015-11-04 7:24 ` Andrzej Hajda
2015-11-04 7:56 ` Inki Dae
2015-11-04 10:13 ` Andrzej Hajda
2015-11-04 11:46 ` Inki Dae
2015-11-19 14:51 ` Javier Martinez Canillas
2015-11-19 14:55 ` Javier Martinez Canillas
2015-11-19 15:51 ` Javier Martinez Canillas
2015-11-20 10:59 ` Inki Dae
2015-11-20 11:13 ` Inki Dae
2015-11-20 16:44 ` Javier Martinez Canillas
2015-11-21 9:38 ` Inki Dae
2015-11-21 13:40 ` Daniel Stone
2015-11-21 14:59 ` Inki Dae
2015-11-23 12:25 ` Javier Martinez Canillas
2015-11-23 16:47 ` Inki Dae
2015-11-23 18:38 ` Javier Martinez Canillas
2015-11-24 2:28 ` Inki Dae
2015-11-24 13:19 ` Javier Martinez Canillas
2015-11-25 15:52 ` Inki Dae
2015-11-20 16:23 ` Javier Martinez Canillas
2015-11-21 9:40 ` Inki Dae
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=5638B57E.9070702@samsung.com \
--to=a.hajda@samsung.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=inki.dae@samsung.com \
--cc=linux-samsung-soc@vger.kernel.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 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.