devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Gross <agross@kernel.org>
To: Doug Anderson <dianders@chromium.org>
Cc: Rob Clark <robdclark@gmail.com>,
	linux-arm-msm <linux-arm-msm@vger.kernel.org>,
	Rob Clark <robdclark@chromium.org>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" 
	<devicetree@vger.kernel.org>,
	open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arm64: dts: qcom: sdm845-cheza: delete zap-shader
Date: Sun, 27 Oct 2019 00:40:32 -0500	[thread overview]
Message-ID: <20191027054032.GI5514@hector.lan> (raw)
In-Reply-To: <CAD=FV=VqNpttUXQZ7KUd1ahsDrxST9BVoy9NXCM+xhQb9aRb1A@mail.gmail.com>

On Fri, Oct 25, 2019 at 02:28:22PM -0700, Doug Anderson wrote:
> Hi,
> 
> On Fri, Oct 25, 2019 at 2:23 PM Rob Clark <robdclark@gmail.com> wrote:
> >
> > From: Rob Clark <robdclark@chromium.org>
> >
> > This is unused on cheza.  Delete the node to get ride of the reserved-
> > memory section, and to avoid the driver from attempting to load a zap
> > shader that doesn't exist every time it powers up the GPU.
> >
> > (This also avoids a massive amount of dmesg spam about missing zap fw.)
> 
> optional nit: maybe when this is applied Bjorn / Andy can put in the
> actual error message to make this easier to find if anyone is seeing
> this problem.  Specifically:
> 
>   msm ae00000.mdss: [drm:adreno_request_fw] *ERROR* failed to load
> qcom/a630_zap.mdt: -2
>   adreno 5000000.gpu: [drm:adreno_zap_shader_load] *ERROR* Unable to
> load a630_zap.mdt
> 
> 
> > Signed-off-by: Rob Clark <robdclark@chromium.org>
> > Cc: Douglas Anderson <dianders@chromium.org>
> > ---
> >  arch/arm64/boot/dts/qcom/sdm845-cheza.dtsi | 2 ++
> >  arch/arm64/boot/dts/qcom/sdm845.dtsi       | 2 +-
> >  2 files changed, 3 insertions(+), 1 deletion(-)
> 
> I probably would have put it in two patches (one for sdm845.dtsi and
> one for cheza) but that's more because I'm obsessive-compulsive than
> for any real reason.  ;-)  In any case:
> 
> Fixes: 3fdeaee951aa ("arm64: dts: sdm845: Add zap shader region for GPU")
> Reviewed-by: Douglas Anderson <dianders@chromium.org>
> Tested-by: Douglas Anderson <dianders@chromium.org>

Applied this patch and added in the dmesg error messages.

Andy

      reply	other threads:[~2019-10-27  5:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-25 21:21 [PATCH] arm64: dts: qcom: sdm845-cheza: delete zap-shader Rob Clark
2019-10-25 21:28 ` Doug Anderson
2019-10-27  5:40   ` Andy Gross [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=20191027054032.GI5514@hector.lan \
    --to=agross@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dianders@chromium.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=robdclark@chromium.org \
    --cc=robdclark@gmail.com \
    --cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).