Re: [PATCH 1/1] thermal: core: call thermal_zone_device_update() after mode update

2016-07-01 Thread Eduardo Valentin
On Thu, Jun 23, 2016 at 02:27:12PM +0200, Rafael J. Wysocki wrote: > On Wed, Jun 22, 2016 at 7:06 AM, Eduardo Valentin wrote: > > Because several drivers do the following pattern: > > .set_mode() > >... > >local_data->mode = new_mode; > >

Re: [PATCH 1/1] thermal: core: call thermal_zone_device_update() after mode update

2016-07-01 Thread Eduardo Valentin
On Thu, Jun 23, 2016 at 02:27:12PM +0200, Rafael J. Wysocki wrote: > On Wed, Jun 22, 2016 at 7:06 AM, Eduardo Valentin wrote: > > Because several drivers do the following pattern: > > .set_mode() > >... > >local_data->mode = new_mode; > >thermal_zone_device_update(tz); > > > > makes

Re: [PATCH 1/1] thermal: core: call thermal_zone_device_update() after mode update

2016-06-23 Thread Keerthy
On Thursday 23 June 2016 05:57 PM, Rafael J. Wysocki wrote: On Wed, Jun 22, 2016 at 7:06 AM, Eduardo Valentin wrote: Because several drivers do the following pattern: .set_mode() ... local_data->mode = new_mode; thermal_zone_device_update(tz); makes sense to

Re: [PATCH 1/1] thermal: core: call thermal_zone_device_update() after mode update

2016-06-23 Thread Keerthy
On Thursday 23 June 2016 05:57 PM, Rafael J. Wysocki wrote: On Wed, Jun 22, 2016 at 7:06 AM, Eduardo Valentin wrote: Because several drivers do the following pattern: .set_mode() ... local_data->mode = new_mode; thermal_zone_device_update(tz); makes sense to simply do the

Re: [PATCH 1/1] thermal: core: call thermal_zone_device_update() after mode update

2016-06-23 Thread Rafael J. Wysocki
On Wed, Jun 22, 2016 at 7:06 AM, Eduardo Valentin wrote: > Because several drivers do the following pattern: > .set_mode() >... >local_data->mode = new_mode; >thermal_zone_device_update(tz); > > makes sense to simply do the thermal_zone_device_update() > in

Re: [PATCH 1/1] thermal: core: call thermal_zone_device_update() after mode update

2016-06-23 Thread Rafael J. Wysocki
On Wed, Jun 22, 2016 at 7:06 AM, Eduardo Valentin wrote: > Because several drivers do the following pattern: > .set_mode() >... >local_data->mode = new_mode; >thermal_zone_device_update(tz); > > makes sense to simply do the thermal_zone_device_update() > in thermal core, after setting

[PATCH 1/1] thermal: core: call thermal_zone_device_update() after mode update

2016-06-21 Thread Eduardo Valentin
Because several drivers do the following pattern: .set_mode() ... local_data->mode = new_mode; thermal_zone_device_update(tz); makes sense to simply do the thermal_zone_device_update() in thermal core, after setting the new mode. Also, this patch also remove deadlocks on drivers that

[PATCH 1/1] thermal: core: call thermal_zone_device_update() after mode update

2016-06-21 Thread Eduardo Valentin
Because several drivers do the following pattern: .set_mode() ... local_data->mode = new_mode; thermal_zone_device_update(tz); makes sense to simply do the thermal_zone_device_update() in thermal core, after setting the new mode. Also, this patch also remove deadlocks on drivers that