public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: Ed Swierk <eswierk@aristanetworks.com>
Cc: linux-i2c@vger.kernel.org,
	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, 6 Jan 2009 14:48:55 -0800	[thread overview]
Message-ID: <200901061448.56500.david-b@pacbell.net> (raw)
In-Reply-To: <1231177261.13443.20.camel@localhost.localdomain>

On Monday 05 January 2009, Ed Swierk wrote:
> 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.

Can i2c_smbus_read_i2c_block_data()/i2c_ smbus_write_i2c_block_data()
work better -- without nauseating anyone?

Faking atomic writes doesn't seem "correct" to me.  Minimally there
is the case of an alarm misfiring.

- Dave

  reply	other threads:[~2009-01-06 22:49 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 [this message]
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
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=200901061448.56500.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=a.zummo@towertech.it \
    --cc=akpm@linux-foundation.org \
    --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