linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* at24: writing with SMBUS and no I2C_FUNC_SMBUS_WRITE_I2C_BLOCK
@ 2014-03-05 18:33 Curt Brune
       [not found] ` <20140305183305.GS27140-qUQiAmfTcIp+XZJcv9eMoEEOCMrvLtNR@public.gmane.org>
  0 siblings, 1 reply; 2+ messages in thread
From: Curt Brune @ 2014-03-05 18:33 UTC (permalink / raw)
  To: Wolfram Sang; +Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA

Hello -

I have a system that uses SMBUS, but without the
I2C_FUNC_SMBUS_WRITE_I2C_BLOCK functionality.  As it is today at24.c
will only support read-only mode for this case.

Looking at at24_eeprom_write() the comments indicate it only supports
page writes as the alternative is too slow.  This decision seems to be
the root of why SMBUS without I2C_FUNC_SMBUS_WRITE_I2C_BLOCK gives the
read-only situation.

The notion of "slow" seems a bit arbitrary to me.  Is there some other
technical reason or gotcha hiding here that you know of?

Would a nicely written patch that adds write support for this case be
acceptable?  I have not written it yet, but would like to.

Cheers,
Curt

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2014-03-05 20:15 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-03-05 18:33 at24: writing with SMBUS and no I2C_FUNC_SMBUS_WRITE_I2C_BLOCK Curt Brune
     [not found] ` <20140305183305.GS27140-qUQiAmfTcIp+XZJcv9eMoEEOCMrvLtNR@public.gmane.org>
2014-03-05 20:15   ` Wolfram Sang

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).