* 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[parent not found: <20140305183305.GS27140-qUQiAmfTcIp+XZJcv9eMoEEOCMrvLtNR@public.gmane.org>]
* Re: at24: writing with SMBUS and no I2C_FUNC_SMBUS_WRITE_I2C_BLOCK [not found] ` <20140305183305.GS27140-qUQiAmfTcIp+XZJcv9eMoEEOCMrvLtNR@public.gmane.org> @ 2014-03-05 20:15 ` Wolfram Sang 0 siblings, 0 replies; 2+ messages in thread From: Wolfram Sang @ 2014-03-05 20:15 UTC (permalink / raw) To: Curt Brune; +Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA [-- Attachment #1: Type: text/plain, Size: 1610 bytes --] > The notion of "slow" seems a bit arbitrary to me. Is there some other > technical reason or gotcha hiding here that you know of? $ git show 7aeb96642f70139a194d685b132605836f6f8dbb commit 7aeb96642f70139a194d685b132605836f6f8dbb Author: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org> Date: Fri May 21 18:40:57 2010 +0200 at24: Fall back to byte or word reads if needed Increase the portability of the at24 driver by letting it read from EEPROM chips connected to cheap SMBus controllers that support neither raw I2C messages nor even I2C block reads. All SMBus controllers should support either word reads or byte reads, so read support becomes universal, much like with the legacy "eeprom" driver. Obviously, this only works with EEPROM chips up to AT24C16, that use 8-bit offset addressing. 16-bit offset addressing is almost impossible to support on SMBus controllers. I did not add universal support for writes, as I had no immediate need for this, but it could be added later if needed (with the same performance issue as byte and word reads have, of course.) Signed-off-by: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org> Reviewed-by: Wolfram Sang <w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org> Cc: Konstantin Lazarev <klazarev-rphTv4pjVZMJGwgDXS7ZQA@public.gmane.org> > Would a nicely written patch that adds write support for this case be > acceptable? I have not written it yet, but would like to. Yes, it would. All the best, Wolfram [-- Attachment #2: Digital signature --] [-- Type: application/pgp-signature, Size: 836 bytes --] ^ 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).