public inbox for linux-rockchip@lists.infradead.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Yakir Yang <ykk@rock-chips.com>
Cc: Krzysztof Kozlowski <k.kozlowski@samsung.com>,
	linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-rockchip@lists.infradead.org, Mark Yao <yzq@rock-chips.com>,
	Jingoo Han <jingoohan1@gmail.com>,
	emil.l.velikov@gmail.com, dianders@chromium.org,
	dri-devel@lists.freedesktop.org, tfiga@chromium.org,
	daniel.vetter@ffwll.ch, Thierry Reding <treding@nvidia.com>,
	Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: [RFC PATCH v1 0/2]
Date: Tue, 31 May 2016 16:38:31 +0200	[thread overview]
Message-ID: <20160531143831.GK7231@phenom.ffwll.local> (raw)
In-Reply-To: <1464701856-8695-1-git-send-email-ykk@rock-chips.com>

On Tue, May 31, 2016 at 09:37:36PM +0800, Yakir Yang wrote:
> The full name of PSR is Panel Self Refresh, panel device could refresh
> itself with the hardware framebuffer in panel, this would make a lots
> of sense to save the power consumption.
> 
> For example, when desktop haven't change the context for a long time,
> then we could refresh the data to the hardware framebuffer of panel,
> and then let panel enter into PSR mode. After that system could poweroff
> the LCDC controller and eDP controller, just let panel refresh the screen
> by itself.
> 
> It's hard to decide when panel should enter into PSR or exit from PSR, in
> this time I chose to let the drm_vblank enable/disable event driver the PSR.
> 
> This thread is based on Mark's RK3399 VOP thread[0] and my RK3399 eDP
> thread[1].
> 
> [0]: https://patchwork.kernel.org/patch/8886041/
> [1]: https://patchwork.kernel.org/patch/9132713/

Looks like you didn't wire up the drm_framebuffer->funcs->dirty callback
for manual upload of simple clients like bootsplash or fbdev. I think
that's needed. At least it's needed for every other manual upload dsi and
edp psr implementation.
-Daniel

> 
> - Yakir
> Thanks,
> 
> 
> Yakir Yang (2):
>   drm/rockchip: add a notify event about vblank enable/disable
>   drm/rockchip: analogix: add eDP PSR function
> 
>  drivers/gpu/drm/bridge/analogix/analogix_dp_core.c |  69 ++++++++++++++
>  drivers/gpu/drm/bridge/analogix/analogix_dp_core.h |   5 +
>  drivers/gpu/drm/bridge/analogix/analogix_dp_reg.c  |  54 +++++++++++
>  drivers/gpu/drm/bridge/analogix/analogix_dp_reg.h  |  28 ++++++
>  drivers/gpu/drm/rockchip/Makefile                  |   2 +-
>  drivers/gpu/drm/rockchip/analogix_dp-rockchip.c    |  65 +++++++++++++
>  drivers/gpu/drm/rockchip/rockchip_drm_notify.c     | 105 +++++++++++++++++++++
>  drivers/gpu/drm/rockchip/rockchip_drm_notify.h     |  33 +++++++
>  drivers/gpu/drm/rockchip/rockchip_drm_vop.c        |  96 +++++++++++++++++++
>  drivers/gpu/drm/rockchip/rockchip_drm_vop.h        |   3 +
>  drivers/gpu/drm/rockchip/rockchip_vop_reg.c        |   2 +
>  include/drm/bridge/analogix_dp.h                   |   3 +
>  12 files changed, 464 insertions(+), 1 deletion(-)
>  create mode 100644 drivers/gpu/drm/rockchip/rockchip_drm_notify.c
>  create mode 100644 drivers/gpu/drm/rockchip/rockchip_drm_notify.h
> 
> -- 
> 1.9.1
> 
> 

-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2016-05-31 14:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-31 13:37 [RFC PATCH v1 0/2] Yakir Yang
2016-05-31 13:39 ` [RFC PATCH v1 1/2] drm/rockchip: add a notify event about vblank enable/disable Yakir Yang
2016-05-31 14:36   ` Daniel Vetter
2016-06-01  2:52     ` Yakir Yang
2016-05-31 13:39 ` [RFC PATCH v1 2/2] drm/rockchip: analogix: add eDP PSR function Yakir Yang
2016-05-31 14:38 ` Daniel Vetter [this message]
2016-06-01  2:41   ` [RFC PATCH v1 0/2] Yakir Yang
2016-06-01  2:54   ` Yakir Yang
2016-06-02 14:19     ` Daniel Vetter
2016-06-03  5:45       ` Yakir Yang

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=20160531143831.GK7231@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=dan.carpenter@oracle.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dianders@chromium.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=emil.l.velikov@gmail.com \
    --cc=jingoohan1@gmail.com \
    --cc=k.kozlowski@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=tfiga@chromium.org \
    --cc=treding@nvidia.com \
    --cc=ykk@rock-chips.com \
    --cc=yzq@rock-chips.com \
    /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