Hi Mark,
> Uhh oh... The i2c-mv64xxx.c driver--note that the ctlr is *not* and
> smbus ctlr and only provides one byte at a time to the driver--that I
> wrote simply puts the incoming bytes into the buffer in the order
> that they arrive (and sends them out in the order that they appear in
> the buffer (i.e., as a byte-stream)). That is wrong?!?!
No, it's all OK. Don't worry :)
> So, after the read transfer is completed, I should go thru the buffer
> applying le16_to_cpu() to each pair of bytes? What if there are an
> odd number of bytes? Also, I guess I should apply cpu_to_le16() to
> the buffer before I send it out?
No. The byte swapping thing only makes sense for word transfers anyway,
as defined by the SMBus specification. In you case, your driver provides
low control (byte-level and flags) control over the bus, if I read
correctly. You do not implement SMBus functions individually. The
i2c-core takes care of it for you, through an smbus-over-i2c-emulation
function (i2c_smbus_xfer_emulated). Look at the function and you'll see
this:
case I2C_SMBUS_WORD_DATA:
(...)
data->word = msgbuf1[0] | (msgbuf1[1] << 8);
break;
So as you see it'll work regardless of the endianess (although not
necessarily in the most efficient way).
No need to worry, really, your code is alright as far as I can see :)
--
Jean Delvare
