Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Akhil P Oommen <quic_akhilpo@quicinc.com>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Rob Clark <robdclark@gmail.com>, Sean Paul <sean@poorly.run>,
	"Konrad Dybcio" <konradybcio@kernel.org>,
	Abhinav Kumar <quic_abhinavk@quicinc.com>,
	Marijn Suijten <marijn.suijten@somainline.org>,
	David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Maxime Ripard <mripard@kernel.org>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Connor Abbott <cwabbott0@gmail.com>,
	<linux-arm-msm@vger.kernel.org>,
	<dri-devel@lists.freedesktop.org>,
	<freedreno@lists.freedesktop.org>, <linux-kernel@vger.kernel.org>,
	<devicetree@vger.kernel.org>,
	Puranam V G Tejaswi <quic_pvgtejas@quicinc.com>
Subject: Re: [PATCH v3 2/2] arm64: dts: qcom: sa8775p-ride: Enable Adreno 663 GPU
Date: Thu, 13 Feb 2025 22:21:52 +0530	[thread overview]
Message-ID: <0b659aed-4b4a-45d5-a388-ebea22d17bc4@quicinc.com> (raw)
In-Reply-To: <fixmfluomzrdnoyztkd57gjpoqzutlv3m4es5jc7fclhpbauby@7u3ddi6dz4f7>

