Devicetree
 help / color / mirror / Atom feed
From: Frank Li <Frank.li@nxp.com>
To: adrianhoyin.ng@altera.com
Cc: alexandre.belloni@bootlin.com, wsa+renesas@sang-engineering.com,
	robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
	dinguyen@kernel.org, linux-i3c@lists.infradead.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] dt-bindings: i3c: Add snps,dev-nack-retry-cnt property to Synopsys I3C master
Date: Tue, 4 Nov 2025 14:25:45 -0500	[thread overview]
Message-ID: <aQpTOXIPzHI5q7Y7@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <9c16c22f67858e24fe7c3a7184537cb5c2c1a85c.1762245890.git.adrianhoyin.ng@altera.com>

On Tue, Nov 04, 2025 at 04:51:08PM +0800, adrianhoyin.ng@altera.com wrote:
> From: Adrian Ng Ho Yin <adrianhoyin.ng@altera.com>
>
> Add a new optional property 'snps,dev-nack-retry-cnt' to the Synopsys
> DesignWare I3C master device tree binding. This property allows
> configuration of the Device NACK Retry count, which determines how many
> times the controller retries a transaction when a slave device responds
> with NACK.

Look like it is software property, why need put in dt?

Frank

>
> Valid values range from 0 to 3, with a default of 0
>
> Signed-off-by: Adrian Ng Ho Yin <adrianhoyin.ng@altera.com>
> ---
>  .../devicetree/bindings/i3c/snps,dw-i3c-master.yaml       | 8 ++++++++
>  1 file changed, 8 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/i3c/snps,dw-i3c-master.yaml b/Documentation/devicetree/bindings/i3c/snps,dw-i3c-master.yaml
> index 5f6467375811..c233be2d4a3c 100644
> --- a/Documentation/devicetree/bindings/i3c/snps,dw-i3c-master.yaml
> +++ b/Documentation/devicetree/bindings/i3c/snps,dw-i3c-master.yaml
> @@ -37,6 +37,14 @@ properties:
>    power-domains:
>      maxItems: 1
>
> +  snps,dev-nack-retry-cnt:
> +    description: |
> +      This field is used to set the Device NACK Retry count for the
> +      particular slave device.
> +    $ref: /schemas/types.yaml#/definitions/uint32
> +    default: 0
> +    maximum: 3
> +
>  required:
>    - compatible
>    - reg
> --
> 2.49.GIT
>

  parent reply	other threads:[~2025-11-04 19:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-04  8:51 [PATCH 0/4] i3c: dw: Add support for Device NACK Retry count adrianhoyin.ng
2025-11-04  8:51 ` [PATCH 1/4] dt-bindings: i3c: Add snps,dev-nack-retry-cnt property to Synopsys I3C master adrianhoyin.ng
2025-11-04  9:02   ` Krzysztof Kozlowski
2025-11-04 19:25   ` Frank Li [this message]
2025-11-04  8:51 ` [PATCH 2/4] arm64: dts: intel: agilex5: Add snps,dev-nack-retry-cnt property for I3C controllers adrianhoyin.ng
2025-11-04  8:51 ` [PATCH 3/4] i3c: dw: Add support for Device NACK Retry count adrianhoyin.ng
2025-11-04 19:28   ` Frank Li
2025-11-04  8:51 ` [PATCH 4/4] i3c: dw: Preserve DAT entry bits when restoring addresses adrianhoyin.ng
2025-11-06 22:10 ` [PATCH 0/4] i3c: dw: Add support for Device NACK Retry count Alexandre Belloni

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=aQpTOXIPzHI5q7Y7@lizhi-Precision-Tower-5810 \
    --to=frank.li@nxp.com \
    --cc=adrianhoyin.ng@altera.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dinguyen@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-i3c@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=wsa+renesas@sang-engineering.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