From: Wei Ni <wni@nvidia.com> To: edubezval@gmail.com, thierry.reding@gmail.com, robh+dt@kernel.org, rui.zhang@intel.com Cc: MLongnecker@nvidia.com, swarren@wwwdotorg.org, mikko.perttunen@kapsi.fi, linux-tegra@vger.kernel.org, linux-pm@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, Wei Ni <wni@nvidia.com> Subject: [PATCH v5 08/11] arm64: tegra: set hot trips for Tegra132 Date: Wed, 11 May 2016 18:20:23 +0800 [thread overview] Message-ID: <1462962026-19653-9-git-send-email-wni@nvidia.com> (raw) In-Reply-To: <1462962026-19653-1-git-send-email-wni@nvidia.com> Enable throttle function for SOC_THERM. Set "hot" trips for cpu and gpu thermal zones, which can trigger the SOC_THERM hardware throttle. Signed-off-by: Wei Ni <wni@nvidia.com> --- arch/arm64/boot/dts/nvidia/tegra132.dtsi | 41 +++++++++++++++++++++++++------- 1 file changed, 32 insertions(+), 9 deletions(-) diff --git a/arch/arm64/boot/dts/nvidia/tegra132.dtsi b/arch/arm64/boot/dts/nvidia/tegra132.dtsi index a3889e930010..3f3a46a4bd01 100644 --- a/arch/arm64/boot/dts/nvidia/tegra132.dtsi +++ b/arch/arm64/boot/dts/nvidia/tegra132.dtsi @@ -729,7 +729,9 @@ soctherm: thermal-sensor@700e2000 { compatible = "nvidia,tegra132-soctherm"; - reg = <0x0 0x700e2000 0x0 0x600>; + reg = <0x0 0x700e2000 0x0 0x600 /* 0: SOC_THERM reg_base */ + 0x0 0x70040000 0x0 0x200>; /* 2: CCROC reg_base */ + reg-names = "soctherm-reg", "ccroc-reg"; interrupts = <GIC_SPI 48 IRQ_TYPE_LEVEL_HIGH>; clocks = <&tegra_car TEGRA124_CLK_TSENSOR>, <&tegra_car TEGRA124_CLK_SOC_THERM>; @@ -737,6 +739,15 @@ resets = <&tegra_car 78>; reset-names = "soctherm"; #thermal-sensor-cells = <1>; + + throttle-cfgs { + throttle_heavy: heavy { + nvidia,priority = <100>; + nvidia,cpu-throt-level = <TEGRA_SOCTHERM_THROT_LEVEL_HIGH>; + + #cooling-cells = <2>; + }; + }; }; thermal-zones { @@ -753,13 +764,19 @@ hysteresis = <1000>; type = "critical"; }; + + cpu_throttle_trip: throttle-trip { + temperature = <102000>; + hysteresis = <1000>; + type = "hot"; + }; }; cooling-maps { - /* - * There are currently no cooling maps, - * because there are no cooling devices. - */ + map0 { + trip = <&cpu_throttle_trip>; + cooling-device = <&throttle_heavy 1 1>; + }; }; }; mem { @@ -797,13 +814,19 @@ hysteresis = <1000>; type = "critical"; }; + + gpu_throttle_trip: throttle-trip { + temperature = <99000>; + hysteresis = <1000>; + type = "hot"; + }; }; cooling-maps { - /* - * There are currently no cooling maps, - * because there are no cooling devices. - */ + map0 { + trip = <&gpu_throttle_trip>; + cooling-device = <&throttle_heavy 1 1>; + }; }; }; pllx { -- 1.9.1
WARNING: multiple messages have this Message-ID (diff)
From: Wei Ni <wni@nvidia.com> To: <edubezval@gmail.com>, <thierry.reding@gmail.com>, <robh+dt@kernel.org>, <rui.zhang@intel.com> Cc: <MLongnecker@nvidia.com>, <swarren@wwwdotorg.org>, <mikko.perttunen@kapsi.fi>, <linux-tegra@vger.kernel.org>, <linux-pm@vger.kernel.org>, <devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>, Wei Ni <wni@nvidia.com> Subject: [PATCH v5 08/11] arm64: tegra: set hot trips for Tegra132 Date: Wed, 11 May 2016 18:20:23 +0800 [thread overview] Message-ID: <1462962026-19653-9-git-send-email-wni@nvidia.com> (raw) In-Reply-To: <1462962026-19653-1-git-send-email-wni@nvidia.com> Enable throttle function for SOC_THERM. Set "hot" trips for cpu and gpu thermal zones, which can trigger the SOC_THERM hardware throttle. Signed-off-by: Wei Ni <wni@nvidia.com> --- arch/arm64/boot/dts/nvidia/tegra132.dtsi | 41 +++++++++++++++++++++++++------- 1 file changed, 32 insertions(+), 9 deletions(-) diff --git a/arch/arm64/boot/dts/nvidia/tegra132.dtsi b/arch/arm64/boot/dts/nvidia/tegra132.dtsi index a3889e930010..3f3a46a4bd01 100644 --- a/arch/arm64/boot/dts/nvidia/tegra132.dtsi +++ b/arch/arm64/boot/dts/nvidia/tegra132.dtsi @@ -729,7 +729,9 @@ soctherm: thermal-sensor@700e2000 { compatible = "nvidia,tegra132-soctherm"; - reg = <0x0 0x700e2000 0x0 0x600>; + reg = <0x0 0x700e2000 0x0 0x600 /* 0: SOC_THERM reg_base */ + 0x0 0x70040000 0x0 0x200>; /* 2: CCROC reg_base */ + reg-names = "soctherm-reg", "ccroc-reg"; interrupts = <GIC_SPI 48 IRQ_TYPE_LEVEL_HIGH>; clocks = <&tegra_car TEGRA124_CLK_TSENSOR>, <&tegra_car TEGRA124_CLK_SOC_THERM>; @@ -737,6 +739,15 @@ resets = <&tegra_car 78>; reset-names = "soctherm"; #thermal-sensor-cells = <1>; + + throttle-cfgs { + throttle_heavy: heavy { + nvidia,priority = <100>; + nvidia,cpu-throt-level = <TEGRA_SOCTHERM_THROT_LEVEL_HIGH>; + + #cooling-cells = <2>; + }; + }; }; thermal-zones { @@ -753,13 +764,19 @@ hysteresis = <1000>; type = "critical"; }; + + cpu_throttle_trip: throttle-trip { + temperature = <102000>; + hysteresis = <1000>; + type = "hot"; + }; }; cooling-maps { - /* - * There are currently no cooling maps, - * because there are no cooling devices. - */ + map0 { + trip = <&cpu_throttle_trip>; + cooling-device = <&throttle_heavy 1 1>; + }; }; }; mem { @@ -797,13 +814,19 @@ hysteresis = <1000>; type = "critical"; }; + + gpu_throttle_trip: throttle-trip { + temperature = <99000>; + hysteresis = <1000>; + type = "hot"; + }; }; cooling-maps { - /* - * There are currently no cooling maps, - * because there are no cooling devices. - */ + map0 { + trip = <&gpu_throttle_trip>; + cooling-device = <&throttle_heavy 1 1>; + }; }; }; pllx { -- 1.9.1
next prev parent reply other threads:[~2016-05-11 10:20 UTC|newest] Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-05-11 10:20 [PATCH v5 00/11] Add HW throttle for Tegra soctherm Wei Ni 2016-05-11 10:20 ` Wei Ni 2016-05-11 10:20 ` [PATCH v5 03/11] thermal: tegra: add hw-throttle for Tegra132 Wei Ni 2016-05-11 10:20 ` Wei Ni 2016-05-11 10:20 ` [PATCH v5 04/11] arm: tegra: set critical trips for Tegra124 Wei Ni 2016-05-11 10:20 ` Wei Ni 2016-05-11 10:20 ` [PATCH v5 05/11] arm: tegra: set hot " Wei Ni 2016-05-11 10:20 ` Wei Ni [not found] ` <1462962026-19653-1-git-send-email-wni-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org> 2016-05-11 10:20 ` [PATCH v5 01/11] of: Add bindings of hw throttle for Tegra soctherm Wei Ni 2016-05-11 10:20 ` Wei Ni 2016-05-16 15:01 ` Rob Herring 2016-05-11 10:20 ` [PATCH v5 02/11] thermal: tegra: add hw-throttle function Wei Ni 2016-05-11 10:20 ` Wei Ni 2016-05-11 10:20 ` [PATCH v5 06/11] arm64: tegra: use tegra132-soctherm for Tegra132 Wei Ni 2016-05-11 10:20 ` Wei Ni 2016-05-26 9:42 ` [PATCH v5 00/11] Add HW throttle for Tegra soctherm Wei Ni 2016-05-26 9:42 ` Wei Ni 2016-08-19 7:15 ` Zhang Rui [not found] ` <1471590924.2691.34.camel-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org> 2016-08-31 3:07 ` Wei Ni 2016-08-31 3:07 ` Wei Ni 2016-05-11 10:20 ` [PATCH v5 07/11] arm64: tegra: set critical trips for Tegra132 Wei Ni 2016-05-11 10:20 ` Wei Ni 2016-05-11 10:20 ` Wei Ni [this message] 2016-05-11 10:20 ` [PATCH v5 08/11] arm64: tegra: set hot " Wei Ni 2016-05-11 10:20 ` [PATCH v5 09/11] arm64: tegra: add soctherm node for Tegra210 Wei Ni 2016-05-11 10:20 ` Wei Ni 2016-05-11 10:20 ` [PATCH v5 10/11] arm64: tegra: set critical trips " Wei Ni 2016-05-11 10:20 ` Wei Ni 2016-05-11 10:20 ` [PATCH v5 11/11] arm64: tegra: set hot " Wei Ni 2016-05-11 10:20 ` Wei Ni
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=1462962026-19653-9-git-send-email-wni@nvidia.com \ --to=wni@nvidia.com \ --cc=MLongnecker@nvidia.com \ --cc=devicetree@vger.kernel.org \ --cc=edubezval@gmail.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-pm@vger.kernel.org \ --cc=linux-tegra@vger.kernel.org \ --cc=mikko.perttunen@kapsi.fi \ --cc=robh+dt@kernel.org \ --cc=rui.zhang@intel.com \ --cc=swarren@wwwdotorg.org \ --cc=thierry.reding@gmail.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.