odd behaviour of chipselect with bitbang driver?

odd behaviour of chipselect with bitbang driver?

[Erwin Authried]

when cs_change is set on the last part of the spi transfer, the
chipselect is kept active after the transfer as expected. When a new
transfer is started with a different chipselect, the first chipselect
isn't deselected. Shouldn't the driver make sure that there is never
more than one chipselect active at once?

Regards,
Erwin



-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone

Re: odd behaviour of chipselect with bitbang driver?

[David Brownell]

On Thursday 24 April 2008, Erwin Authried wrote:
> when cs_change is set on the last part of the spi transfer, the
> chipselect is kept active after the transfer as expected. When a new
> transfer is started with a different chipselect, the first chipselect
> isn't deselected. Shouldn't the driver make sure that there is never
> more than one chipselect active at once?

Yes it should.  That's an oversight in the testing ... got patch?

- dave

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone