On Thursday 12 March 2009, Yusuf Caglar AKYUZ wrote: > In fact we're using GPIO in our own boards and: > > 1) DRVVBUS control must be board specific.
Ditto the very notion that the SoC's own DRVVBUS output won't be used, so a GPIO is needed instead. Yeech. > 2) Simply passing GPIO with platform data is not enough because > polarity may even change. > 3) I guess we don't need a workqueue for direct GPIO control. > > What is the best way to achieve these goals? Passing a function > pointer via platform data to handle pin control at board* files, or > passing GPIO number and polarity via platform data while using > workqueue for all the cases? If the SoC's signal isn't being used, some kind of platform_data solution might be best. Although I had hoped that nastiness would be specific to the DM6446 EVM ... if more than one board is doing it, then sharing that code would be best. Call gpio_cansleep() to tell if a workqueue is needed. _______________________________________________ Davinci-linux-open-source mailing list [email protected] http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
