On Thu, Feb 18, 2016 at 03:19:09PM -0300, Javier Martinez Canillas wrote:
> The Exynos Thermal Management Unit binding says that the vtmu-supply
> is optional but is listed in the required properties section. Add an
> optional properties section and move the regulator property there.
>
> Signed-off-by: Javier Martinez Canillas <javier@xxxxxxxxxxxxxxx>
> ---
>
> Documentation/devicetree/bindings/thermal/exynos-thermal.txt | 9 ++++++---
> 1 file changed, 6 insertions(+), 3 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/thermal/exynos-thermal.txt b/Documentation/devicetree/bindings/thermal/exynos-thermal.txt
> index faa62059b5c5..70b4c16c7ed8 100644
> --- a/Documentation/devicetree/bindings/thermal/exynos-thermal.txt
> +++ b/Documentation/devicetree/bindings/thermal/exynos-thermal.txt
> @@ -41,9 +41,6 @@
> for current TMU channel
> -- "tmu_sclk" clock for functional operation of the current TMU
> channel
> -- 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.
>
> The Exynos TMU supports generating interrupts when reaching given
> temperature thresholds. Number of supported thermal trip points depends
Where is this patch based on? I checked it on my fixes and linus
branches, also on linux-next 0308 branch, and none of those apply clean.
Can you please send this based on upstream kernel?
> @@ -65,6 +62,12 @@ Following properties are mandatory (depending on SoC):
> - samsung,tmu_default_temp_offset: Default temperature offset
> - samsung,tmu_cal_type: Callibration type
>
> +** Optional properties:
> +
> +- 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):
>
> tmu@100C0000 {
> --
> 2.5.0
>
--
To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
