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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 7167BC7619A for ; Sun, 26 Mar 2023 09:22:28 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231904AbjCZJW1 (ORCPT ); Sun, 26 Mar 2023 05:22:27 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:43098 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231873AbjCZJWZ (ORCPT ); Sun, 26 Mar 2023 05:22:25 -0400 Received: from mail-ed1-x52a.google.com (mail-ed1-x52a.google.com [IPv6:2a00:1450:4864:20::52a]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 94C9893F2 for ; Sun, 26 Mar 2023 02:22:23 -0700 (PDT) Received: by mail-ed1-x52a.google.com with SMTP id eg48so24162962edb.13 for ; Sun, 26 Mar 2023 02:22:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; t=1679822542; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=5rXoV9ZT/umKedJfUsdr0K9co5AscuT4z2LTYT9lVJE=; b=hYCTtRTQIwtNTBhlkzPyuFFAPazi45fgs2gh50HZ0mVZH3WeBAIUhsM3JvkTriUX0q gEs+Hc+UXyBAr57Mwt+AwZ6i+yvzBLvDvMgjpyIaDswBAncOimGd8ldcdooTX3qw6spO AXymcTg1sLL/T1Jc19eSPapIJIVObgxB8bNp0+yNwOJGdsCKSAvGFpY/XVeYI8SnrMSH R0sb/nvRVPxrHg2OGTrG2zQ22HpPzaDqi2dMh9K10MVzLqo8UJGlqJzzp+xtVhyNI4CY higkRFpYE6RvTrHWqo5f9qUEtW/HlImSaYrJAbSt8hW0r5ePGrZXl0aQCav2zEOgJuCW yccw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1679822542; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=5rXoV9ZT/umKedJfUsdr0K9co5AscuT4z2LTYT9lVJE=; b=XadpYk/qWcHV1xGbvJivzTGSmxRF+zlGyvkyZkSxj2+/xY5x9Z5H5Ia/6LfCwF4dq8 hiHZ6Dl8kR2Dy77V3OMhveecZdvrMaf1HjkXbX4SEUE3B7Dc4zDk5ROPCZjdnbaQdzQs wYUiB25yvju4PGYfFsmgpSB+8qYdU7rrrBY8FDz9KM65Wtz0XjTJov0yD8QVJ1KgZPfr 50gw5D3DEBHqpmL/ROIWJhkx1zYBDvK8U+U6gSMEQ16Gw9EMfb8sNWLnF3NXc4I23Hgl 4RxOYIxsC0mj9vPMWS9snPCjP5wGnELL9YSzU3Dbx7Onu82XjkeZNLQwYS/srtKw0eu/ Hg/Q== X-Gm-Message-State: AAQBX9d/biDIeCSY1o3chwGxub7M/Ohl5uPq6wli2ExJRyZDMujZ2fgB ZuDXVhIBQ/AW3rryK65N916RkQ== X-Google-Smtp-Source: AKy350ZEeKY6w6K1zzH/dW/xivR15vW3hQd6CLYZegluO5Sbjosmz2HaeiqG5cUr1ggyvwzbv6IOqQ== X-Received: by 2002:aa7:c7cf:0:b0:500:50f6:dd27 with SMTP id o15-20020aa7c7cf000000b0050050f6dd27mr7533927eds.26.1679822542121; Sun, 26 Mar 2023 02:22:22 -0700 (PDT) Received: from ?IPV6:2a02:810d:15c0:828:6cac:926d:a4f2:aa09? ([2a02:810d:15c0:828:6cac:926d:a4f2:aa09]) by smtp.gmail.com with ESMTPSA id xi3-20020a170906dac300b009445d6213c0sm308958ejb.75.2023.03.26.02.22.21 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 26 Mar 2023 02:22:21 -0700 (PDT) Message-ID: Date: Sun, 26 Mar 2023 11:22:20 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.9.0 Subject: Re: [PATCH v2] arm64: dts: qcom: sdm630: move DSI opp-table out of soc node Content-Language: en-US To: Dmitry Baryshkov 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 References: <20230326091605.18908-1-krzysztof.kozlowski@linaro.org> From: Krzysztof Kozlowski In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org 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. Best regards, Krzysztof