All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Andy Gross <agross@kernel.org>, Rob Herring <robh+dt@kernel.org>,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 3/7] arm64: dts: qcom: qrb5165-rb5: add gpu/zap-shader node
Date: Wed, 2 Dec 2020 16:38:00 -0600	[thread overview]
Message-ID: <X8gXSEeBxFHAPmZe@builder.lan> (raw)
In-Reply-To: <20201127095548.128217-3-dmitry.baryshkov@linaro.org>

On Fri 27 Nov 03:55 CST 2020, Dmitry Baryshkov wrote:

> Add firmware configuration for Adreno zap shader on qrb5165-rb5.
> 
> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
> ---
>  arch/arm64/boot/dts/qcom/qrb5165-rb5.dts | 7 +++++++
>  1 file changed, 7 insertions(+)
> 
> diff --git a/arch/arm64/boot/dts/qcom/qrb5165-rb5.dts b/arch/arm64/boot/dts/qcom/qrb5165-rb5.dts
> index 9c5135585ec9..d1f6cadca35a 100644
> --- a/arch/arm64/boot/dts/qcom/qrb5165-rb5.dts
> +++ b/arch/arm64/boot/dts/qcom/qrb5165-rb5.dts
> @@ -423,6 +423,13 @@ &dsi0_phy {
>  	vdds-supply = <&vreg_l5a_0p88>;
>  };
>  
> +&gpu {
> +	zap-shader {
> +		memory-region = <&gpu_mem>;
> +		firmware-name = "qcom/a650_zap.mdt";

The zap shader is unfortunately signed with a vendor specific key. So
can we please move the test signed file into qcom/sm8250/?

And to avoid pushing all these scattered files to linux-firmware, can
you please run pil-squasher [1] on it and use the a650_zap.mbn?

[1] https://github.com/andersson/pil-squasher

Regards,
Bjorn

> +	};
> +};
> +
>  /* LS-I2C0 */
>  &i2c4 {
>  	status = "okay";
> -- 
> 2.29.2
> 

  reply	other threads:[~2020-12-02 22:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-27  9:55 [PATCH 1/7] arm64: dts: qcom: sm8250.dtsi: add display system nodes Dmitry Baryshkov
2020-11-27  9:55 ` [PATCH 2/7] arm64: dts: qrb5165-rb5: add mdss/mdp/dsi nodes Dmitry Baryshkov
2020-11-27  9:55 ` [PATCH 3/7] arm64: dts: qcom: qrb5165-rb5: add gpu/zap-shader node Dmitry Baryshkov
2020-12-02 22:38   ` Bjorn Andersson [this message]
2020-11-27  9:55 ` [PATCH 4/7] arm64: dts: qcom: sm8250-mtp: " Dmitry Baryshkov
2020-11-27  9:55 ` [PATCH 5/7] arm64: dts: qcom: qrb5165-rb5: correct vdc_3v3 regulator Dmitry Baryshkov
2020-11-27  9:55 ` [PATCH 6/7] arm64: dts: qcom: qrb5165-rb5: add lt9611 HDMI bridge Dmitry Baryshkov
2020-11-27  9:55 ` [PATCH 7/7] arm64: dts: qcom: sm8250: power up dispcc on sm8250 by MMCX regulator Dmitry Baryshkov

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=X8gXSEeBxFHAPmZe@builder.lan \
    --to=bjorn.andersson@linaro.org \
    --cc=agross@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.