Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp7942903imu; Fri, 28 Dec 2018 07:43:56 -0800 (PST) X-Google-Smtp-Source: ALg8bN41fzKCYv2sbVXFXlwmWHul7RqenTxfn8KEWaRdP0zT3zdbpA5aAIcn5Xnnkzl+jrBsJ61S X-Received: by 2002:a63:8ac4:: with SMTP id y187mr26952225pgd.446.1546011836416; Fri, 28 Dec 2018 07:43:56 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1546011836; cv=none; d=google.com; s=arc-20160816; b=yte8f18FrNL6POiu2KixLscQgOl/iThAzQI+6cK4WcVH0VZMwq1S+0BjO2P/XzSPOW jigK18KvPvdu5EwKozvl5lrxxqcKaTPM9dpJvzon4qLYrbQi9IacY2bmBchdQJOTU6K2 fcBLnjccSW82mTD3PfraIWi1Eqf8FQdNkFozvX75ictXSvqABXqoh12qGAYyFf+4fIKc 3xNx4U2SuKys365Ks7fcEfaKpMXONbIYNbIP59KuMEotugXqtbNd4nYw3rVfvXaAKUsT ZeKaiiQE/l3XAwZuarpTCTrCCUSpt6eadoPunWz9eWwnOa6Vys8/WMJ7z8W8ur9hSomc 4ncg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:dkim-signature:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=Fk25YwDk14iKImVfDRIFURu7Oc6aQaJL03IKPhsAmGk=; b=pj0xw59GfeN9/bn7+ToduNG9AYtKPOGxpgot3MyhLFJypS3BDpqRbN6RQ2KWfwrA9F xRx9Y7BUYnX4Jw4jZNoLS7Fy41A+HwWA5V2uHLcwrr7peYuJDiuH8pF5FdLLVlPtxdOw jiJ/qJgZ9Bm1hdP9LIIQfrSZ9saXZ+vAhOB/+DqPD+gd+NAtj59MXegzpJGWKYuPA6TK sSiWZOg/IvTmyVaKYE4rm8pkE59zKjsFB3Ec/IWrD0In2yXc+KyEJ5J31psv5qflHu1b fj7ZnIwOjgs/g5Jrrw/+2VCzm5DQCJMNuJftO4BT2Nk6zWWz+NXDeE5p7Sr3gwF+wXdw zYMg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@nvidia.com header.s=n1 header.b=Bp5+PyCl; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=nvidia.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 19si37490748pgp.186.2018.12.28.07.43.38; Fri, 28 Dec 2018 07:43:56 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@nvidia.com header.s=n1 header.b=Bp5+PyCl; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=nvidia.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731445AbeL1D2w (ORCPT + 99 others); Thu, 27 Dec 2018 22:28:52 -0500 Received: from hqemgate16.nvidia.com ([216.228.121.65]:8464 "EHLO hqemgate16.nvidia.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726054AbeL1D2w (ORCPT ); Thu, 27 Dec 2018 22:28:52 -0500 Received: from hqpgpgate101.nvidia.com (Not Verified[216.228.121.13]) by hqemgate16.nvidia.com (using TLS: TLSv1.2, DES-CBC3-SHA) id ; Thu, 27 Dec 2018 19:28:31 -0800 Received: from hqmail.nvidia.com ([172.20.161.6]) by hqpgpgate101.nvidia.com (PGP Universal service); Thu, 27 Dec 2018 19:28:47 -0800 X-PGP-Universal: processed; by hqpgpgate101.nvidia.com on Thu, 27 Dec 2018 19:28:47 -0800 Received: from [10.19.225.182] (10.124.1.5) by HQMAIL101.nvidia.com (172.20.187.10) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Fri, 28 Dec 2018 03:28:44 +0000 Subject: Re: [PATCH v1 01/12] of: Add bindings of thermtrip for Tegra soctherm To: Rob Herring CC: , , , , , , , References: <1545118484-23641-1-git-send-email-wni@nvidia.com> <1545118484-23641-3-git-send-email-wni@nvidia.com> <20181227230630.GA3659@bogus> From: Wei Ni Message-ID: <1441d2d1-acfa-7b8d-5ed8-c2ca257df05d@nvidia.com> Date: Fri, 28 Dec 2018 11:28:42 +0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 MIME-Version: 1.0 In-Reply-To: <20181227230630.GA3659@bogus> X-Originating-IP: [10.124.1.5] X-ClientProxiedBy: HQMAIL101.nvidia.com (172.20.187.10) To HQMAIL101.nvidia.com (172.20.187.10) Content-Type: text/plain; charset="utf-8" Content-Language: en-US Content-Transfer-Encoding: 7bit DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nvidia.com; s=n1; t=1545967711; bh=Fk25YwDk14iKImVfDRIFURu7Oc6aQaJL03IKPhsAmGk=; h=X-PGP-Universal:Subject:To:CC:References:From:Message-ID:Date: User-Agent:MIME-Version:In-Reply-To:X-Originating-IP: X-ClientProxiedBy:Content-Type:Content-Language: Content-Transfer-Encoding; b=Bp5+PyClnyLkednYdCv1i9I6UX65NiWS/hf1a6Yi+ynBe95/uoKFRMOiD4n88O4yp m3BpTdyuJkEIQDHaZOdoM9DxBQfxik+5DoPNpeQeutpXkGjqXKfGPirAqJpCmi7x8T eELhFTapdH7ZvVr2PTl4WIcFDlAiWB4FGoIonKmT4wTZlXimQ9w2yl0Nfz2g4+1XRY deAyTv1jOkT0ZRpwH+HbXFE2/f91gEG823Ydqeyf+eNo05kWZPpL2xGWEJfdBFLVXB eT9ktshASPGAUlayuyacEdBiyZxbY4zP1/ooiY7d/mbHynSSrTbXzX80W3UI3eT4P5 FskBe/P7Lj27A== Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 28/12/2018 7:06 AM, Rob Herring wrote: > On Tue, Dec 18, 2018 at 03:34:33PM +0800, Wei Ni wrote: >> Add optional property "nvidia,thermtrips". >> If present, these trips will be used as HW shutdown trips, >> and critical trips will be used as SW shutdown trips. >> >> Signed-off-by: Wei Ni >> --- >> .../bindings/thermal/nvidia,tegra124-soctherm.txt | 20 +++++++++++++++++--- >> 1 file changed, 17 insertions(+), 3 deletions(-) >> >> diff --git a/Documentation/devicetree/bindings/thermal/nvidia,tegra124-soctherm.txt b/Documentation/devicetree/bindings/thermal/nvidia,tegra124-soctherm.txt >> index b6c0ae53d4dc..ab66d6feab4b 100644 >> --- a/Documentation/devicetree/bindings/thermal/nvidia,tegra124-soctherm.txt >> +++ b/Documentation/devicetree/bindings/thermal/nvidia,tegra124-soctherm.txt >> @@ -55,10 +55,21 @@ Required properties : >> - #cooling-cells: Should be 1. This cooling device only support on/off state. >> See ./thermal.txt for a description of this property. >> >> +Optional properties: >> +- nvidia,thermtrips : When present, this property specifies the temperature at >> + which the soctherm hardware will assert the thermal trigger signal to the >> + Power Management IC, which can be configured to reset or shutdown the device. >> + It is an array of pairs where each pair represents a tsensor id followed by a >> + temperature in milli Celcius. In the absence of this property the critical >> + trip point will be used for thermtrip temperature. >> + >> Note: >> -- the "critical" type trip points will be set to SOC_THERM hardware as the >> -shut down temperature. Once the temperature of this thermal zone is higher >> -than it, the system will be shutdown or reset by hardware. >> +- the "critical" type trip points will be used to set the temperature at which >> +the SOC_THERM hardware will assert a thermal trigger if the "nvidia,thermtrips" >> +property is missing. When the thermtrips property is present, the breach of a >> +critical trip point is reported back to the thermal framework to implement >> +software shutdown. > > This hardly seems like a NVidia specific concept. A h/w shutdown > temperature... Come up with something common. Hi Rob, In current thermal framework, it doesn't support to set h/w shutdown trips, the "critical" trip is used for s/w shutdown. I noticed that in rockchip-thermal driver, it also used "rockchip,hw-tshut-temp" to set h/w shutdown temperature. > > Also, we already have a temperature table. Why do we need temperatures > in 2 places. Sorry, what do you mean temperature table? Do you mean the trip nodes? Thanks. Wei. > >> + >> - the "hot" type trip points will be set to SOC_THERM hardware as the throttle >> temperature. Once the the temperature of this thermal zone is higher >> than it, it will trigger the HW throttle event. >> @@ -79,6 +90,9 @@ Example : >> >> #thermal-sensor-cells = <1>; >> >> + nvidia,thermtrips = > + TEGRA124_SOCTHERM_SENSOR_GPU 103000>; >> + >> throttle-cfgs { >> /* >> * When the "heavy" cooling device triggered, >> -- >> 2.7.4 >>