On Fri, 2015-03-27 at 17:39 +0100, Cédric Le Goater wrote: > The opal sensor mutex protects the opal_sensor_read call which > can return a OPAL_BUSY code on IBM Power systems if a previous > request is in progress. > > This can be handled at user level with a retry.
It can, but how does it actually look in practice? It looks like the only use of opal_get_sensor_data() is show_sensor() in drivers/hwmon/ibmpowernv.c. Because that's a sysfs attribute folks will be generally just dumping that with cat, or reading it in a shell script, neither of which will cope nicely with EBUSY I think? cheers _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
