From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.9 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id BA717C49ED7 for ; Fri, 20 Sep 2019 23:21:30 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 89B1B2190F for ; Fri, 20 Sep 2019 23:21:30 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=chromium.org header.i=@chromium.org header.b="QzLHfKdI" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2407131AbfITXV3 (ORCPT ); Fri, 20 Sep 2019 19:21:29 -0400 Received: from mail-pl1-f193.google.com ([209.85.214.193]:34181 "EHLO mail-pl1-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2407095AbfITXTy (ORCPT ); Fri, 20 Sep 2019 19:19:54 -0400 Received: by mail-pl1-f193.google.com with SMTP id d3so3899899plr.1 for ; Fri, 20 Sep 2019 16:19:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=message-id:mime-version:content-transfer-encoding:in-reply-to :references:cc:to:from:subject:user-agent:date; bh=x3KkooxIJHeflg3Q/MEdAWrgYVbuQ7dU5z8XbMOS1lc=; b=QzLHfKdIn3q1t4ZF2RMzkmMjfTHq/FprJnnZJs3zYFU7y2qEoRaLlRN0Y7Jq0AdNAC PDfaWzDyVmNcPgDP160yRKk+6DjeC8GYQEpY8ACjMkLlsfsLOmx+dwv1tNluk5ekf3ru UgXwy6ysHSMAxJ7o+Uw8r0YgF2N9y5ueHmVKo= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:mime-version :content-transfer-encoding:in-reply-to:references:cc:to:from:subject :user-agent:date; bh=x3KkooxIJHeflg3Q/MEdAWrgYVbuQ7dU5z8XbMOS1lc=; b=nQH8TD1qrwlhnfoFSbkddDRSkm/z1abn1hl/41eFDPmkwhWvOSDDNjUB9hDGJ1hlce z70EEYvllbnM7oCOYFLShpIWxCGvQn9Xesdjik335LVbvbe4X3ynZ6Ge3saJuxT1SOXa Iy25eq1c7xNlTW2JWTG6H7m4nDCZsasMYtA8VCVNiGV1p/3h9q/12xCgy8+2KXykmqS/ Okra/bH9gZmxSBTatcL1mHPIqkyN+aQFjOofi8g8Hx7iY0Jxf8mC2j/s8T6J8wsAvzjc INcvHLVGn3s9czo5fi3x952ok1wBswsXawC7buQCkXSj7+2yVG0j/KKKzuCzSgMbdaos ONmA== X-Gm-Message-State: APjAAAXG1oju113TXgvYxkiaf0FqXr6SFaUkrGO6sR9qjMBu747VV6LG f7j6uXP1FhWNTYeItFsA/9iCbA== X-Google-Smtp-Source: APXvYqw+23bVFXVYDopNzEoteLtijFTF7+FHjQV5JUkx0GnkKnOeZTAyxgjw8he9IKiO6G9R5MvM2g== X-Received: by 2002:a17:902:5a89:: with SMTP id r9mr18599724pli.206.1569021594105; Fri, 20 Sep 2019 16:19:54 -0700 (PDT) Received: from chromium.org ([2620:15c:202:1:fa53:7765:582b:82b9]) by smtp.gmail.com with ESMTPSA id a4sm2720148pgq.6.2019.09.20.16.19.53 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 20 Sep 2019 16:19:53 -0700 (PDT) Message-ID: <5d855e99.1c69fb81.1d457.733b@mx.google.com> Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable In-Reply-To: References: <5d854c82.1c69fb81.66e1f.96ab@mx.google.com> <5d854e1d.1c69fb81.4f771.9391@mx.google.com> Cc: Daniel Lezcano , Mark Rutland , Rob Herring , Zhang Rui , Andy Gross , Bjorn Andersson , Eduardo Valentin , linux-arm-msm , LKML , Brian Masney , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" To: Amit Kucheria From: Stephen Boyd Subject: Re: [PATCH v4 09/15] arm64: dts: msm8996: thermal: Add interrupt support User-Agent: alot/0.8.1 Date: Fri, 20 Sep 2019 16:19:52 -0700 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Quoting Amit Kucheria (2019-09-20 15:14:58) > On Fri, Sep 20, 2019 at 3:09 PM Stephen Boyd wrote: > > > > Ok so the plan is to change DT and then change it back? That sounds > > quite bad so please fix the thermal core to not care about this before > > applying these changes so that we don't churn DT. >=20 > Hi Stephen, >=20 > Our emails crossed paths. I think we could just make the property > optional so that we can remove the property completely for drivers > that support interrupts. Comments? OK. This means that the delay properties become irrelevant once an interrupt is there? I guess that's OK. My concern is that we need to choose one or the other when it would be simpler to have both and fallback to the delays so that DT migration strategies are purely additive. It's not like the delays aren't calculated to be those numbers anymore. They're just not going to be used. >=20 > That is a bigger change to the bindings and I don't want to hold the > tsens interrupt support hostage to agreement on this. Alright. I admit I haven't looked into the details but is it hard for some reason to make it use interrupts before delays?