linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* What endianness is word in i2c_smbus_data?
@ 2013-07-17  1:57 Andy Lutomirski
       [not found] ` <CALCETrUKK2j17LP+dVe61UCj05w914RRgyGXhorP1nfS7=rKnA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
  0 siblings, 1 reply; 2+ messages in thread
From: Andy Lutomirski @ 2013-07-17  1:57 UTC (permalink / raw)
  To: linux-i2c, linux-kernel

I'm rather confused here.  In SMBUS, the "read word" operation returns
two bytes.  Just to be confusing, the SMBUS spec calls the first byte
"Data Byte Low" and the second byte "Data Byte High".  But they really
are the first and second bytes -- Read Word will return whatever Read
Byte would have as its first byte.  Let's call these bytes B1 and B2
for first and second.

The eeprom and at24 drivers expect data->word to be (B2 << 8) | B1.
That is, data->word is the cpu representation of the value on the bus
if that value is treated as little-endian.  Is that indeed the correct
interpretation?  If so, should it be documented somewhere?

--Andy

-- 
Andy Lutomirski
AMA Capital Management, LLC

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

* Re: What endianness is word in i2c_smbus_data?
       [not found] ` <CALCETrUKK2j17LP+dVe61UCj05w914RRgyGXhorP1nfS7=rKnA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
@ 2013-07-17 13:05   ` Paul Carpenter
  0 siblings, 0 replies; 2+ messages in thread
From: Paul Carpenter @ 2013-07-17 13:05 UTC (permalink / raw)
  To: Andy Lutomirski
  Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA

Andy Lutomirski wrote:
> I'm rather confused here.  In SMBUS, the "read word" operation returns
> two bytes.  Just to be confusing, the SMBUS spec calls the first byte
> "Data Byte Low" and the second byte "Data Byte High".  But they really
> are the first and second bytes -- Read Word will return whatever Read
> Byte would have as its first byte.  Let's call these bytes B1 and B2
> for first and second.

No that tells you WHATEVER the HOST endianness the bus transfer is
always treated the same, so when two bytes are combined (into a word,
the first will be the low byte for the HOST and the second will be the
high byte for the HOST. These may actually be different for the SLAVE
device.

> The eeprom and at24 drivers expect data->word to be (B2 << 8) | B1.
> That is, data->word is the cpu representation of the value on the bus
> if that value is treated as little-endian.  Is that indeed the correct
> interpretation?  If so, should it be documented somewhere?

Several I2C devices eg PCF8575 and MCP23017 often give 16 bit results as
2 byte transfers, knowing which byte order from device to bus to host
needs matching.

So knowing that a word is made up of bytes transmitted or received in a
particular order is important as some devices do transmit high byte
first.

> --Andy
> 


-- 
Paul Carpenter          | paul-YHLC2tV1sDlxR4N9A70vTlRxknfHcPLb9dF7HbQ/qKg@public.gmane.org
<http://www.pcserviceselectronics.co.uk/>    PC Services
<http://www.pcserviceselectronics.co.uk/pi/>  Raspberry Pi Add-ons
<http://www.pcserviceselectronics.co.uk/fonts/> Timing Diagram Font
<http://www.gnuh8.org.uk/>  GNU H8 - compiler & Renesas H8/H8S/H8 Tiny
<http://www.badweb.org.uk/> For those web sites you hate

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

end of thread, other threads:[~2013-07-17 13:05 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-07-17  1:57 What endianness is word in i2c_smbus_data? Andy Lutomirski
     [not found] ` <CALCETrUKK2j17LP+dVe61UCj05w914RRgyGXhorP1nfS7=rKnA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-07-17 13:05   ` Paul Carpenter

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