linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: myungjoo.ham@samsung.com (MyungJoo Ham)
To: linux-arm-kernel@lists.infradead.org
Subject: RE: [PATCH v10 5/5] drm/rockchip: Add dmc notifier in vop driver
Date: Tue, 06 Sep 2016 04:37:54 +0000	[thread overview]
Message-ID: <705204681.416743.1473136674125.JavaMail.weblogic@ep1ml102b> (raw)
In-Reply-To: CGME20160905050631epcas1p4ebe75a5f119132f583a5020187382026@epcas1p4.samsung.com

> when in ddr frequency scaling process, vop can not do enable or
> disable operation, since in dcf we check vop clock to see whether
> vop work. If vop work, dcf do ddr frequency scaling when vop
> in vblank status, and we need to read vop register to check whether
> vop go into vblank status. If vop not work, dcf can do ddr frequency
> any time. So when do ddr frequency scaling, you disabled or enable
> vop, there may two bad thing happen: 1, the panel flicker(when vop from
> disable status change to enable). 2, kernel hang (when vop from enable
> status change to disable, dcf need to read vblank status, but if you disable
> vop clock, it can not get the status, it will lead soc dead) So we need
> register to devfreq notifier, and we can get the dmc status. Also, when
> there have two vop enabled, we need to disable dmc, since dcf only base
> on one vop vblank time, so the other panel will flicker when do ddr
> frequency scaling.
> 
> Signed-off-by: Lin Huang <hl@rock-chips.com>
> Reviewed-by: Chanwoo Choi <cw00.choi@samsung.com>


Acked-by: MyungJoo Ham <myungjoo.ham@samsung.com>


The code looks fine, but I've just found that I cannot merge this
code as I am not handling drivers/gpu/drm.

Please try to merge this piece into drivers/gpu/drm tree.

For the other 4 piecies (1/5 to 4/5) I'm ok with them. I'm merging them now.


> ---
> Changes in v10:
> - None
> 
> Changes in v9:
> - None
> 
> Changes in v8:
> - None
> 
> Changes in v7:
> - None
> 
> Changes in v6:
> - fix a build error
> 
> Changes in v5:
> - improve some nits
> 
> Changes in v4:
> - register notifier to devfreq_register_notifier
> - use DEVFREQ_PRECHANGE and DEVFREQ_POSTCHANGE to get dmc status
> - when two vop enable, disable dmc
> - when two vop back to one vop, enable dmc
> 
> Changes in v3:
> - when do vop eanble/disable, dmc will wait until it finish
> 
> Changes in v2:
> - None
> 
> Changes in v1:
> - use wait_event instead usleep
> 
>  drivers/gpu/drm/rockchip/rockchip_drm_vop.c | 116 ++++++++++++++++++++++++++++
>  1 file changed, 116 insertions(+)
> 

      parent reply	other threads:[~2016-09-06  4:37 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-05  5:06 [PATCH v10 0/5] rk3399 support ddr frequency scaling Lin Huang
2016-09-05  5:06 ` [PATCH v10 1/5] Documentation: bindings: add dt documentation for dfi controller Lin Huang
2016-09-12 16:18   ` Rob Herring
2016-09-05  5:06 ` [PATCH v10 2/5] PM / devfreq: event: support rockchip " Lin Huang
2016-09-05  5:06 ` [PATCH v10 3/5] Documentation: bindings: add dt documentation for rk3399 dmc Lin Huang
2016-09-12 16:31   ` Rob Herring
2016-09-05  5:06 ` [PATCH v10 4/5] PM / devfreq: rockchip: add devfreq driver " Lin Huang
2016-09-05  5:06 ` [PATCH v10 5/5] drm/rockchip: Add dmc notifier in vop driver Lin Huang
2016-09-06  3:40   ` kbuild test robot
2016-09-06 17:18   ` Sean Paul
2016-09-06 18:15     ` hl
2016-09-06 18:55       ` Sean Paul
2016-09-06 19:01         ` hl
2016-09-06 19:07           ` Sean Paul
2016-09-07 18:07             ` dbasehore .
2016-09-07 18:27               ` Sean Paul
2016-09-07 18:13     ` dbasehore .
2016-09-07 20:31       ` Sean Paul
2016-09-07 22:21         ` dbasehore .
     [not found] ` <CGME20160905050631epcas1p4ebe75a5f119132f583a5020187382026@epcas1p4.samsung.com>
2016-09-06  4:37   ` MyungJoo Ham [this message]

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=705204681.416743.1473136674125.JavaMail.weblogic@ep1ml102b \
    --to=myungjoo.ham@samsung.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).