From: Jean Delvare <khali@linux-fr.org>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Alessandro Zummo <a.zummo@towertech.it>,
Andrew Morton <akpm@linux-foundation.org>,
Atsushi Nemoto <anemo@mba.ocn.ne.jp>,
David Woodhouse <dwmw2@infradead.org>,
Ralf Baechle <ralf@linux-mips.org>,
Thomas Gleixner <tglx@linutronix.de>,
rtc-linux@googlegroups.com, i2c@lm-sensors.org,
linux-mips@linux-mips.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/6] RTC: SMBus support for the M41T80, etc. driver (#2)
Date: Tue, 13 May 2008 14:04:44 +0200 [thread overview]
Message-ID: <20080513140444.49d7a044@hyperion.delvare> (raw)
In-Reply-To: <Pine.LNX.4.55.0805130254420.535@cliff.in.clinika.pl>
Hi Maciej,
On Tue, 13 May 2008 04:27:30 +0100 (BST), Maciej W. Rozycki wrote:
> The BCM1250A SOC which is used on the SWARM board utilising an M41T81
> chip only supports pure I2C in the raw bit-banged mode. Nobody sane
> really wants to use it unless absolutely necessary and the M41T80, etc.
> chips work just fine with an SMBus adapter which is what the standard mode
> of operation of the BCM1250A. The only drawback of byte accesses with the
> M41T80 is the chip only latches clock data registers for the duration of
> an I2C transaction which works fine with a block transfers, but not
> byte-wise accesses.
>
> The driver currently requires an I2C adapter providing both SMBus and raw
> I2C access. This is a set of changes to make it work with any SMBus
> adapter providing at least read byte and write byte protocols.
> Additionally, if a given SMBus adapter supports I2C block read and/or
> write protocols (a common extension beyond the SMBus spec), they are used
> as well. The problem of unlatched clock data if SMBus byte transactions
> are used is resolved in the standard way. For raw I2C controllers this
> functionality is provided by the I2C core as SMBus emulation in a
> transparent way.
>
> Signed-off-by: Maciej W. Rozycki <macro@linux-mips.org>
The I2C part of the changes look OK to me. With one comment below:
> +static int m41t80_get_datetime(struct i2c_client *client, struct rtc_time *tm)
> +{
> + u8 buf[M41T80_DATETIME_REG_SIZE];
> + int loops = 2;
> + int sec0, sec1;
> +
> + /*
> + * Time registers are latched by this chip if an I2C block
> + * transfer is used, but with SMBus-style byte accesses
> + * this is not the case, so check seconds for a wraparound.
> + */
> + do {
> + if (m41t80_read_block_data(client, M41T80_REG_SEC,
> + M41T80_DATETIME_REG_SIZE -
> + M41T80_REG_SEC,
> + buf + M41T80_REG_SEC) < 0) {
> + dev_err(&client->dev, "read error\n");
> + return -EIO;
> + }
> + sec0 = buf[M41T80_REG_SEC];
>
> - tm->tm_sec = BCD2BIN(buf[M41T80_REG_SEC] & 0x7f);
> + sec1 = i2c_smbus_read_byte_data(client, M41T80_REG_SEC);
> + if (sec1 < 0) {
> + dev_err(&client->dev, "read error\n");
> + return -EIO;
> + }
> +
> + sec0 = BCD2BIN(sec0 & 0x7f);
> + sec1 = BCD2BIN(sec1 & 0x7f);
> + } while (sec1 < sec0 && --loops);
You will do this even if all the registers were read as a block and the
RTC latched the register values so they have to be correct. Isn't it a
bit unfair / inefficient? If client->adapter has the
I2C_FUNC_SMBUS_READ_I2C_BLOCK functionality you can skip the comparison
and retry mechanism completely, saving some time and CPU cycles.
--
Jean Delvare
next prev parent reply other threads:[~2008-05-13 12:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-13 3:27 [PATCH 5/6] RTC: SMBus support for the M41T80, etc. driver (#2) Maciej W. Rozycki
2008-05-13 12:04 ` Jean Delvare [this message]
2008-05-13 16:57 ` Maciej W. Rozycki
2008-05-17 15:31 ` Atsushi Nemoto
2008-05-17 20:46 ` Maciej W. Rozycki
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=20080513140444.49d7a044@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=a.zummo@towertech.it \
--cc=akpm@linux-foundation.org \
--cc=anemo@mba.ocn.ne.jp \
--cc=dwmw2@infradead.org \
--cc=i2c@lm-sensors.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=macro@linux-mips.org \
--cc=ralf@linux-mips.org \
--cc=rtc-linux@googlegroups.com \
--cc=tglx@linutronix.de \
/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