Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751584Ab3FUEDO (ORCPT ); Fri, 21 Jun 2013 00:03:14 -0400 Received: from mail-ie0-f170.google.com ([209.85.223.170]:36684 "EHLO mail-ie0-f170.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750709Ab3FUEDM (ORCPT ); Fri, 21 Jun 2013 00:03:12 -0400 MIME-Version: 1.0 In-Reply-To: <51C20E8D.8040005@ti.com> References: <1367489937-30725-1-git-send-email-amit.daniel@samsung.com> <51C20E8D.8040005@ti.com> Date: Fri, 21 Jun 2013 09:33:11 +0530 X-Google-Sender-Auth: Q0jTG2loZdZG60GAWg5whqoiBsc Message-ID: Subject: Re: [PATCH V2] thermal: exynos: Support for TMU regulator defined at device tree From: amit daniel kachhap To: Eduardo Valentin Cc: linux-pm@vger.kernel.org, Zhang Rui , linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org, Kukjin Kim , Lukasz Majewski , Sylwester Nawrocki Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 5122 Lines: 132 On Thu, Jun 20, 2013 at 1:33 AM, Eduardo Valentin wrote: > On 02-05-2013 06:18, Amit Daniel Kachhap wrote: >> TMU probe function now checks for a device tree defined regulator. >> For compatibility reasons it is allowed to probe driver even without >> this regulator defined. >> >> Signed-off-by: Luk asz Majewski >> Signed-off-by: Kyungmin Park >> Signed-off-by: Amit Daniel Kachhap > > I assume this one got superseeded by the same patch on your 30 patch > series, right? > https://patchwork.kernel.org/patch/2731031/ Yes right. In my re-structuring patch series this one is included. > > >> --- >> >> Changes in V2: >> * Added log message in regulator_get failure as suggested by Sylwester. >> * Used IS_ERR for checking regulator pointer as suggested by Sylwester. >> >> This patch is repost of the patch posted by Lukasz Majewski >> (https://patchwork.kernel.org/patch/2488211/). I have rebased this >> patch on top of my TMU re-structured patch series >> (http://lwn.net/Articles/548634/). Although I thought of handling >> regulator as one type of feature (newly added) but could not do >> so as regulator is a board/platform property and not SOC property so >> leaving the device tree to define and handle it. >> >> .../devicetree/bindings/thermal/exynos-thermal.txt | 4 ++++ >> drivers/thermal/samsung/exynos_tmu.c | 19 +++++++++++++++++++ >> 2 files changed, 23 insertions(+), 0 deletions(-) >> >> diff --git a/Documentation/devicetree/bindings/thermal/exynos-thermal.txt b/Documentation/devicetree/bindings/thermal/exynos-thermal.txt >> index 970eeba..ff62f7a 100644 >> --- a/Documentation/devicetree/bindings/thermal/exynos-thermal.txt >> +++ b/Documentation/devicetree/bindings/thermal/exynos-thermal.txt >> @@ -14,6 +14,9 @@ >> - interrupts : Should contain interrupt for thermal system >> - clocks : The main clock for TMU device >> - clock-names : Thermal system clock name >> +- vtmu-supply: This entry is optional and provides the regulator node supplying >> + voltage to TMU. If needed this entry can be placed inside >> + board/platform specific dts file. >> >> Example 1): >> >> @@ -25,6 +28,7 @@ Example 1): >> clocks = <&clock 383>; >> clock-names = "tmu_apbif"; >> status = "disabled"; >> + vtmu-supply = <&tmu_regulator_node>; >> }; >> >> Example 2): >> diff --git a/drivers/thermal/samsung/exynos_tmu.c b/drivers/thermal/samsung/exynos_tmu.c >> index 72446c9..b7c609a 100644 >> --- a/drivers/thermal/samsung/exynos_tmu.c >> +++ b/drivers/thermal/samsung/exynos_tmu.c >> @@ -32,6 +32,7 @@ >> #include >> #include >> #include >> +#include >> #include >> #include >> #include "exynos_thermal_common.h" >> @@ -52,6 +53,7 @@ >> * @clk: pointer to the clock structure. >> * @temp_error1: fused value of the first point trim. >> * @temp_error2: fused value of the second point trim. >> + * @regulator: pointer to the TMU regulator structure. >> * @reg_conf: pointer to structure to register with core thermal. >> */ >> struct exynos_tmu_data { >> @@ -65,6 +67,7 @@ struct exynos_tmu_data { >> struct mutex lock; >> struct clk *clk; >> u8 temp_error1, temp_error2; >> + struct regulator *regulator; >> struct thermal_sensor_conf *reg_conf; >> }; >> >> @@ -501,10 +504,23 @@ static int exynos_map_dt_data(struct platform_device *pdev) >> struct exynos_tmu_data *data = platform_get_drvdata(pdev); >> struct exynos_tmu_platform_data *pdata = data->pdata; >> struct resource res; >> + int ret; >> >> if (!data) >> return -ENODEV; >> >> + /* Try enabling the regulator if found */ >> + data->regulator = devm_regulator_get(&pdev->dev, "vtmu"); >> + if (!IS_ERR(data->regulator)) { >> + ret = regulator_enable(data->regulator); >> + if (ret) { >> + dev_err(&pdev->dev, "failed to enable vtmu\n"); >> + return ret; >> + } >> + } else { >> + dev_info(&pdev->dev, "Regulator node (vtmu) not found\n"); >> + } >> + >> data->id = of_alias_get_id(pdev->dev.of_node, "tmuctrl"); >> if (data->id < 0) >> data->id = 0; >> @@ -669,6 +685,9 @@ static int exynos_tmu_remove(struct platform_device *pdev) >> >> clk_unprepare(data->clk); >> >> + if (!IS_ERR(data->regulator)) >> + regulator_disable(data->regulator); >> + >> platform_set_drvdata(pdev, NULL); >> >> return 0; >> > > > -- > 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-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/