Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Sean Paul <seanpaul@chromium.org>
To: Rajesh Yadav <ryadav@codeaurora.org>
Cc: linux-arm-msm@vger.kernel.org, dri-devel@lists.freedesktop.org,
	hoegsberg@chromium.org, freedreno@lists.freedesktop.org
Subject: Re: [DPU PATCH v2 0/2] Remove DPU RSC support
Date: Wed, 4 Apr 2018 16:21:19 -0400	[thread overview]
Message-ID: <20180404202119.GF73214@art_vandelay> (raw)
In-Reply-To: <1522832680-24490-1-git-send-email-ryadav@codeaurora.org>

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.
> 
> 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

Hi Rajesh,
Unrelated to this change, but I've noticed the threading seems off on the patch
sets you're sending. Are you sending the emails one-by-one, or specifying
--no-thread in git send-email?

Sean

> 
> 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
> 

-- 
Sean Paul, Software Engineer, Google / Chromium OS
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2018-04-04 20:21 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
     [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 [this message]
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=20180404202119.GF73214@art_vandelay \
    --to=seanpaul@chromium.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=freedreno@lists.freedesktop.org \
    --cc=hoegsberg@chromium.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=ryadav@codeaurora.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