Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp866894ybl; Sat, 17 Aug 2019 12:28:32 -0700 (PDT) X-Google-Smtp-Source: APXvYqzbgRSMznfRQ74HRcxZMVZVvnVdKCdC3gQGnzJf09PcdpJUbQtYwuf+fnq7ws3NLS3BYZL8 X-Received: by 2002:a63:e213:: with SMTP id q19mr12953616pgh.180.1566070112317; Sat, 17 Aug 2019 12:28:32 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1566070112; cv=none; d=google.com; s=arc-20160816; b=RToubr4fQpN2DO4aW1QtH32nw4n/rhVsOrqQ9xFiW4oGKvyW6Pz3y3kTNzELCtlyfG 9ovV2Mo/dJSkRVb6l9+yWmYlA9+I36LOGZsMkp89JGT+drVIPaB8wuI7DPpxOMgFvHuN ZCL+u/V6nOUYWAEKLTcbloMiEf95wPA0M8M4CkYD92H2tL2KkqO70mQ5z4xjRWBwusz+ hq3xronDkkRjQnrk0zyyFC2/GnFlPDFXqeqXt1OzywlXsE2Ayhz8j///K9tuvPYysd1r 7EJQ6QZodF9jB5rcIMlSH2gEw+Uox++nabO7FsRX/enLY8fopJvSRhkExGLpvQS37gWR 3LeQ== 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 :in-reply-to:references:mime-version:dkim-signature; bh=L+hZKRR6Zg2z/tQRi2C4jMfVhdCq8oSEVLowVYJIhSc=; b=ehIUKTVLUCVA7vhvyVdQ4ZwtKpoiTfRX7UYZgLV74PrQkooalPXDxSl3ac7pkIzGYk 1PAzz6/qKKkxh/BkFWSHHG6A0C/OPZC/52p9IVUR5eq1PXtZISyeAmeuhoyzvfYhew4/ l5rEX0SKpURMmLb5mwALey/RfPmLgf3hWYng4fWz/e3Sz6D8uEe+E6+RzhdhFXxHNOTM yX1Cg9OSZck06AD0uQb/zInR2L36k7AuFEYRMDaE7PozH58geGoAn3F4EEJ8H5qbJosD XXJk/erg2SHtCCxLIexc04XNY6Xdta5bB8fvavR3AVSza3/9zdYGYQTPxQxfTu3SAWqf njEQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=bgGST+iX; 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=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 33si6580432plq.299.2019.08.17.12.28.17; Sat, 17 Aug 2019 12:28:32 -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=@kernel.org header.s=default header.b=bgGST+iX; 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=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726215AbfHQTZv (ORCPT + 99 others); Sat, 17 Aug 2019 15:25:51 -0400 Received: from mail.kernel.org ([198.145.29.99]:47570 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725929AbfHQTZu (ORCPT ); Sat, 17 Aug 2019 15:25:50 -0400 Received: from mail-qk1-f178.google.com (mail-qk1-f178.google.com [209.85.222.178]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id DCC2121773; Sat, 17 Aug 2019 19:25:49 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1566069950; bh=0NanKliApozmuL7V6nL8uKH5LTiliTZ9hOPreXVS068=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=bgGST+iX4UmnS3RqbOu/FfRSnf0c7+mYCCB8xVHjEcod3//fj+6o2zG1MpR2/BmIF wQgcm5O3WBckm7FwnV0gomnJn/VVVXFl/zHj2WWkecLSu901qGNgM7znj7t4gDjMEx ihM+ds/w+EeZDUEPWQqQH/13p80Go2CjQigV0YE0= Received: by mail-qk1-f178.google.com with SMTP id m10so7619127qkk.1; Sat, 17 Aug 2019 12:25:49 -0700 (PDT) X-Gm-Message-State: APjAAAVM193W5zvF+74UATNxRYAo8cYYAiTyj5bRv1WdvYwDLSC0/0ds setRVhg6U1zJf36nx9uAgVI0xxyEx518GARHow== X-Received: by 2002:a37:d8f:: with SMTP id 137mr13539239qkn.254.1566069949063; Sat, 17 Aug 2019 12:25:49 -0700 (PDT) MIME-Version: 1.0 References: <72bce036fa8cba3db6e5ba82249837ee46e9c077.1564091601.git.amit.kucheria@linaro.org> <20190816213648.GA10244@bogus> In-Reply-To: From: Rob Herring Date: Sat, 17 Aug 2019 14:25:36 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH 07/15] dt: thermal: tsens: Document interrupt support in tsens driver To: Amit Kucheria Cc: Linux Kernel Mailing List , linux-arm-msm , Bjorn Andersson , Eduardo Valentin , Andy Gross , Andy Gross , Daniel Lezcano , Mark Rutland , Zhang Rui , Linux PM list , DTML 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 On Fri, Aug 16, 2019 at 5:02 PM Amit Kucheria wrote: > > On Sat, Aug 17, 2019 at 3:06 AM Rob Herring wrote: > > > > On Fri, Jul 26, 2019 at 03:48:42AM +0530, Amit Kucheria wrote: > > > Define two new required properties to define interrupts and > > > interrupt-names for tsens. > > > > > > Signed-off-by: Amit Kucheria > > > --- > > > Documentation/devicetree/bindings/thermal/qcom-tsens.txt | 5 +++++ > > > 1 file changed, 5 insertions(+) > > > > > > diff --git a/Documentation/devicetree/bindings/thermal/qcom-tsens.txt b/Documentation/devicetree/bindings/thermal/qcom-tsens.txt > > > index 673cc1831ee9..3d3dd5dc6d36 100644 > > > --- a/Documentation/devicetree/bindings/thermal/qcom-tsens.txt > > > +++ b/Documentation/devicetree/bindings/thermal/qcom-tsens.txt > > > @@ -22,6 +22,8 @@ Required properties: > > > > > > - #thermal-sensor-cells : Should be 1. See ./thermal.txt for a description. > > > - #qcom,sensors: Number of sensors in tsens block > > > +- interrupts: Interrupts generated from Always-On subsystem (AOSS) > > > +- interrupt-names: The name of the interrupt e.g. "tsens0", "tsens1" > > > > How many interrupts? A name with just indices isn't too useful. > > Depending on the version of the tsens IP, there can be 1 (upper/lower > threshold), 2 (upper/lower + critical threshold) or 3 (upper/lower + > critical + zero degree) interrupts. This patch series only introduces > support for a single interrupt (upper/lower). I would expect a different compatible for each possibility. > I used the names tsens0, tsens1 to encapsulate the controller instance > since some SoCs have 1 controller, others have two. So we'll end up > with something like the following in DT: That's not really how *-names is supposed to work. The name is for identifying what is at each index. Or to put it another way, a driver should be able to use platform_get_irq_by_name(). So 'critical', 'zero' and something for the first one. > tsens0: thermal-sensor@c263000 { > compatible = "qcom,sdm845-tsens", "qcom,tsens-v2"; > reg = <0 0x0c263000 0 0x1ff>, /* TM */ > <0 0x0c222000 0 0x1ff>; /* SROT */ > #qcom,sensors = <13>; > interrupts = , > ; > interrupt-names = "tsens0", "tsens0-critical"; > #thermal-sensor-cells = <1>; > }; > > tsens1: thermal-sensor@c265000 { > compatible = "qcom,sdm845-tsens", "qcom,tsens-v2"; > reg = <0 0x0c265000 0 0x1ff>, /* TM */ > <0 0x0c223000 0 0x1ff>; /* SROT */ > #qcom,sensors = <8>; > interrupts = , > ; > interrupt-names = "tsens1", "tsens1-critical"; > #thermal-sensor-cells = <1>; > } > > Does that work? > > Regards, > Amit > > > > - Refer to Documentation/devicetree/bindings/nvmem/nvmem.txt to know how to specify > > > nvmem cells > > > > > > @@ -40,6 +42,9 @@ tsens0: thermal-sensor@c263000 { > > > reg = <0xc263000 0x1ff>, /* TM */ > > > <0xc222000 0x1ff>; /* SROT */ > > > #qcom,sensors = <13>; > > > + interrupts = ; > > > + interrupt-names = "tsens0"; > > > + > > > #thermal-sensor-cells = <1>; > > > }; > > > > > > -- > > > 2.17.1 > > >