devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Akhil P Oommen <quic_akhilpo@quicinc.com>
Cc: freedreno <freedreno@lists.freedesktop.org>,
	dri-devel@lists.freedesktop.org, linux-arm-msm@vger.kernel.org,
	Rob Clark <robdclark@gmail.com>,
	Bjorn Andersson <andersson@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Konrad Dybcio <konrad.dybcio@linaro.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Rob Herring <robh@kernel.org>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 3/3] arm64: dts: qcom: x1e80100: Add gpu support
Date: Sun, 23 Jun 2024 22:05:51 +0200	[thread overview]
Message-ID: <bbd15b19-fd16-428e-ad6d-0ba7eb00ca9f@kernel.org> (raw)
In-Reply-To: <20240623151630.bskqwqhp25mu3yuf@hu-akhilpo-hyd.qualcomm.com>

On 23/06/2024 17:16, Akhil P Oommen wrote:
> On Sun, Jun 23, 2024 at 02:53:17PM +0200, Krzysztof Kozlowski wrote:
>> On 23/06/2024 14:28, Akhil P Oommen wrote:
>>> On Sun, Jun 23, 2024 at 01:17:16PM +0200, Krzysztof Kozlowski wrote:
>>>> On 23/06/2024 13:06, Akhil P Oommen wrote:
>>>>> Add the necessary dt nodes for gpu support in X1E80100.
>>>>>
>>>>> Signed-off-by: Akhil P Oommen <quic_akhilpo@quicinc.com>
>>>>> ---
>>>>> +		gmu: gmu@3d6a000 {
>>>>> +			compatible = "qcom,adreno-gmu-x185.1", "qcom,adreno-gmu";
>>>>> +			reg = <0x0 0x03d50000 0x0 0x10000>,
>>>>> +			      <0x0 0x03d6a000 0x0 0x35000>,
>>>>> +			      <0x0 0x0b280000 0x0 0x10000>;
>>>>> +			reg-names =  "rscc", "gmu", "gmu_pdc";
>>>>
>>>> Really, please start testing your patches. Your internal instructions
>>>> tells you to do that, so please follow it carefully. Don't use the
>>>> community as the tool, because you do not want to run checks and
>>>> investigate results.
>>>
>>> This was obviously tested before (and retested now) and everything works. I am
>>> confused about what you meant. Could you please elaborate a bit? The device
>>> and the compilation/test setup is new for me, so I am wondering if I
>>> made any silly mistake!
>>
>> Eh, your DTS is not correct, but this could not be pointed out by tests,
>> because the binding does not work. :(
> 
> I reordered both "reg" and "reg-names" arrays based on the address. Not sure if
> that is what we are talking about here. Gpu driver uses platform_get_resource_byname()
> to query mmio resources.
> 
> I will retest dt-bindings and dts checks after picking the patches you
> just posted and report back. Is the schema supposed to enforce strict
> order?

Yes, because the lists are strictly ordered (with exceptions).

Best regards,
Krzysztof


  reply	other threads:[~2024-06-23 20:05 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-23 11:06 [PATCH v1 0/3] Support for Adreno X1-85 GPU Akhil P Oommen
2024-06-23 11:06 ` [PATCH v1 1/3] dt-bindings: display/msm/gmu: Add Adreno X185 GMU Akhil P Oommen
2024-06-23 11:13   ` Krzysztof Kozlowski
2024-06-23 12:40   ` Krzysztof Kozlowski
2024-06-26  7:46     ` Akhil P Oommen
2024-06-23 11:06 ` [PATCH v1 3/3] arm64: dts: qcom: x1e80100: Add gpu support Akhil P Oommen
2024-06-23 11:17   ` Krzysztof Kozlowski
2024-06-23 12:28     ` Akhil P Oommen
2024-06-23 12:53       ` Krzysztof Kozlowski
2024-06-23 15:16         ` Akhil P Oommen
2024-06-23 20:05           ` Krzysztof Kozlowski [this message]
2024-06-23 20:40           ` Bjorn Andersson
2024-06-23 21:01             ` Akhil P Oommen
2024-06-23 21:23   ` Dmitry Baryshkov
2024-06-26 21:00     ` Akhil P Oommen
2024-06-24 13:57   ` Konrad Dybcio
2024-06-26 21:04     ` Akhil P Oommen
2024-06-26 21:39       ` Konrad Dybcio
2024-06-27  7:36   ` kernel test robot
2024-06-27 20:22   ` kernel test robot
2024-06-28 13:44   ` kernel test robot
2024-06-29 10:28   ` kernel test robot
2024-06-23 11:11 ` [PATCH v1 0/3] Support for Adreno X1-85 GPU Krzysztof Kozlowski
2024-06-23 21:24   ` Dmitry Baryshkov
2024-06-24  6:21   ` Akhil P Oommen
2024-06-24 10:21     ` Krzysztof Kozlowski

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=bbd15b19-fd16-428e-ad6d-0ba7eb00ca9f@kernel.org \
    --to=krzk@kernel.org \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=freedreno@lists.freedesktop.org \
    --cc=konrad.dybcio@linaro.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=quic_akhilpo@quicinc.com \
    --cc=robdclark@gmail.com \
    --cc=robh@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).