Re: [PATCH 07/18] thermal: exynos: remove threshold_code checking from exynos4210_tmu_initialize()

2018-04-30 Thread Daniel Lezcano
On Thu, Apr 26, 2018 at 01:51:22PM +0200, Bartlomiej Zolnierkiewicz wrote: > On Exynos4210 one-point trimming is always used and data->temp_error1 > is equal to 75. Therefore temp_to_code() will never return negative > value for the reference temperature conversion. > > There should be no

Re: [PATCH 07/18] thermal: exynos: remove threshold_code checking from exynos4210_tmu_initialize()

2018-04-30 Thread Daniel Lezcano
On Thu, Apr 26, 2018 at 01:51:22PM +0200, Bartlomiej Zolnierkiewicz wrote: > On Exynos4210 one-point trimming is always used and data->temp_error1 > is equal to 75. Therefore temp_to_code() will never return negative > value for the reference temperature conversion. > > There should be no

[PATCH 07/18] thermal: exynos: remove threshold_code checking from exynos4210_tmu_initialize()

2018-04-26 Thread Bartlomiej Zolnierkiewicz
On Exynos4210 one-point trimming is always used and data->temp_error1 is equal to 75. Therefore temp_to_code() will never return negative value for the reference temperature conversion. There should be no functional changes caused by this patch. Signed-off-by: Bartlomiej Zolnierkiewicz

[PATCH 07/18] thermal: exynos: remove threshold_code checking from exynos4210_tmu_initialize()

2018-04-26 Thread Bartlomiej Zolnierkiewicz
On Exynos4210 one-point trimming is always used and data->temp_error1 is equal to 75. Therefore temp_to_code() will never return negative value for the reference temperature conversion. There should be no functional changes caused by this patch. Signed-off-by: Bartlomiej Zolnierkiewicz ---