linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* I2C Master with limited transmission sizes
@ 2013-11-16  3:38 Peter Hüwe
       [not found] ` <201311160438.36636.PeterHuewe-Mmb7MZpHnFY@public.gmane.org>
  0 siblings, 1 reply; 3+ messages in thread
From: Peter Hüwe @ 2013-11-16  3:38 UTC (permalink / raw)
  To: linux-i2c-u79uwXL29TY76Z2rM5mHXA

Hi,

I'm currently writing a driver for a cheap usb-to-i2c master device, which 
unfortunately can only write 31 bytes (+slave addr) and read 32 bytes.

What is the correct behavior if a user requests larger read/writes?
Simply set i2c_msg.len to the bytes transmitted?
(in this case i2cdump -i doesn't honor this length ?)

Or should the master try to split up the requests?
but if so how, as some devices don't support continuous reads.

Thanks,
Peter

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

end of thread, other threads:[~2013-11-18 23:03 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-11-16  3:38 I2C Master with limited transmission sizes Peter Hüwe
     [not found] ` <201311160438.36636.PeterHuewe-Mmb7MZpHnFY@public.gmane.org>
2013-11-17 11:15   ` Wolfram Sang
2013-11-18 23:03     ` Peter Hüwe

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).