public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: "Romli, Khairul Anuar" <khairul.anuar.romli@altera.com>
Cc: Dinh Nguyen <dinguyen@kernel.org>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	"Rao, Mahesh" <mahesh.rao@altera.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"Ng, Adrian Ho Yin" <adrian.ho.yin.ng@altera.com>,
	"Rabara, Niravkumar Laxmidas" <nirav.rabara@altera.com>
Subject: Re: [PATCH v3 1/2] dt-bindings: firmware: svc: Add IOMMU support for Agilex5
Date: Tue, 4 Nov 2025 15:33:36 +0100	[thread overview]
Message-ID: <4e4d89c8-4a59-445b-ac2c-2d3992190e99@kernel.org> (raw)
In-Reply-To: <fc68b68a-586c-4af6-ae59-85b79d1d8002@altera.com>

On 04/11/2025 12:14, Romli, Khairul Anuar wrote:
> On 4/11/2025 5:48 pm, Krzysztof Kozlowski wrote:
>> On Tue, Nov 04, 2025 at 07:39:27AM +0800, Khairul Anuar Romli wrote:
>>> In Agilex5, the TBU (Translation Buffer Unit) can now operate in non-secure
>>> mode, enabling Linux to utilize it through the IOMMU framework. This allows
>>> improved memory management capabilities in non-secure environments. With
>>> Agilex5 lifting this restriction, we are now extending the device tree
>>> bindings to support IOMMU for the Agilex5 SVC.
>>>
>>> Signed-off-by: Khairul Anuar Romli <khairul.anuar.romli@altera.com>
>>> Reviewed-by: Adrian Ng Ho Yin <adrianhoyin.ng@altera.com>
>>> Reviewed-by: Niravkumar L Rabara <niravkumarlaxmidas.rabara@altera.com>
>>
>> Two reviews but...
>>
>>>   
>>> -required:
>>> -  - compatible
>>> -  - method
>>> -  - memory-region
>>> +allOf:
>>> +  - required:
>>> +      - compatible
>>> +      - method
>>> +      - memory-region
>>
>> ... none told you this is not the correct syntax / style?
>>
>> Were these reviews really happening? What exactly was reviewed here?
>>
>> Best regards,
>> Krzysztof
>>
> 
> The peer review was on the property and compatible added in this patch.
> I was at fault for not emphasize to check on the syntax / style for the 
> logical changes.

Rather the reviewers gave you just simple acks without doing their job.
That's a 10 liner patch...

Feels like just to tick gerrit or satisfy internal procedures.

If internal reviewers give you such "okay" marks, without adhering to
reviewers statement of oversight, you can freely ignore them and instead
educate them to provide full review on the mailing list.

> 
> I refers to 
> Documentation/devicetree/bindings/phy/qcom,sc8280xp-qmp-usb3-uni-phy.yaml 
> and the changes could be as follows:
> 
> required:
>    - compatible
>    - method
>    - memory-region
> +allOf:
> +  - if:
> +      properties:
> +        compatible:
> +          const: intel,agilex5-svc
> +    then:
> +      required:
> +        - iommus
> 
> Do I need to re-specify the rest of the compatible property other than 
> intel,agilex5-svc and their required properties under the allOf block?
> 
> My objective is to specify that iommus only for intel,agilex5-svc but 
> not the rest of devices.
It all depends whether other devices also use IOMMU.

Best regards,
Krzysztof

  reply	other threads:[~2025-11-04 14:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-03 23:39 [PATCH v3 0/2] Enable Service layer driver for Agilex5 Khairul Anuar Romli
2025-11-03 23:39 ` [PATCH v3 1/2] dt-bindings: firmware: svc: Add IOMMU support " Khairul Anuar Romli
2025-11-04  9:48   ` Krzysztof Kozlowski
2025-11-04 11:14     ` Romli, Khairul Anuar
2025-11-04 14:33       ` Krzysztof Kozlowski [this message]
2025-11-05  1:40   ` Romli, Khairul Anuar
2025-11-03 23:39 ` [PATCH v3 2/2] arm64: dts: intel: Add Agilex5 SVC node with memory region Khairul Anuar Romli

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=4e4d89c8-4a59-445b-ac2c-2d3992190e99@kernel.org \
    --to=krzk@kernel.org \
    --cc=adrian.ho.yin.ng@altera.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dinguyen@kernel.org \
    --cc=khairul.anuar.romli@altera.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mahesh.rao@altera.com \
    --cc=nirav.rabara@altera.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