Re: sysfs and power management

[Henrique de Moraes Holschuh <hmh@hmh.eng.br>]

On Fri, 29 Oct 2010, Greg KH wrote:
> back to sleep.  That's probably the best way to do this, as userspace
> isn't going to open the sysfs file and not close it instantly anyway
> after it has read the data (seeking on a sysfs file isn't really
> recommended, even if it sometimes seems to work.)

Well, it is documented that seek(start of file) on sysfs works, and it
is ABI already (some userspace uses it on poll/select-capable
attributes).  So, maybe seek(somewhere that is not the start of the
file) doesn't work -- and it should return an error in that case if it
doesn't already...  but it is a lot more deterministic than "sometimes"
;-)

So yes, userspace will open() and not close() a sysfs attribute immediately
afterwards.  It is not only shell crap that interfaces to the kernel over
sysfs :-)

It would make a lot of sense to support the poll/select model on any
sensor for which you have event-driven notifications of change from the
hardware or firmware.

I don't know about open/close notifications, however.  Usually you need
those when you're going to stream something to userspace, and there are FAR
better interfaces to use in that case, such as the ring buffers used by the
data acquisition devices, netlink (which userspace programmers seems not to
like much :p), input devices, and generic character devices...

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh