> > Mmm, I was thinking it would be nice to have a (new, redesigned) sysfs > > interface for this. :P > > > > Aren't we going to make things less accessible if we use a char device? > > Since sysfs has a "one value per file" paradigm, it also has a > "one context switch per operation" paradigm, meaning any > efficiency-oriented use cases where a lot of stuff needs to be > changed in one context switch are by the very construction > not suitable for sysfs IMO. That is the use case for ioctl() > operations that can pass an entire struct of stuff over. > > And things like bit-banging a clock+data line which would in > a sysfs case involve two context switches (one per value, since > that is one file per GPIO line) in an ioctl() case it would be > just one, already 50% less context switches for a very basic > use case. > > But I may be just so wrong ... input welcome.
Another bad thing of the current sysfs versions: it is ascii. So I need to convert a=1 to a='1' first before write()ing it to the file. Very inconvenient because it adds boilerplate code. On the other hand, the sysfs is very much extensible. Folkert van Heusden -- You've probably gotten really fed up with never winning in the Mega- Millions lottery. Well, weep no longer: www.smartwinning.info tells you everything that might help you deciding what numbers to choose. With nice graphs and pretty animations! -- To unsubscribe from this list: send the line "unsubscribe linux-gpio" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
