Received: by 2002:a05:6358:11c7:b0:104:8066:f915 with SMTP id i7csp2061735rwl; Sun, 26 Mar 2023 15:06:29 -0700 (PDT) X-Google-Smtp-Source: AKy350aZhzKr3MmtwQbYfOYAe325VDng7mm5Niknmf/lwDQwuvpRYfuwMdP1WXxUJR4SO8ff2gN/ X-Received: by 2002:a17:902:e543:b0:19e:665b:2514 with SMTP id n3-20020a170902e54300b0019e665b2514mr11123394plf.43.1679868388937; Sun, 26 Mar 2023 15:06:28 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1679868388; cv=none; d=google.com; s=arc-20160816; b=b5eG04fWIC3kVMNnvp3b0m7n8UBJlt7/TGthJzFoQ6rJYCwSFm+WNdzhFc8lkQQAm/ 1gLkLK8cPStij1JfDrWeEH9UqE0BlVJD7hkV1G6QhJl8kTVioqtxJdPEhsWEP+OxvD6F 9lxOY8W63/wZ3gjexPXfLyJHISN9lp9nWuPgh/01oIfw0VC+97IlWzSwXRxulJtkIsZT 1cCpEzDf6EoN+NRo4p7ce+1QKEKWKtVksAYXIDt6LUWX+unruCMKerUyca8Xg4FQiai0 XF/BDgYeXnFmMOYY203xoDUl6LLRvFyzLCJVJQpXRK0SHd7e1Y2aMs9Vp4TOBnTGscLK TkQg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=6dnlWUNBhdNVErKLJFu8u1ZEtEftWkVM7mHppRzmj0A=; b=Z4EXZd8Xaikd6rPLTPLmY85b1peHcoULeLPO8pW6WpUZvhInFX44gYfKa0luQp2yT4 XveRbkrpMopG+YbvHtGt/6w5p7HX/sI1ERT+x7y4YSFh7gawuBoRwXqhYzVHWr0fDz3I PTLXs9zM3cQglb1nwEvjmD5m2vSeGRBQEyR/cZpdEQrrOTCXWm5hBchKEWnjnLm9j/dq I2FRlQKxwYN7kSf9ENt8fe4oIjAZYX6f7gU3XFpDNDnw0cKd+NT19SZQeZ87d82vYfvR Nerf+RHxGXZLunlBRrHRv2VIme5cF+NDUnjqbEkhAFwINEAXhfE0t499xDt1FBHKWywT nBvw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=BwOtjOY1; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id l11-20020a170903244b00b001a0403b77c9si28488259pls.42.2023.03.26.15.06.17; Sun, 26 Mar 2023 15:06:28 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=BwOtjOY1; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231840AbjCZWDL (ORCPT + 99 others); Sun, 26 Mar 2023 18:03:11 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36154 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229621AbjCZWDJ (ORCPT ); Sun, 26 Mar 2023 18:03:09 -0400 Received: from mail-yb1-xb33.google.com (mail-yb1-xb33.google.com [IPv6:2607:f8b0:4864:20::b33]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id DE8FE2688 for ; Sun, 26 Mar 2023 15:03:08 -0700 (PDT) Received: by mail-yb1-xb33.google.com with SMTP id p15so8203766ybl.9 for ; Sun, 26 Mar 2023 15:03:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; t=1679868188; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=6dnlWUNBhdNVErKLJFu8u1ZEtEftWkVM7mHppRzmj0A=; b=BwOtjOY19Rbe5MMDNIggqEiiDqqh703Hg75oWLfRkIQH61644JK9CUmAzLnuRZjq2I GvJc7eDaoDYJ7eunwPV5ypZcG3BCsCjKiRA9UbDOhEINzogt9NPzK/7sL9BOgiRicI73 QnMwuzC53se0SOUHVwNa/RpYP+bfUQi3kMu+r96LR+u1Yda4X7D6ML2nVf5x8ecmg7E3 b4u7tjceIP/l/WG4hW5spSy/9H+wZ+ydUku/zBdcDRNNm4gx/M34+N6XGECxxZW7FX33 IQ/vN4dazau7x7pt5J7Z6B9/kxEqUs5af9tRQPJOrwWFlaLbLnVuBG04bE0bvz0zMj7T OZ0Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1679868188; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=6dnlWUNBhdNVErKLJFu8u1ZEtEftWkVM7mHppRzmj0A=; b=5mV7blS5IZhY9xy+qz9mNLABEqfdgRAhgCIy6ECpV30HIl0+dhdnj5GXey8TCRuzKn fAPjjUfsbuUG7v9nCeW2yym2u6DOyUPpSeufGScYVv3Ziri5DPfYMpw3tcrV4vHj6386 +GBzIM/8ctMA+ohj+udQwtp81kr0bnxgaACTokODOKy1n+b2U0G+N9DpC1XK3cS4WisG yO/j356eRPNfyOVOdFyE35WVAVz9NcQtifgCRNJIxWCA7Ikrzwq5erBDuNwehvg2lkrK xB7HPND8yFvL0bSVQyTyx7yNzx4b4bIM3ZsLldv+E0hKgausoBSKRpgkUSbUJkzYzvsz ZtIw== X-Gm-Message-State: AAQBX9d24TbRDLKohNxA40v/rGzJurl+ariD+nbRiNMi5M4xl0JVBQyQ jvfV2Lbe3IvXsYRmCBHHyEygJxlokHr0KhhBv8ge/g== X-Received: by 2002:a05:6902:168d:b0:b6c:2d28:b3e7 with SMTP id bx13-20020a056902168d00b00b6c2d28b3e7mr5687001ybb.9.1679868188072; Sun, 26 Mar 2023 15:03:08 -0700 (PDT) MIME-Version: 1.0 References: <20230326091605.18908-1-krzysztof.kozlowski@linaro.org> <83b657c3-5a78-1c81-fea5-5679a30bd517@linaro.org> In-Reply-To: <83b657c3-5a78-1c81-fea5-5679a30bd517@linaro.org> From: Dmitry Baryshkov Date: Mon, 27 Mar 2023 01:02:57 +0300 Message-ID: Subject: Re: [PATCH v2] arm64: dts: qcom: sdm630: move DSI opp-table out of soc node To: Krzysztof Kozlowski Cc: Andy Gross , Bjorn Andersson , Konrad Dybcio , Rob Herring , Krzysztof Kozlowski , linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-0.2 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, 26 Mar 2023 at 13:13, Krzysztof Kozlowski wrote: > > On 26/03/2023 12:03, Dmitry Baryshkov wrote: > > On Sun, 26 Mar 2023 at 12:22, Krzysztof Kozlowski > > wrote: > >> > >> On 26/03/2023 11:21, Dmitry Baryshkov wrote: > >>> On Sun, 26 Mar 2023 at 12:16, Krzysztof Kozlowski > >>> wrote: > >>>> > >>>> The soc node is supposed to have only device nodes with MMIO addresses, > >>>> so move the DSI OPP out of it (it is used also by second DSI1 on > >>>> SDM660): > >>> > >>> This raises a question: would it make sense to add /opps to handle all > >>> opp tables? > >> > >> We didn't add it to any other cases like this (and we already fixed all > >> other boards), so why now? We can but it is a bit late for it. > > > > Because nobody expressed this idea beforehand? I'm not insisting here, > > you have a better understanding of DT. Just wondering if it makes > > sense. > > It will not change much of ordering - all nodes will be close to each > other anyway (opp-table-XYZ), thus is rather a matter of readability and > subjective preference. No other platforms have "opps" or "opp-tables". Ack, thanks for the explanation. Reviewed-by: Dmitry Baryshkov -- With best wishes Dmitry