Re: [PATCH v3 3/3] powerpc/powernv: remove opal_sensor_mutex

2015-03-30 Thread Cedric Le Goater
On 03/30/2015 08:59 AM, Michael Ellerman wrote: > On Mon, 2015-03-30 at 08:51 +0200, Cedric Le Goater wrote: >> On 03/30/2015 04:09 AM, Michael Ellerman wrote: >>> 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

Re: [PATCH v3 3/3] powerpc/powernv: remove opal_sensor_mutex

2015-03-30 Thread Michael Ellerman
On Mon, 2015-03-30 at 08:51 +0200, Cedric Le Goater wrote: > On 03/30/2015 04:09 AM, Michael Ellerman wrote: > > 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

Re: [PATCH v3 3/3] powerpc/powernv: remove opal_sensor_mutex

2015-03-29 Thread Cedric Le Goater
On 03/30/2015 04:09 AM, Michael Ellerman wrote: > 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 u

Re: [PATCH v3 3/3] powerpc/powernv: remove opal_sensor_mutex

2015-03-29 Thread Michael Ellerman
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 actua

[PATCH v3 3/3] powerpc/powernv: remove opal_sensor_mutex

2015-03-27 Thread Cédric Le Goater
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. Signed-off-by: Cédric Le Goater --- Changes since v2 : - removed a goto label arch/powerpc/