Message ID | 1371486863-12398-30-git-send-email-t.figa@samsung.com (mailing list archive) |
---|---|
State | Not Applicable, archived |
Headers | show |
On Monday 17 June 2013, Tomasz Figa wrote: > diff --git a/drivers/thermal/exynos_thermal.c b/drivers/thermal/exynos_thermal.c > index 788b1dd..4cbe3ee 100644 > --- a/drivers/thermal/exynos_thermal.c > +++ b/drivers/thermal/exynos_thermal.c > @@ -817,7 +817,8 @@ static struct exynos_tmu_platform_data const exynos4210_default_tmu_data = { > #define EXYNOS4210_TMU_DRV_DATA (NULL) > #endif > > -#if defined(CONFIG_SOC_EXYNOS5250) || defined(CONFIG_SOC_EXYNOS4412) > +#if defined(CONFIG_SOC_EXYNOS5250) || defined(CONFIG_SOC_EXYNOS4412) || \ > + defined(CONFIG_SOC_EXYNOS4212) > static struct exynos_tmu_platform_data const exynos_default_tmu_data = { > .threshold_falling = 10, > .trigger_levels[0] = 85, The patch is correct, but generally speaking I think we should get away from having the drivers get configured per SoC on such a fine-grained level. Better make this driver (and others) always work on all exynos variants. Arnd -- To unsubscribe from this list: send the line "unsubscribe linux-pm" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Arnd, On 17-06-2013 15:59, Arnd Bergmann wrote: > On Monday 17 June 2013, Tomasz Figa wrote: >> diff --git a/drivers/thermal/exynos_thermal.c b/drivers/thermal/exynos_thermal.c >> index 788b1dd..4cbe3ee 100644 >> --- a/drivers/thermal/exynos_thermal.c >> +++ b/drivers/thermal/exynos_thermal.c >> @@ -817,7 +817,8 @@ static struct exynos_tmu_platform_data const exynos4210_default_tmu_data = { >> #define EXYNOS4210_TMU_DRV_DATA (NULL) >> #endif >> >> -#if defined(CONFIG_SOC_EXYNOS5250) || defined(CONFIG_SOC_EXYNOS4412) >> +#if defined(CONFIG_SOC_EXYNOS5250) || defined(CONFIG_SOC_EXYNOS4412) || \ >> + defined(CONFIG_SOC_EXYNOS4212) >> static struct exynos_tmu_platform_data const exynos_default_tmu_data = { >> .threshold_falling = 10, >> .trigger_levels[0] = 85, > > The patch is correct, but generally speaking I think we should get away from > having the drivers get configured per SoC on such a fine-grained level. > Better make this driver (and others) always work on all exynos variants. Amit, correct if I am wrong, but: The driver will work on supported exynos variants. Those that have the need for thermal sensing. And each of them have specific thermal needs (trigger points, thresholds, etc). That is what this file tries to isolate. And there is specific data structures for each soc version. > > Arnd > >
Hi Eduardo, On Tue, Jun 18, 2013 at 5:04 AM, Eduardo Valentin <eduardo.valentin@ti.com> wrote: > Arnd, > > On 17-06-2013 15:59, Arnd Bergmann wrote: >> On Monday 17 June 2013, Tomasz Figa wrote: >>> diff --git a/drivers/thermal/exynos_thermal.c b/drivers/thermal/exynos_thermal.c >>> index 788b1dd..4cbe3ee 100644 >>> --- a/drivers/thermal/exynos_thermal.c >>> +++ b/drivers/thermal/exynos_thermal.c >>> @@ -817,7 +817,8 @@ static struct exynos_tmu_platform_data const exynos4210_default_tmu_data = { >>> #define EXYNOS4210_TMU_DRV_DATA (NULL) >>> #endif >>> >>> -#if defined(CONFIG_SOC_EXYNOS5250) || defined(CONFIG_SOC_EXYNOS4412) >>> +#if defined(CONFIG_SOC_EXYNOS5250) || defined(CONFIG_SOC_EXYNOS4412) || \ >>> + defined(CONFIG_SOC_EXYNOS4212) >>> static struct exynos_tmu_platform_data const exynos_default_tmu_data = { >>> .threshold_falling = 10, >>> .trigger_levels[0] = 85, >> >> The patch is correct, but generally speaking I think we should get away from >> having the drivers get configured per SoC on such a fine-grained level. >> Better make this driver (and others) always work on all exynos variants. > > Amit, correct if I am wrong, but: > > The driver will work on supported exynos variants. Those that have the > need for thermal sensing. And each of them have specific thermal needs > (trigger points, thresholds, etc). That is what this file tries to > isolate. And there is specific data structures for each soc version. Yes its correct that there may be some changes in data points for different soc's. in the new re-structured code data is separated from driver so more data can be added cleanly. > > >> >> Arnd >> >> > > > -- > You have got to be excited about what you are doing. (L. Lamport) > > Eduardo Valentin > -- To unsubscribe from this list: send the line "unsubscribe linux-pm" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Tuesday 18 June 2013, Eduardo Valentin wrote: > The driver will work on supported exynos variants. Those that have the > need for thermal sensing. And each of them have specific thermal needs > (trigger points, thresholds, etc). That is what this file tries to > isolate. And there is specific data structures for each soc version. Correct. My point is that the driver itself is much larger than the SoC-specific data sets in it. There is no reason to conditionally build a 108 byte data structure, making it more maintainably by removing all the #ifdef far outweighs the cost. You can also change the driver to work only for DT based booting, that will simplify it further and save you more in terms of object code size than the exynos_tmu_platform_data instances. Arnd -- To unsubscribe from this list: send the line "unsubscribe linux-pm" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
diff --git a/drivers/thermal/exynos_thermal.c b/drivers/thermal/exynos_thermal.c index 788b1dd..4cbe3ee 100644 --- a/drivers/thermal/exynos_thermal.c +++ b/drivers/thermal/exynos_thermal.c @@ -817,7 +817,8 @@ static struct exynos_tmu_platform_data const exynos4210_default_tmu_data = { #define EXYNOS4210_TMU_DRV_DATA (NULL) #endif -#if defined(CONFIG_SOC_EXYNOS5250) || defined(CONFIG_SOC_EXYNOS4412) +#if defined(CONFIG_SOC_EXYNOS5250) || defined(CONFIG_SOC_EXYNOS4412) || \ + defined(CONFIG_SOC_EXYNOS4212) static struct exynos_tmu_platform_data const exynos_default_tmu_data = { .threshold_falling = 10, .trigger_levels[0] = 85,