From: Jean Delvare <jdelvare@suse.de>
To: Linux I2C <linux-i2c@vger.kernel.org>
Cc: Bartosz Golaszewski <bgolaszewski@baylibre.com>,
Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: [PATCH 2/2 RFC] eeprom: at24: Tidy at24_read()
Date: Fri, 7 Aug 2020 16:19:06 +0200 [thread overview]
Message-ID: <20200807161906.6d119d2e@endymion> (raw)
In-Reply-To: <20200807150005.48c8c89b@endymion>
The elegant code in at24_read() has the drawback that we now need
to make a copy of all parameters to pass them to the post-processing
callback function if there is one. Rewrite the loop in such a way that
the parameters are not modified, so saving them is no longer needed.
Signed-off-by: Jean Delvare <jdelvare@suse.de>
Cc: Bartosz Golaszewski <bgolaszewski@baylibre.com>
Cc: Arnd Bergmann <arnd@arndb.de>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
---
This has the drawback of creating an asymetry with at24_write(), so
I'm not 100% if we want to apply this. If anyone has a better idea,
please let me know.
drivers/misc/eeprom/at24.c | 13 +++++--------
1 file changed, 5 insertions(+), 8 deletions(-)
--- linux-5.7.orig/drivers/misc/eeprom/at24.c 2020-08-07 14:23:39.882191500 +0200
+++ linux-5.7/drivers/misc/eeprom/at24.c 2020-08-07 14:28:39.039360687 +0200
@@ -423,10 +423,7 @@ static int at24_read(void *priv, unsigne
struct at24_data *at24;
struct device *dev;
char *buf = val;
- int ret;
- unsigned int orig_off = off;
- char *orig_buf = buf;
- size_t orig_count = count;
+ int i, ret;
at24 = priv;
dev = at24_base_client_dev(at24);
@@ -449,15 +446,15 @@ static int at24_read(void *priv, unsigne
*/
mutex_lock(&at24->lock);
+ i = 0;
while (count) {
- ret = at24_regmap_read(at24, buf, off, count);
+ ret = at24_regmap_read(at24, buf + i, off + i, count);
if (ret < 0) {
mutex_unlock(&at24->lock);
pm_runtime_put(dev);
return ret;
}
- buf += ret;
- off += ret;
+ i += ret;
count -= ret;
}
@@ -466,7 +463,7 @@ static int at24_read(void *priv, unsigne
pm_runtime_put(dev);
if (unlikely(at24->read_post))
- at24->read_post(orig_off, orig_buf, orig_count);
+ at24->read_post(off, buf, i);
return 0;
}
--
Jean Delvare
SUSE L3 Support
next prev parent reply other threads:[~2020-08-07 14:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-07 13:00 [PATCH 1/2] eeprom: at24: Add support for the Sony VAIO EEPROMs Jean Delvare
2020-08-07 14:19 ` Jean Delvare [this message]
2020-08-18 13:46 ` [PATCH 2/2 RFC] eeprom: at24: Tidy at24_read() Bartosz Golaszewski
2020-08-25 6:38 ` Jean Delvare
2020-08-12 18:10 ` [PATCH 1/2] eeprom: at24: Add support for the Sony VAIO EEPROMs Bartosz Golaszewski
2020-08-18 13:41 ` Bartosz Golaszewski
2020-08-24 17:03 ` Jean Delvare
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=20200807161906.6d119d2e@endymion \
--to=jdelvare@suse.de \
--cc=arnd@arndb.de \
--cc=bgolaszewski@baylibre.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-i2c@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