devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Abd-Alrhman Masalkhi <abd.masalkhi@gmail.com>
To: christophe.jaillet@wanadoo.fr
Cc: abd.masalkhi@gmail.com, arnd@arndb.de, conor+dt@kernel.org,
	devicetree@vger.kernel.org, gregkh@linuxfoundation.org,
	krzk+dt@kernel.org, linux-kernel@vger.kernel.org,
	luoyifan@cmss.chinamobile.com, robh@kernel.org
Subject: Re: [PATCH v5 2/3] eeprom: add driver for ST M24LR series RFID/NFC EEPROM chips
Date: Fri,  4 Jul 2025 21:29:28 +0000	[thread overview]
Message-ID: <20250704212929.12348-1-abd.masalkhi@gmail.com> (raw)
In-Reply-To: <95dad033-4338-46de-b62a-be1db459b0ec@wanadoo.fr>

Hi Christophe

On Fri, 4 Jul 2025 20:40:51 +0200, Christophe JAILLET wrote:
>>>> +/**
>>>> + * m24lr_regmap_read - read data using regmap with retry on failure
>>>> + * @regmap:  regmap instance for the device
>>>> + * @buf:     buffer to store the read data
>>>> + * @size:    number of bytes to read
>>>> + * @offset:  starting register address
>>>> + *
>>>> + * Attempts to read a block of data from the device with retries and timeout.
>>>> + * Some M24LR chips may transiently NACK reads (e.g., during internal write
>>>> + * cycles), so this function retries with a short sleep until the timeout
>>>> + * expires.
>>>> + *
>>>> + * Returns:
>>>> + *	 Number of bytes read on success,
>>>> + *	 -ETIMEDOUT if the read fails within the timeout window.
>>>> + */
>>>> +static ssize_t m24lr_regmap_read(struct regmap *regmap, u8 *buf,
>>>> +				 size_t size, unsigned int offset)
>>>
>>> Why returning a ssize_t?
>>> regmap_bulk_read() returns an int.
>> 
>> Since I return @size (of type size_t) on success, should I keep the
>> return type as ssize_t, or would it be better to change it to int
>> to match regmap_bulk_read()?
>
> Hmm, this ends being used with BIN_ATTR() in 
> m24lr_ctl_sss_[read|write]() so it needs to keep with ssize_t.

Done.

Best regards,
Abd-Alrhman Masalkhi

  reply	other threads:[~2025-07-04 21:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-04 12:39 [PATCH v5 0/3] Add support for STMicroelectronics M24LR EEPROM/NFC chips Abd-Alrhman Masalkhi
2025-07-04 12:39 ` [PATCH v5 1/3] dt-bindings: eeprom: Add ST M24LR support Abd-Alrhman Masalkhi
2025-07-04 15:10   ` Krzysztof Kozlowski
2025-07-04 15:24     ` Abd-Alrhman Masalkhi
2025-07-04 12:39 ` [PATCH v5 2/3] eeprom: add driver for ST M24LR series RFID/NFC EEPROM chips Abd-Alrhman Masalkhi
2025-07-04 14:12   ` Christophe JAILLET
2025-07-04 14:41     ` Abd-Alrhman Masalkhi
2025-07-04 15:11     ` Abd-Alrhman Masalkhi
2025-07-04 18:40       ` Christophe JAILLET
2025-07-04 21:29         ` Abd-Alrhman Masalkhi [this message]
2025-07-04 12:39 ` [PATCH v5 3/3] ABI: sysfs: add documentation for ST M24LR EEPROM and control interface Abd-Alrhman Masalkhi

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=20250704212929.12348-1-abd.masalkhi@gmail.com \
    --to=abd.masalkhi@gmail.com \
    --cc=arnd@arndb.de \
    --cc=christophe.jaillet@wanadoo.fr \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luoyifan@cmss.chinamobile.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;
as well as URLs for NNTP newsgroup(s).