public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jordan Crouse <jcrouse@codeaurora.org>
To: georgi.djakov@linaro.org
Cc: linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-arm-msm@vger.kernel.org, dri-devel@lists.freedesktop.org,
	freedreno@lists.freedesktop.org
Subject: [PATCH 0/1] drm/msm/a6xx: Add interconnect support
Date: Wed, 28 Nov 2018 11:29:28 -0700	[thread overview]
Message-ID: <20181128182929.19925-1-jcrouse@codeaurora.org> (raw)

I heard at LPC that there was some confusion that the OPP bindings [1]
were needed to land interconnect support. They aren't.

There is a two step process for the SDM845 GPU. First we need a vote (any vote)
because the default bus settings are way too bad for any reasonable
performance.

The next step after that would be to scale the bus request based on the
frequency in order to save power. For that we *do* need a solution but that
can be calmly discussed separately.

This patch accommodates the first step. It cranks the bus to max for GPU
activity and turns it off when the GPU goes to sleep. Hopefully this can
alleviate the confusion and help interconnect land that much quicker.
After that, we can calmly re-introduce the OPP discussion.

This patch depends on interconnect support [2].

[1] https://patchwork.kernel.org/patch/10577303/
[2] https://patchwork.kernel.org/patch/10701287/

Jordan Crouse (1):
  drm/msm/a6xx: Add support for an interconnect path

 drivers/gpu/drm/msm/adreno/a6xx_gmu.c   | 20 ++++++++++++++++++++
 drivers/gpu/drm/msm/adreno/adreno_gpu.c |  9 +++++++++
 drivers/gpu/drm/msm/msm_gpu.h           |  3 +++
 3 files changed, 32 insertions(+)

-- 
2.18.0


             reply	other threads:[~2018-11-28 18:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-28 18:29 Jordan Crouse [this message]
2018-11-28 18:29 ` [PATCH 1/1] drm/msm/a6xx: Add support for an interconnect path Jordan Crouse
2018-11-28 19:09   ` [Freedreno] " Rob Clark

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=20181128182929.19925-1-jcrouse@codeaurora.org \
    --to=jcrouse@codeaurora.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=freedreno@lists.freedesktop.org \
    --cc=georgi.djakov@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox