Devicetree
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Xing Loong <xing.xl.loong@gmail.com>, Jens Wiklander <jenswi@kernel.org>
Cc: Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>, Rob Herring <robh@kernel.org>,
	Sumit Garg <sumit.garg@kernel.org>,
	op-tee@lists.trustedfirmware.org, devicetree@vger.kernel.org,
	linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/3] dt-bindings: firmware: add mbedtee,tee binding
Date: Thu, 2 Jul 2026 17:27:27 +0200	[thread overview]
Message-ID: <f5f6aa5f-8c28-43eb-b254-17816f976f19@kernel.org> (raw)
In-Reply-To: <20260702151115.544016-3-xing.xl.loong@gmail.com>

On 02/07/2026 17:11, Xing Loong wrote:
> +
> +  On RISC-V the TEE signals the REE via IMSIC MSI; the REE submits
> +  commands via r2t-ring that the TEE polls. No REE-to-TEE interrupt
> +  is used. No SBI ecall is involved.
> +
> +properties:
> +  compatible:
> +    const: mbedtee,tee


No, you need to respond to feedback instead of sending the same code
called v2. You received comments for a reason. Sending v2 now hides all
this comments and people might think discussion is resolved. This is
very bad practice.

Also,
Do not attach (thread) your patchsets to some other threads (unrelated
or older versions). This buries them deep in the mailbox and might
interfere with applying entire sets. See also:
https://elixir.bootlin.com/linux/v6.16-rc2/source/Documentation/process/submitting-patches.rst#L830

...

> +
> +examples:
> +  - |
> +    /* ARM TrustZone (SMC) */
> +    #include <dt-bindings/interrupt-controller/arm-gic.h>
> +
> +    firmware {
> +      mbedtee {
> +        compatible = "mbedtee,tee";
> +        interrupts = <GIC_SPI 72 IRQ_TYPE_EDGE_RISING>;
> +        memory-region = <&mbedtee_t2r_ring>, <&mbedtee_t2r_shm>;
> +        memory-region-names = "t2r-ring", "t2r-shm";
> +      };
> +    };
> +
> +    /* memory-region phandle targets */
> +    mbedtee_t2r_ring: t2r-ring {};
> +    mbedtee_t2r_shm: t2r-shm {};

I asked you to drop all these irrelevant entries.

> +
> +  - |
> +    /* RISC-V IMSIC (ring-buffer polling REE->TEE, MSI TEE->REE) */
> +
> +    firmware {
> +      mbedtee {
> +        compatible = "mbedtee,tee";
> +        msi-parent = <&imsic>;
> +        memory-region = <&rv_t2r_ring>, <&rv_t2r_shm>,
> +                        <&rv_r2t_ring>;
> +        memory-region-names = "t2r-ring", "t2r-shm",
> +                              "r2t-ring";
> +      };
> +    };
> +
> +    /* msi-parent phandle target */
> +    imsic: imsic {
> +      msi-controller;
> +      #msi-cells = <0>;
> +    };

Also drop.

> +
> +    /* memory-region phandle targets */
> +    rv_t2r_ring: t2r-ring {};
> +    rv_t2r_shm: t2r-shm {};
> +    rv_r2t_ring: r2t-ring {};

Also not relevant.

I will not continue the review. Please go back to v1 and continue the
discussion.

I consider this version NAKed.


Best regards,
Krzysztof

  parent reply	other threads:[~2026-07-02 15:27 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-01 13:25 [PATCH 0/3] tee: add MbedTEE driver Xing Loong
2026-07-01 13:25 ` [PATCH 1/3] dt-bindings: vendor-prefixes: add mbedtee Xing Loong
2026-07-01 13:25 ` [PATCH 2/3] dt-bindings: firmware: add mbedtee,rpc binding Xing Loong
2026-07-01 13:32   ` sashiko-bot
2026-07-01 14:05   ` Krzysztof Kozlowski
2026-07-01 16:39   ` Rob Herring (Arm)
2026-07-01 13:25 ` [PATCH 3/3] tee: add MbedTEE driver Xing Loong
2026-07-01 13:42   ` sashiko-bot
2026-07-02 15:11 ` [PATCH v2 0/3] " Xing Loong
2026-07-02 15:11   ` [PATCH v2 1/3] dt-bindings: vendor-prefixes: add mbedtee Xing Loong
2026-07-02 15:11   ` [PATCH v2 2/3] dt-bindings: firmware: add mbedtee,tee binding Xing Loong
2026-07-02 15:21     ` sashiko-bot
2026-07-02 15:27     ` Krzysztof Kozlowski [this message]
2026-07-02 15:11   ` [PATCH v2 3/3] tee: add MbedTEE driver Xing Loong
2026-07-02 15:32     ` sashiko-bot

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=f5f6aa5f-8c28-43eb-b254-17816f976f19@kernel.org \
    --to=krzk@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jenswi@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=op-tee@lists.trustedfirmware.org \
    --cc=robh@kernel.org \
    --cc=sumit.garg@kernel.org \
    --cc=xing.xl.loong@gmail.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