On 2/12/2025 4:26 PM, Dmitry Baryshkov wrote:
> On Wed, Feb 12, 2025 at 12:48:01PM +0530, Akhil P Oommen wrote:
>> On 2/12/2025 5:30 AM, Dmitry Baryshkov wrote:
>>> On Tue, Feb 11, 2025 at 06:41:39PM +0530, Akhil P Oommen wrote:
>>>> On 2/9/2025 9:59 PM, Dmitry Baryshkov wrote:
>>>>> On Wed, Nov 13, 2024 at 02:18:43AM +0530, Akhil P Oommen wrote:
>>>>>> On 10/30/2024 12:32 PM, Akhil P Oommen wrote:
>>>>>>> From: Puranam V G Tejaswi <quic_pvgtejas@quicinc.com>
>>>>>>>
>>>>>>> Enable GPU for sa8775p-ride platform and provide path for zap
>>>>>>> shader.
>>>>>>>
>>>>>>> Signed-off-by: Puranam V G Tejaswi <quic_pvgtejas@quicinc.com>
>>>>>>> Signed-off-by: Akhil P Oommen <quic_akhilpo@quicinc.com>
>>>>>>> Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
>>>>>>> ---
>>>>>>>  arch/arm64/boot/dts/qcom/sa8775p-ride.dtsi | 8 ++++++++
>>>>>>>  1 file changed, 8 insertions(+)
>>>>>>>
>>>>>>> diff --git a/arch/arm64/boot/dts/qcom/sa8775p-ride.dtsi b/arch/arm64/boot/dts/qcom/sa8775p-ride.dtsi
>>>>>>> index 0c1b21def4b6..4901163df8f3 100644
>>>>>>> --- a/arch/arm64/boot/dts/qcom/sa8775p-ride.dtsi
>>>>>>> +++ b/arch/arm64/boot/dts/qcom/sa8775p-ride.dtsi
>>>>>>> @@ -407,6 +407,14 @@ queue3 {
>>>>>>>  	};
>>>>>>>  };
>>>>>>>  
>>>>>>> +&gpu {
>>>>>>> +	status = "okay";
>>>>>>> +};
>>>>>>> +
>>>>>>> +&gpu_zap_shader {
>>>>>>> +	firmware-name = "qcom/sa8775p/a663_zap.mbn";
>>>>>>> +};
>>>>>>> +
>>>>>>>  &i2c11 {
>>>>>>>  	clock-frequency = <400000>;
>>>>>>>  	pinctrl-0 = <&qup_i2c11_default>;
>>>>>>>
>>>>>>
>>>>>> Bjorn,
>>>>>>
>>>>>> Please ignore this patch for now. This is probably not the right
>>>>>> platform dtsi file where gpu should be enabled. I am discussing about
>>>>>> this internally. Will send a revision or a new patch based on the
>>>>>> conclusion.
>>>>>
>>>>> Akhil, any updates on this?
>>>>>
>>>>
>>>> I am still waiting for the discussion about QCS9075 board dts files [1]
>>>> to conclude.
>>>>
>>>> [1]
>>>> https://lore.kernel.org/lkml/Z3eMxl1Af8TOAQW%2F@hu-wasimn-hyd.qualcomm.com/T/
>>>
>>> Why? We currently have several boards supported. We can enable GPU on
>>> those as your patches are pretty fine. Then we can land Wasim's patches.
>>> Not to mention that the discussion seems to be dead, last message was
>>> sent almost a month ago.
>>>
>>
>> sa8775p is an automotive-grade chipset which has a pretty different
>> non-HLOS firmware. One of the major difference is that it has a SAFETY
>> monitoring system (using SAIL IP block) which monitors different
>> parameters like GPU frequency for eg and it takes control of the entire
>> system when it detects an anomaly. That means we cannot use GPU DCVS,
>> passive thermal mitigation etc there.
>>
>> QCS9075 uses the same SoC but has different NHLOS firmwares that has
>> SAIL disabled to make it behave like our regular chipsets. I am aware of
>> only QCS9075 boards' GPU spec at the moment. I don't know the complete
>> details of the impact of SAIL/SAFE features on GPU and other specs yet,
>> so I can't disturb sa8775p-ride/qcs9100-ride boards.
> 
> Ack, thanks for the explanation. Indeed, it would be interesting to
> understand how that's working together. Do SA8775P / QCS9100 use a
> different GMU firmware?

We don't have a linux compatible GMU firmware for SA8775P yet. But it
will be a common gmu fw between all three platforms.

-Akhil.

> 
>> I can see that Wazim is still discussing about board DTS internally.
>> Hopefully he will send out another revision of his series soon.
> 
> The discussion stopped a month ago. 
> 


      reply	other threads:[~2025-02-13 16:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-30  7:02 [PATCH v3 0/2] DRM/MSM: Support for Adreno 663 GPU Akhil P Oommen
2024-10-30  7:02 ` [PATCH v3 1/2] arm64: dts: qcom: sa8775p: Add gpu and gmu nodes Akhil P Oommen
2024-10-31 20:30   ` Konrad Dybcio
2024-11-01 14:46     ` Akhil P Oommen
2024-11-12 20:57   ` Akhil P Oommen
2024-10-30  7:02 ` [PATCH v3 2/2] arm64: dts: qcom: sa8775p-ride: Enable Adreno 663 GPU Akhil P Oommen
2024-10-31 20:30   ` Konrad Dybcio
2024-11-12 20:48   ` Akhil P Oommen
2025-02-09 16:29     ` Dmitry Baryshkov
2025-02-11 13:11       ` Akhil P Oommen
2025-02-12  0:00         ` Dmitry Baryshkov
2025-02-12  7:18           ` Akhil P Oommen
2025-02-12 10:56             ` Dmitry Baryshkov
2025-02-13 16:51               ` Akhil P Oommen [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=0b659aed-4b4a-45d5-a388-ebea22d17bc4@quicinc.com \
    --to=quic_akhilpo@quicinc.com \
    --cc=airlied@gmail.com \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=cwabbott0@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=freedreno@lists.freedesktop.org \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=marijn.suijten@somainline.org \
    --cc=mripard@kernel.org \
    --cc=quic_abhinavk@quicinc.com \
    --cc=quic_pvgtejas@quicinc.com \
    --cc=robdclark@gmail.com \
    --cc=robh@kernel.org \
    --cc=sean@poorly.run \
    --cc=simona@ffwll.ch \
    --cc=tzimmermann@suse.de \
    /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