public inbox for linux-i3c@lists.infradead.org
 help / color / mirror / Atom feed
From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: adrianhoyin.ng@altera.com
Cc: Frank.Li@nxp.com, linux-i3c@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 1/5] i3c: add sysfs entry for Device NACK Retry count
Date: Wed, 10 Dec 2025 17:21:16 +0100	[thread overview]
Message-ID: <202512101621169fc49b8c@mail.local> (raw)
In-Reply-To: <35bb0a3cae4664dc423ef57a1ef3ebcb378bce00.1765177110.git.adrianhoyin.ng@altera.com>

On 08/12/2025 15:11:16+0800, adrianhoyin.ng@altera.com wrote:
> From: Adrian Ng Ho Yin <adrianhoyin.ng@altera.com>
> 
> Document sysfs attribute dev_nack_retry_cnt that controls the number of
> automatic retries performed by the I3C controller when a target device
> returns a NACK
> 
> Signed-off-by: Adrian Ng Ho Yin <adrianhoyin.ng@altera.com>
> Reviewed-by: Frank Li <Frank.Li@nxp.com>
> ---
>  Documentation/ABI/testing/sysfs-bus-i3c | 12 ++++++++++++
>  1 file changed, 12 insertions(+)
> 

Please squash 1/5 and 2/5.

> diff --git a/Documentation/ABI/testing/sysfs-bus-i3c b/Documentation/ABI/testing/sysfs-bus-i3c
> index c812ab180ff4..0b8a0c223f4a 100644
> --- a/Documentation/ABI/testing/sysfs-bus-i3c
> +++ b/Documentation/ABI/testing/sysfs-bus-i3c
> @@ -161,3 +161,15 @@ Contact:	linux-i3c@vger.kernel.org
>  Description:
>  		These directories are just symbolic links to
>  		/sys/bus/i3c/devices/i3c-<bus-id>/<bus-id>-<device-pid>.
> +
> +What:		/sys/bus/i3c/devices/i3c-<bus-id>/<bus-id>-<device-pid>/dev_nack_retry_count
> +KernelVersion:  6.18
> +Contact:	linux-i3c@vger.kernel.org
> +Description:
> +		Expose the dev_nak_retry_count which controls the number of
> +		automatic retries that will be performed by the controller when
> +		the target device returns a NACK response. A value of 0 disables
> +		the automatic retries. A max value of 3 can be configured. Exist
> +		only when I3C constroller supports this retry on nack feature.
> +
> +		Valid values: 0-3
> -- 
> 2.49.GIT
> 

-- 
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

-- 
linux-i3c mailing list
linux-i3c@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-i3c

  reply	other threads:[~2025-12-10 16:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-08  7:11 [PATCH v7 0/5] i3c: dw-i3c: Enable support for dw-i3c controller NACK retry sysfs and DAT restore fix adrianhoyin.ng
2025-12-08  7:11 ` [PATCH v7 1/5] i3c: add sysfs entry for Device NACK Retry count adrianhoyin.ng
2025-12-10 16:21   ` Alexandre Belloni [this message]
2025-12-08  7:11 ` [PATCH v7 2/5] i3c: add sysfs attribute for device NACK retry adrianhoyin.ng
2025-12-08 15:25   ` Frank Li
2025-12-10 16:22   ` Alexandre Belloni
2025-12-08  7:11 ` [PATCH v7 3/5] i3c: dw: Add support for Device NACK Retry configuration adrianhoyin.ng
2025-12-08 15:27   ` Frank Li
2025-12-08  7:11 ` [PATCH v7 4/5] i3c: dw: use FIELD_PREP for device address table macros adrianhoyin.ng
2025-12-08  7:11 ` [PATCH v7 5/5] i3c: dw: Preserve DAT entry bits when restoring addresses adrianhoyin.ng

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=202512101621169fc49b8c@mail.local \
    --to=alexandre.belloni@bootlin.com \
    --cc=Frank.Li@nxp.com \
    --cc=adrianhoyin.ng@altera.com \
    --cc=linux-i3c@lists.infradead.org \
    --cc=linux-kernel@vger.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