public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Sumit Garg <sumit.garg@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	andersson@kernel.org, konradybcio@kernel.org, robh@kernel.org,
	krzk+dt@kernel.org, conor+dt@kernel.org,
	akhilpo@oss.qualcomm.com, vikash.garodia@oss.qualcomm.com,
	dikshita.agarwal@oss.qualcomm.com, robin.clark@oss.qualcomm.com,
	lumag@kernel.org, loic.poulain@oss.qualcomm.com,
	jorge.ramirez@oss.qualcomm.com, linux-kernel@vger.kernel.org,
	Sumit Garg <sumit.garg@oss.qualcomm.com>
Subject: Re: [PATCH v2 1/3] dt-bindings: display: msm: qcm2290-mdss: Fix iommus property
Date: Tue, 20 Jan 2026 13:30:13 +0100	[thread overview]
Message-ID: <bdc8011b-6501-43e5-815b-a981df665e03@kernel.org> (raw)
In-Reply-To: <aW9yCK0rPjRcqplk@sumit-xelite>

On 20/01/2026 13:16, Sumit Garg wrote:
> 
>>
>>>
>>> There has been ongoing disscusion related to how stream ID associated
>>> with different translation context can be represented in DT here [1].
>>> With that only the secure bank stream IDs can be properly represented.
>>>
>>> Here I just followed the approach taken by Adreno GPU bindings for the
>>> iommus property [2].
>>>
>>> [2] Documentation/devicetree/bindings/display/msm/gpu.yaml +82
>>
>> Such justifications are pointless. What about commit msg which explains
>> why this was added? What about entire public discussion happening with
>> this patch? What about all previous revisions of that patch and
>> discussions leading to this piece of code? So you just found few lines
>> of code, ignored entire background and any other arguments, and copied
>> it here.
> 
> Looks like you are mixing other patch-set with this one.

How different? You found some old code and use it as argument that you
can do the same:

"Here I just followed the approach taken by Adreno GPU bindings for the"

so how I am mixing patchsets in my response above?


> 
>>
>> That's the approach - I found a piece of some buggy code, so I can do
>> the same.
>>
>> Again, we discussed it 2-3 months ago for the same patch and I gave
>> exactly same reason why this patch is incomplete.
> 
> Sorry you are just mixing different discussions here. I am trying to fix

How am I mixing? Exactly same approach was posted for other SoC. I gave
same comments. Same comments apply here.

> the SMMU stream IDs for Agatti SoC which listed secure bank stream IDs
> incorrectly.

You explain what you did, but you did not explain why or how I mixed
anything.

> 
> And this is the first version of this patch only for DT bindings fix for
> Agatti, there are no prior discussions I had on this aspect upstream.

I did not say you had discussions before. I said exactly same problems
were being solved and I give here and there exactly the same feedback.

Best regards,
Krzysztof

  reply	other threads:[~2026-01-20 12:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-16  6:20 [PATCH v2 0/3] arm64: dts: qcom: agatti: Fix IOMMU DT properties Sumit Garg
2026-01-16  6:20 ` [PATCH v2 1/3] dt-bindings: display: msm: qcm2290-mdss: Fix iommus property Sumit Garg
2026-01-16  8:46   ` Krzysztof Kozlowski
2026-01-16 12:53     ` Sumit Garg
2026-01-16 13:15       ` Krzysztof Kozlowski
2026-01-20 12:16         ` Sumit Garg
2026-01-20 12:30           ` Krzysztof Kozlowski [this message]
2026-01-21  7:59             ` Sumit Garg
2026-01-16  6:20 ` [PATCH v2 2/3] media: dt-bindings: venus: " Sumit Garg
2026-01-16  8:47   ` Krzysztof Kozlowski
2026-01-16  6:20 ` [PATCH v2 3/3] arm64: dts: qcom: agatti: Fix IOMMU DT properties Sumit Garg
2026-01-16  8:40   ` 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=bdc8011b-6501-43e5-815b-a981df665e03@kernel.org \
    --to=krzk@kernel.org \
    --cc=akhilpo@oss.qualcomm.com \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dikshita.agarwal@oss.qualcomm.com \
    --cc=jorge.ramirez@oss.qualcomm.com \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=loic.poulain@oss.qualcomm.com \
    --cc=lumag@kernel.org \
    --cc=robh@kernel.org \
    --cc=robin.clark@oss.qualcomm.com \
    --cc=sumit.garg@kernel.org \
    --cc=sumit.garg@oss.qualcomm.com \
    --cc=vikash.garodia@oss.qualcomm.com \
    /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