Wolfgang Denk <[EMAIL PROTECTED]> wrote: > In message <[EMAIL PROTECTED]> you wrote: > > > > Yes, perhaps we need that. But I was sort of thinking that once you > > initialize a slave, it will just stick around until you boot an OS or > > reset. Most drivers don't seem to have any cleanup hooks anyway, and > > some don't even have init hooks. In the latter case, you can simply > > keep a static struct spi_slave * around and if it's NULL, you > > initialize it. > > Even if there is lots of bad examples, it is a design requirement to > disable a hardware interface after use. See bullet 6 at > http://www.denx.de/wiki/UBoot/DesignRequirements
I know. That's what the spi_claim_bus() and spi_release_bus() hooks are supposed to do. I just don't see the point of deallocating the spi_slave struct memory; this has nothing to do with disabling hardware. Haavard ------------------------------------------------------------------------- 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 _______________________________________________ U-Boot-Users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/u-boot-users
