archive mirror
 help / color / mirror / Atom feed
* spi_mpc8xxx: Setting cs_change at the last transfer of a message
@ 2010-01-25 16:21 Torsten Fleischer
  0 siblings, 0 replies; only message in thread
From: Torsten Fleischer @ 2010-01-25 16:21 UTC (permalink / raw)
  To: spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f
  Cc: linuxppc-dev-uLR06cmDAlY/bJ5BZ2RsiQ

As stated in spi.h (at struct spi_transfer) the driver can keep the chip 
select of the last device active if cs_change is set at the last transfer of a 
The spi_mpc8xxx driver always deactivates the chip select after completing the 
message regardless of cs_change is set or not.

I'd like to patch this. But before doing that I'd like to learn if there are 
any known use cases where the above described behavior of the driver is 


Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2010-01-25 16:21 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-01-25 16:21 spi_mpc8xxx: Setting cs_change at the last transfer of a message Torsten Fleischer

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