On 23/08/15 08:29, Matt Ranostay wrote: > That all seems perfectly logical just wanted to be sure what would be the best way. > > Would it make sense to block temp reads to raw with the heater on? > Like what a lot of drivers do on buffered triggered reads for some > channels Probably chip dependent (might be well isolated as some of these parts are quite large). However, if it definitely has a pronounced effect (guessing it does) then sure. Return -EBUSY if it is enabled and the temperature is read. J > > Sent from my iPhone > >> On Aug 20, 2015, at 20:56, Matt Ranostay <mranostay@xxxxxxxxx> wrote: >> >> Jonathan et all, >> >> So I am currently working on a driver for the TI HDC100x series of >> temp + humidity sensors, and have a question on how we should handler >> the heater functionality. >> >> This seems quite common in high accuracy relative humidity sensors to >> have a resistive element within the sensor to heat up the device and >> get rid of any condensation that happens in a high humidity >> environment. >> >> Now it could be a one off sysfs entry within the driver like >> "heater_status" but it seems something we want to more generic since >> this will be an issue in the future (aka si7005 driver for instance). >> >> Thoughts? Comments? >> >> Thanks, >> >> Matt > -- > To unsubscribe from this list: send the line "unsubscribe linux-iio" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- To unsubscribe from this list: send the line "unsubscribe linux-iio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
