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: Wed, 7 Jan 2009 14:24:26 +0100 [thread overview]
Message-ID: <20090107142426.4be04d4d@hyperion.delvare> (raw)
In-Reply-To: <1231177261.13443.20.camel@localhost.localdomain>
Hi Ed,
On Mon, 05 Jan 2009 09:41:01 -0800, Ed Swierk wrote:
> [Resent to correct linux-i2c address]
>
> Following up to Sebastien Barre's recent patch, here I go one step
> further, replacing i2c block transfers with SMBus byte transfers.
Please, no. Adding a compatibility quirk may be acceptable, but forcing
everyone to use it instead of the more efficient original code is not
fair.
> Sticking to pure SMBus makes the driver work on our board, which has an
> nVidia SMBus controller driving a DS1339; nforce2 controllers
> unfortunately don't support any flavor of i2c block transfer.
Are you certain the nForce2 controllers can't do it? The i2c-nforce2
driver doesn't implement it, but this doesn't mean the hardware can't
do it. I don't have any datasheet for these chips, but I know their
SMBus implementation is very similar to those of the AMD 8111, and
i2c-amd8111 has support for I2C block reads and writes. I think it
would be worth giving it a try, by copying the i2c-amd8111
implementation into the i2c-nforce2 driver and seeing if it happens to
just work. If it works, that would be more elegant than your proposed
hack to the rtc-ds1307 driver.
> Reading or writing registers repeatedly until they stick is rather
> nauseating but I'm aiming for correctness if not elegance. I would
> appreciate any suggestions for improvement.
See above.
--
Jean Delvare
next prev parent reply other threads:[~2009-01-07 13:24 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 [this message]
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
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=20090107142426.4be04d4d@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