All of lore.kernel.org
 help / color / mirror / Atom feed
From: Inki Dae <inki.dae@samsung.com>
To: Emil Velikov <emil.l.velikov@gmail.com>,
	Gustavo Padovan <gustavo@padovan.org>
Cc: "moderated list:ARM/S5P EXYNOS AR..."
	<linux-samsung-soc@vger.kernel.org>,
	jg1.han@samsung.com,
	ML dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH] drm/exynos: dp: remove suspend/resume functions
Date: Wed, 30 Sep 2015 22:46:04 +0900	[thread overview]
Message-ID: <560BE79C.6040903@samsung.com> (raw)
In-Reply-To: <CACvgo52GwALBN1Tw_WXntbC6+QJRDrjM7EAFbYtC+VG5OZm9yA@mail.gmail.com>

Hi Emil,

On 2015년 09월 30일 21:19, Emil Velikov wrote:
> Hi Inki,
> 
> On 30 September 2015 at 12:21, Inki Dae <inki.dae@samsung.com> wrote:
>> This patch removes unnecessary pm suspend/resume functions.
>>
>> All kms sub drivers will be controlled by top of Exynos drm driver
>> and connector dpms so these sub drivers shouldn't have their own
>> pm interfaces.
>>
> Not sure if you've noticed but this patch seems to do the opposite of
> what Gustavo was aiming with an earlier series [1].

I removed just the interfaces related to sleep pm not runtime pm. From
long ago, Linux DRM drivers - especially ARM DRM drivers - have been
stepping forward to a integrated DRM driver so it'd be reasonable for
sleep pm operations of all KMS drivers are controlled by top of DRM
driver. It means that Exynos drm driver has already sleep pm interfaces.

However, I think a power domain of each kms device couldn't be
controlled by the top in case of ARM SoC because kms devices can use a
different power domain each other according to Vendor SoC so runtime pm
should be controlled by each kms driver, which will be triggered by DRM top.

And Gustavo's patch set you mentioned - now being reviewed - will add
only runtime pm interfaces to each kms driver.

Thanks,
Inki Dae

> 
> Cheers,
> Emil
> 
> [1] http://lists.freedesktop.org/archives/dri-devel/2015-September/089800.html
> --
> To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2015-09-30 13:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-30 11:21 [PATCH] drm/exynos: dp: remove suspend/resume functions Inki Dae
2015-09-30 12:19 ` Emil Velikov
2015-09-30 13:46   ` Inki Dae [this message]
2015-09-30 14:36     ` Emil Velikov
2015-09-30 14:25 ` Gustavo Padovan

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=560BE79C.6040903@samsung.com \
    --to=inki.dae@samsung.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=emil.l.velikov@gmail.com \
    --cc=gustavo@padovan.org \
    --cc=jg1.han@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.