Hi! > > Perhaps we might do it via sysfs naming instead. > > > > illuminance[n] - defined to be visible (which is what term means anyway) > > > > infrared[n] - hmm.. will be in different units to illuminance - perhaps we leave > > these raw with suitable documentation? > > > > illuminance_and_infrared[n] > > > what's the unit of this? > what does the value of this file mean? > I think we should make sure that there are more sensors need this and > the same "visible + infrared" reading on different sensors stands for > the same ambient light environment. Are you sure that makes sense? And is that even possible? I'd be afraid that the sensors are not nearly accurate enough to give precise values, and each sensor is going to take different parts of spectrum, etc. Yes, we should aim at having similar interface with similar values on all the sensors, but lets not overdo it. > But maybe there are some other sensors that don't have this asynchronous > notification so that the cached values don't have a chance to get > updated. > then we need to read the sensor every time the sysfs I/F is poked. I bet most sensors are like that. And no, we don't have to reread from hw every time, we can just read and cache it once per second or something. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
