Received: by 2002:ac0:a581:0:0:0:0:0 with SMTP id m1-v6csp993889imm; Tue, 3 Jul 2018 03:46:18 -0700 (PDT) X-Google-Smtp-Source: ADUXVKJ4ayB864Qn8fJyK/xSfcdZXLjPVGZ+SSj0wnXAeR0mNiZZptVGRXGxygSbSIF4MrX945VO X-Received: by 2002:a63:9311:: with SMTP id b17-v6mr25115364pge.261.1530614778183; Tue, 03 Jul 2018 03:46:18 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1530614778; cv=none; d=google.com; s=arc-20160816; b=P7S6k1FLz9GgTOx6r68hpxbAgceby78Ly+aGM1kAVM/hVr4fZub+uD+RPES812d+u0 bITfGAYlSdg+5LhIyr6IJgX9MMDYVQpoYn+Gk4ugxeKiPbDqqKJji5inRADn8u5vb6v7 eiCGSo/LFX9BAt/HTF11MGTz6C2JRvnrH17Qz7MoUJ8MRsoy53cGGeecSvpIc1mokN5o pCjNGQp3cj2hEo8otrO3tmiT6Y4vUBajvw0w65RqqdF4kn9XJTHFOX5iYAHf50UVkePP QQ5DuMnPVACUxdziMoSPomqv8E/0OzC1q3LCjTTkZ6siXiI1M6D+S+vvcuTbOYwDlZX3 MrdA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :references:in-reply-to:mime-version:dkim-signature :arc-authentication-results; bh=phjj0F3sehQjIGOvRH/8aGkH+FLYMb1adDuz0PMuALw=; b=pW6Vivqds5a28ModitUl1lnjRsnMXQZC7PkKFt2NUgBMBMEiCj54O5dmZzqzmCzQ6S uoOsPtTGUnCxXuVk69iI4Zu3Mi1Q4Og7knqOQa/3yQvKaYEaX1p5XlzIwj72F5rhTG/q DBmI6UsoogmzhEyMNJcVENtCbeWhJ+sUeL/tWrSUDtRwty8VQI2WtYRiVsiSw1T7fq/w zibf8Y4Z7YZbbLQ/d8SSdsDLBhMDyZpc594gQlXAOvZdfvejDD4LW3YOXJAamUAO8Rjv mQgkDkYVNC/TxP0QPeah2s/al8HbkN/RRcaCFZXu0uBJ1ipRJXAmAB+IdBm/8/vKS3hy 0VRA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@broadcom.com header.s=google header.b=XNw+CH9q; 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=QUARANTINE sp=QUARANTINE dis=NONE) header.from=broadcom.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id q130-v6si732063pgq.526.2018.07.03.03.46.03; Tue, 03 Jul 2018 03:46:18 -0700 (PDT) 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=@broadcom.com header.s=google header.b=XNw+CH9q; 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=QUARANTINE sp=QUARANTINE dis=NONE) header.from=broadcom.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752612AbeGCKpX (ORCPT + 99 others); Tue, 3 Jul 2018 06:45:23 -0400 Received: from mail-oi0-f65.google.com ([209.85.218.65]:41572 "EHLO mail-oi0-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752435AbeGCKpU (ORCPT ); Tue, 3 Jul 2018 06:45:20 -0400 Received: by mail-oi0-f65.google.com with SMTP id k12-v6so2808487oiw.8 for ; Tue, 03 Jul 2018 03:45:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=broadcom.com; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=phjj0F3sehQjIGOvRH/8aGkH+FLYMb1adDuz0PMuALw=; b=XNw+CH9q4lr0sNVaROkQKaYYWCllRINaOcu0FWk/lCctPHq+yTTNjgpdFti3a6u0T+ wBQBKhAZTnk0uoF+enrp7ZC1EXdpJDrZcp6RuTuVULgHvrTD8DIQPonc/OgbnXQ5nDuM wY8SkaRDePVQGeHa6wq4KDKAOeUQbfBsbpGgM= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=phjj0F3sehQjIGOvRH/8aGkH+FLYMb1adDuz0PMuALw=; b=O/hoLr44zlkkR9pDi2P+0QZmlvYTY6R0Bems/SDRhPDptRPp67TQFGhFjn0D97Mj5s reAQkjWrFMH10eNADE694nNttD8YTbBphZEAa6dxVa/cFKUmKTZJcIli0+j5X/yTaqcC PcbfjgihgwOmNjXJMLl15QaFD9VAlqkSRHjz8P8iq7sZt4ZkGY4F4wCegj8z5ZYJHwpY BBG3gqby8VXw+pdDjwBA78Zu3mPE85jAtx2uf8EsM0/XTSs3xCR9lw/K9lBH8M9f6ZZU edW+MghdkZU5if5R6uzi7HoizWtQX7BlmC2MvZ0b7/dLVGz+wqmZRc8PGdFaqEOFkZQw XxXw== X-Gm-Message-State: APt69E22CkBimVVxfF77g18OI3KDBrG8j560VkYmdSoumG1V3eaPyqXN dAqm3vZQDoUGt38oo4skgBZcXzgGulqPVI2L42cvDQ== X-Received: by 2002:aca:5e07:: with SMTP id s7-v6mr20609047oib.353.1530614719785; Tue, 03 Jul 2018 03:45:19 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a9d:51d2:0:0:0:0:0 with HTTP; Tue, 3 Jul 2018 03:45:19 -0700 (PDT) In-Reply-To: References: <1529310679-13482-1-git-send-email-srinath.mannam@broadcom.com> <1529310679-13482-2-git-send-email-srinath.mannam@broadcom.com> <20180620195214.GA10436@rob-hp-laptop> From: Srinath Mannam Date: Tue, 3 Jul 2018 16:15:19 +0530 Message-ID: Subject: Re: [PATCH v2 1/3] dt-bindings: thermal: Add binding document for SR thermal To: Rob Herring Cc: Zhang Rui , Eduardo Valentin , Mark Rutland , devicetree@vger.kernel.org, Linux Kernel Mailing List , BCM Kernel Feedback , Pramod Kumar Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Rob, Kindly provide your feedback. Regards, Srinath. On Fri, Jun 22, 2018 at 11:21 AM, Srinath Mannam wrote: > Hi Rob, > > Please find my comments for the reason to have multiple DT nodes. > > On Thu, Jun 21, 2018 at 1:22 AM, Rob Herring wrote: >> On Mon, Jun 18, 2018 at 02:01:17PM +0530, Srinath Mannam wrote: >>> From: Pramod Kumar >>> >>> Add binding document for supported thermal implementation >>> in Stingray. >>> >>> Signed-off-by: Pramod Kumar >>> Reviewed-by: Ray Jui >>> Reviewed-by: Scott Branden >>> Reviewed-by: Srinath Mannam >>> --- >>> .../bindings/thermal/brcm,sr-thermal.txt | 45 ++++++++++++++++++++++ >>> 1 file changed, 45 insertions(+) >>> create mode 100644 Documentation/devicetree/bindings/thermal/brcm,sr-thermal.txt >>> >>> diff --git a/Documentation/devicetree/bindings/thermal/brcm,sr-thermal.txt b/Documentation/devicetree/bindings/thermal/brcm,sr-thermal.txt >>> new file mode 100644 >>> index 0000000..33f9e11 >>> --- /dev/null >>> +++ b/Documentation/devicetree/bindings/thermal/brcm,sr-thermal.txt >>> @@ -0,0 +1,45 @@ >>> +* Broadcom Stingray Thermal >>> + >>> +This binding describes thermal sensors that is part of Stingray SoCs. >>> + >>> +Required properties: >>> +- compatible : Must be "brcm,sr-thermal" >>> +- reg : memory where tmon data will be available. >>> + >>> +Example: >>> + tmons { >>> + compatible = "simple-bus"; >>> + #address-cells = <1>; >>> + #size-cells = <1>; >>> + ranges; >>> + >>> + tmon_ihost0: thermal@8f100000 { >>> + compatible = "brcm,sr-thermal"; >>> + reg = <0x8f100000 0x4>; >>> + }; >> >> You still haven't given me a compelling reason why you need a node per >> register. >> >> You have a single range of registers. Make this 1 node. >> > > We Have two reasons to have multiple nodes.. > 1. Our chip has multiple functional blocks. Each functional block has > its own thermal zone. > Functional blocks and their thermal zones enabled/disabled based on end product. > Few functional blocks need to disabled for few products so thermal > zones also need to disable. > In that case, nodes of specific thermal zones are removed from DTS > file of corresponding product. > > 2. Thermal framework provides sysfs interface to configure thermal > zones and read temperature of thermal zone. > To configure individual thermal zone, we need to have separate DT node. > Same to read temperature of individual thermal zone. > Ex: To read temperature of thermal zone 0. > cat /sys/class/thermal/thermal_zone0/temp > To configure trip temperature of thermal zone 0. > echo 110000 > /sys/class/thermal/thermal_zone0/trip_point_0_temp > > Also to avoid driver source change for the multiple products it is > clean to have multiple DT nodes. > >> Rob