* FSL eSPI driver: bits_per_word not used when calculating TRANLEN?
@ 2012-06-19 13:23 Kenth Eriksson
0 siblings, 0 replies; only message in thread
From: Kenth Eriksson @ 2012-06-19 13:23 UTC (permalink / raw)
To: spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f
Hi!
The eSPI drivers does not use the bits_per_word parameter when calculating
the transmission length (TRANLEN). Why?
TRANLEN in the eSPI controller is counted in characters and the len field
in spi_transfer is in bytes. I thought the relation between the two was
bits_per_word?
/k
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2012-06-19 13:23 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-06-19 13:23 FSL eSPI driver: bits_per_word not used when calculating TRANLEN? Kenth Eriksson
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.