From: Jean Delvare <khali@linux-fr.org>
To: Ed Swierk <eswierk@aristanetworks.com>
Cc: linux-i2c@vger.kernel.org, David Brownell <david-b@pacbell.net>,
Alessandro Zummo <a.zummo@towertech.it>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
BARRE Sebastien <sbarre@sdelcc.com>
Subject: Re: [PATCH] rtc-ds1307: True SMBus compatibility
Date: Tue, 20 Jan 2009 11:43:04 +0100 [thread overview]
Message-ID: <20090120114304.3b956189@hyperion.delvare> (raw)
In-Reply-To: <1232409577.25123.11.camel@localhost.localdomain>
Hi Ed,
On Mon, 19 Jan 2009 15:59:37 -0800, Ed Swierk wrote:
> Here is an updated patch for rtc-ds1307 that allows the driver to work
> with SMBus controllers like nforce2 that do not support i2c block
> transfers. The driver now checks the capabilities of the controller and
> emulates the block transfers with SMBus byte transfers only if
> necessary.
>
> Signed-off-by: Ed Swierk <eswierk@aristanetworks.com>
Patch looks reasonable, with just minor objections:
> Index: linux-2.6.27.4/drivers/rtc/rtc-ds1307.c
> ===================================================================
> --- linux-2.6.27.4.orig/drivers/rtc/rtc-ds1307.c
> +++ linux-2.6.27.4/drivers/rtc/rtc-ds1307.c
> @@ -94,6 +94,10 @@ struct ds1307 {
> struct i2c_client *client;
> struct rtc_device *rtc;
> struct work_struct work;
> + s32 (*read_block_data)(struct i2c_client *client, u8 command,
> + u8 length, u8 *values);
> + s32 (*write_block_data)(struct i2c_client *client, u8 command,
> + u8 length, const u8 *values);
> };
>
> struct chip_desc {
> @@ -132,6 +136,61 @@ MODULE_DEVICE_TABLE(i2c, ds1307_id);
>
> /*----------------------------------------------------------------------*/
>
> +static s32 ds1307_read_block_data_once(struct i2c_client *client, u8 command,
> + u8 length, u8 *values)
> +{
> + s32 i, data;
> + for (i = 0; i < length; i++) {
> + data = i2c_smbus_read_byte_data(client, command + i);
> + if (data < 0)
> + return data;
> + *(values + i) = data;
> + }
> + return i;
> +}
> +
> +static s32 ds1307_read_block_data(struct i2c_client *client, u8 command,
> + u8 length, u8 *values)
> +{
> + u8 oldvalues[I2C_SMBUS_BLOCK_MAX];
> + s32 ret;
> + pr_debug("ds1307_read_block_data (length=%d)\n", length);
Please use dev_dbg(&client->dev, ...).
> + ret = ds1307_read_block_data_once(client, command, length, values);
> + if (ret < 0)
> + return ret;
> + do {
> + s32 ret;
Redeclaring a variable that already exists?
> + memcpy(oldvalues, values, length);
> + ret = ds1307_read_block_data_once(client, command, length, values);
> + if (ret < 0)
> + return ret;
> + } while (memcmp(oldvalues, values, length));
What guarantee do you have that you'll ever leave this loop?
> + return length;
> +}
> +
> +static s32 ds1307_write_block_data(struct i2c_client *client, u8 command,
> + u8 length, const u8 *values)
> +{
> + u8 currvalues[I2C_SMBUS_BLOCK_MAX];
> + pr_debug("ds1307_write_block_data (length=%d)\n", length);
dev_dbg
> + do {
> + s32 i, ret;
> + for (i = 0; i < length; i++) {
> + ret = i2c_smbus_write_byte_data(client, command + i,
> + *(values + i));
> + if (ret < 0)
> + return ret;
> + }
> + ret = ds1307_read_block_data_once(client, command, length,
> + currvalues);
> + if (ret < 0)
> + return ret;
> + } while (memcmp(currvalues, values, length));
Same question as above, what if you get stuck in the loop?
> + return length;
> +}
> +
> +/*----------------------------------------------------------------------*/
> +
> /*
All the rest is fine.
--
Jean Delvare
next prev parent reply other threads:[~2009-01-20 10:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-05 17:41 [PATCH] rtc-ds1307: True SMBus compatibility Ed Swierk
2009-01-06 22:48 ` David Brownell
2009-01-07 13:24 ` Jean Delvare
2009-01-07 15:22 ` Ed Swierk
2009-01-07 15:27 ` Jean Delvare
2009-01-07 15:43 ` Ed Swierk
2009-01-07 15:49 ` Jean Delvare
2009-01-19 23:59 ` Ed Swierk
2009-01-20 10:43 ` Jean Delvare [this message]
2009-01-26 6:33 ` Ed Swierk
2009-01-26 9:37 ` Jean Delvare
2009-01-26 21:06 ` David Brownell
2009-01-26 21:54 ` Ed Swierk
-- strict thread matches above, loose matches on Subject: below --
2009-01-05 17:36 Ed Swierk
2009-01-06 13:35 ` BARRE Sebastien
2009-01-06 22:06 ` Alessandro Zummo
2009-01-06 22:13 ` Ed Swierk
2009-01-07 14:22 ` BARRE Sebastien
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=20090120114304.3b956189@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=a.zummo@towertech.it \
--cc=akpm@linux-foundation.org \
--cc=david-b@pacbell.net \
--cc=eswierk@aristanetworks.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sbarre@sdelcc.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