Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: ryadav-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org
To: Daniel Vetter <daniel-/w4YWyX8dFk@public.gmane.org>
Cc: linux-arm-msm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	hoegsberg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org,
	freedreno-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
	dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
	Daniel Vetter <daniel.vetter-/w4YWyX8dFk@public.gmane.org>
Subject: Re: [DPU PATCH v2 0/2] Remove DPU RSC support
Date: Wed, 04 Apr 2018 16:53:51 +0530	[thread overview]
Message-ID: <9b96938a6c783fd00e55cc767592ec7e@codeaurora.org> (raw)
In-Reply-To: <20180404102633.GG3881-dv86pmgwkMBes7Z6vYuT8azUEOm+Xw19@public.gmane.org>

On 2018-04-04 15:56, Daniel Vetter wrote:
> On Wed, Apr 04, 2018 at 02:34:40PM +0530, Rajesh Yadav wrote:
>> MSM display controller hardware (DPU) has an inbuilt RSC block
>> which can control power resources and bus bandwidth voting
>> based on frame timing parameters w/o DPU driver intervention.
>> In absence of RSC HW, DPU driver controls these resources.
>> 
>> Downstream driver relies on RSC driver for controlling these
>> resources (via RSC HW block) for better power benefits.
>> 
>> Since, DPU driver can control these resources, removing RSC
>> driver support. Corresponding devicetree binding are also removed.
> 
> If it has benefits, why remove the support for this?
> -Daniel
Currently, the dpu driver has custom implementation for power 
management.
We are planning to move to runtime_pm and this change is 1st step toward 
that goal.
We will re-introduce the RSC support at a later stage when all the 
dependencies
are sent upstream.

Thanks,
Rajesh
> 
>> 
>> Details for DPU driver upstreaming:
>> https://lists.freedesktop.org/archives/freedreno/2018-February/001678.html
>> 
>> Changes in v2:
>> 	- Remove last reference to dpu_power_rsc_update
>> 	- Add DPU PATCH tag for better filtering
>> 	- Rebase on tip of for-next-staging
>> 
>> Rajesh Yadav (2):
>>   dt-bindings: msm/disp: Remove DPU RSC device bindings
>>   drm/msm: Remove RSC support from DPU driver
>> 
>>  .../devicetree/bindings/display/msm/dpu-rsc.txt    |   96 --
>>  drivers/gpu/drm/msm/disp/dpu1/dpu_core_perf.c      |  130 +-
>>  drivers/gpu/drm/msm/disp/dpu1/dpu_core_perf.h      |    6 -
>>  drivers/gpu/drm/msm/disp/dpu1/dpu_crtc.c           |   14 -
>>  drivers/gpu/drm/msm/disp/dpu1/dpu_crtc.h           |    9 +-
>>  drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.c        |  242 +---
>>  drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.h        |    7 -
>>  drivers/gpu/drm/msm/disp/dpu1/dpu_encoder_phys.h   |    1 -
>>  drivers/gpu/drm/msm/disp/dpu1/dpu_hw_top.c         |   20 +-
>>  drivers/gpu/drm/msm/disp/dpu1/dpu_hw_top.h         |    3 -
>>  drivers/gpu/drm/msm/dpu_dbg.c                      |   27 -
>>  drivers/gpu/drm/msm/dpu_dbg.h                      |   10 -
>>  drivers/gpu/drm/msm/dpu_power_handle.c             |   73 +-
>>  drivers/gpu/drm/msm/dpu_power_handle.h             |    4 -
>>  drivers/gpu/drm/msm/dpu_rsc.c                      | 1367 
>> --------------------
>>  drivers/gpu/drm/msm/dpu_rsc_hw.c                   |  818 
>> ------------
>>  drivers/gpu/drm/msm/dpu_rsc_priv.h                 |  191 ---
>>  include/linux/dpu_rsc.h                            |  302 -----
>>  18 files changed, 42 insertions(+), 3278 deletions(-)
>>  delete mode 100644 
>> Documentation/devicetree/bindings/display/msm/dpu-rsc.txt
>>  delete mode 100644 drivers/gpu/drm/msm/dpu_rsc.c
>>  delete mode 100644 drivers/gpu/drm/msm/dpu_rsc_hw.c
>>  delete mode 100644 drivers/gpu/drm/msm/dpu_rsc_priv.h
>>  delete mode 100644 include/linux/dpu_rsc.h
>> 
>> --
>> The Qualcomm Innovation Center, Inc. is a member of the Code Aurora 
>> Forum,
>> a Linux Foundation Collaborative Project
>> 
>> _______________________________________________
>> dri-devel mailing list
>> dri-devel@lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/dri-devel
_______________________________________________
Freedreno mailing list
Freedreno@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/freedreno

  parent reply	other threads:[~2018-04-04 11:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-04  9:04 [DPU PATCH v2 0/2] Remove DPU RSC support Rajesh Yadav
     [not found] ` <1522832680-24490-1-git-send-email-ryadav-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2018-04-04 10:26   ` Daniel Vetter
     [not found]     ` <20180404102633.GG3881-dv86pmgwkMBes7Z6vYuT8azUEOm+Xw19@public.gmane.org>
2018-04-04 11:23       ` ryadav-sgV2jX0FEOL9JmXXK+q4OQ [this message]
     [not found]         ` <9b96938a6c783fd00e55cc767592ec7e-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2018-04-04 12:19           ` Daniel Vetter
     [not found]             ` <20180404121938.GM3881-dv86pmgwkMBes7Z6vYuT8azUEOm+Xw19@public.gmane.org>
2018-04-05  4:45               ` ryadav-sgV2jX0FEOL9JmXXK+q4OQ
2018-04-04 20:21 ` Sean Paul
2018-04-05  4:42   ` ryadav-sgV2jX0FEOL9JmXXK+q4OQ

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=9b96938a6c783fd00e55cc767592ec7e@codeaurora.org \
    --to=ryadav-sgv2jx0feol9jmxxk+q4oq@public.gmane.org \
    --cc=daniel-/w4YWyX8dFk@public.gmane.org \
    --cc=daniel.vetter-/w4YWyX8dFk@public.gmane.org \
    --cc=dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    --cc=freedreno-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    --cc=hoegsberg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org \
    --cc=linux-arm-msm-u79uwXL29TY76Z2rM5mHXA@public.gmane.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