From patchwork Tue Jul 31 18:45:53 2018 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Patchwork-Submitter: Matthias Kaehlcke X-Patchwork-Id: 10551185 X-Patchwork-Delegate: eduardo.valentin@ti.com Return-Path: Received: from mail.wl.linuxfoundation.org (pdx-wl-mail.web.codeaurora.org [172.30.200.125]) by pdx-korg-patchwork-2.web.codeaurora.org (Postfix) with ESMTP id 111B814E0 for ; Tue, 31 Jul 2018 18:46:51 +0000 (UTC) Received: from mail.wl.linuxfoundation.org (localhost [127.0.0.1]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id 023432B244 for ; Tue, 31 Jul 2018 18:46:51 +0000 (UTC) Received: by mail.wl.linuxfoundation.org (Postfix, from userid 486) id EA0242B2EC; Tue, 31 Jul 2018 18:46:50 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on pdx-wl-mail.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-7.9 required=2.0 tests=BAYES_00,MAILING_LIST_MULTI, RCVD_IN_DNSWL_HI autolearn=ham version=3.3.1 Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id 2B8BE2B2F0 for ; Tue, 31 Jul 2018 18:46:49 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1732088AbeGaU1z (ORCPT ); Tue, 31 Jul 2018 16:27:55 -0400 Received: from mail-pf1-f194.google.com ([209.85.210.194]:43648 "EHLO mail-pf1-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1732074AbeGaU1y (ORCPT ); Tue, 31 Jul 2018 16:27:54 -0400 Received: by mail-pf1-f194.google.com with SMTP id j26-v6so6524791pfi.10 for ; Tue, 31 Jul 2018 11:46:17 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=XWHD3U11wghvwRII1kRUIs8QoNbRmHkZbA9xigt5SRw=; b=FBduHDirNNwAgryL+NYDZPJQ6LTIHdqKefRQvStw11mU4Uosbd1ry/8LTVGEmH7dkF OMDAfgO8yXDFELouOOMgN/Do3wfpG+G4mRzFuFONrb9Fh2pNQbh89jmXviEHUbsdgunB DEfl/l5sm2ChNdk7ipWkf4c9PYM3G8Mvcq+c5IwDX0abo9+McA3eQApG/fFh9SUEDY/V s4HPAtKtllcwEd2GhZ9OF3RwSe4oKvh6vqfgBtRg25KAGpGIZsOjdqcF5Oudnc3pT+7p QMLdHLsAj2qb8KVewubnfbLJZ83b4Nw2waWT0kHRvQO8xiIqBNMURz/EzVdI+drQD/Gc N7ng== X-Gm-Message-State: AOUpUlEA6LNDQfaGEFch7Gegh+VTPuSNUITdVnSe4TjHMEdOM3vJrFHK ZF0nvA+YB8sK4YvPkHRkn7W9RQ== X-Google-Smtp-Source: AAOMgpftK6VTik1iP9nFlcx7ntOye747JELX84OSDJcz9G0DVVKUu/tcmDwuawxnh1cK9zEp6EzsSQ== X-Received: by 2002:a63:6441:: with SMTP id y62-v6mr21271003pgb.240.1533062776409; Tue, 31 Jul 2018 11:46:16 -0700 (PDT) Received: from mka.mtv.corp.google.com ([2620:15c:202:1:b6af:f85:ed6c:ac6a]) by smtp.gmail.com with ESMTPSA id b21-v6sm4981683pgw.79.2018.07.31.11.46.14 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 31 Jul 2018 11:46:15 -0700 (PDT) From: Matthias Kaehlcke To: Andy Gross , David Brown , Rob Herring , Mark Rutland , Catalin Marinas , Will Deacon , Zhang Rui , Eduardo Valentin Cc: linux-soc@vger.kernel.org, linux-arm-msm@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, linux-pm@vger.kernel.org, David Collins , Douglas Anderson , Stephen Boyd , Matthias Kaehlcke Subject: [PATCH v6 2/5] dt-bindings: thermal: qcom-spmi-temp-alarm: Improve thermal zone in example Date: Tue, 31 Jul 2018 11:45:53 -0700 Message-Id: <20180731184556.169290-2-mka@chromium.org> X-Mailer: git-send-email 2.18.0.345.g5c9ce644c3-goog In-Reply-To: <20180731184556.169290-1-mka@chromium.org> References: <20180731184556.169290-1-mka@chromium.org> MIME-Version: 1.0 Sender: linux-pm-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-pm@vger.kernel.org X-Virus-Scanned: ClamAV using ClamSMTP The current example for a thermal zone isn't very useful as reference since it would result in a hardware shutdown at 145°C, instead of allowing the system to try to shutdown gracefully. Without an ADC channel a maximum of two trip points is useful in practice for this sensor, with temperatures corresponding to the stage 1 and stage 2 'hardware trip points'. A critical trip point at stage 2 may allow the system to shutdown before a hardware shutdown at stage 3 kicks in. It should be noted though that by default the chip performs a 'partial shutdown' when the temperature reaches stage 2, which may prevent an orderly shutdown. The 'partial shutdown' can be disabled by software. Signed-off-by: Matthias Kaehlcke Reviewed-by: Douglas Anderson --- Changes in v6: - patch added to the series --- .../bindings/thermal/qcom-spmi-temp-alarm.txt | 11 +++-------- 1 file changed, 3 insertions(+), 8 deletions(-) diff --git a/Documentation/devicetree/bindings/thermal/qcom-spmi-temp-alarm.txt b/Documentation/devicetree/bindings/thermal/qcom-spmi-temp-alarm.txt index 86fb41fe772f..0273a92a2a84 100644 --- a/Documentation/devicetree/bindings/thermal/qcom-spmi-temp-alarm.txt +++ b/Documentation/devicetree/bindings/thermal/qcom-spmi-temp-alarm.txt @@ -35,19 +35,14 @@ Example: thermal-sensors = <&pm8941_temp>; trips { - passive { - temperature = <1050000>; + stage1 { + temperature = <105000>; hysteresis = <2000>; type = "passive"; }; - alert { + stage2 { temperature = <125000>; hysteresis = <2000>; - type = "hot"; - }; - crit { - temperature = <145000>; - hysteresis = <2000>; type = "critical"; }; };