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 AE118C4167B for ; Fri, 30 Dec 2022 16:03:50 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229649AbiL3QDt (ORCPT ); Fri, 30 Dec 2022 11:03:49 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36332 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235123AbiL3QDc (ORCPT ); Fri, 30 Dec 2022 11:03:32 -0500 Received: from mail-lf1-x12f.google.com (mail-lf1-x12f.google.com [IPv6:2a00:1450:4864:20::12f]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 2420D1C420 for ; Fri, 30 Dec 2022 08:03:22 -0800 (PST) Received: by mail-lf1-x12f.google.com with SMTP id p36so32220556lfa.12 for ; Fri, 30 Dec 2022 08:03:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=6pEMTZq5rWT0ikjSiFOqMGW0/ayLLsoOFF5CL8qcGVQ=; b=tQHXrbSsOaLTfZRY8dRbWpePUdxsxdvtzwxe7/2GetpusnJZFxpXJB8wRNwpr3WldV s19kmo24ZbZ1oe/x1SR82hwEyCgdnBWKzDUj6AOErBuUw6+I9Cqot1WrBFmkJRiYNtup MqYehAtpYs7zSsESkCvEleijxlmtHXHHXnPqBOfwe0dAj9+nUsnrqqTCL8+Gkf8bj9V2 4eWPD5nV3b/j/I4MmlnWPpEVx35FcyqeN6g0LSclC7UGtnayDcgOmJP+Gg/CFUrmfoh1 tgF2U6pw9RrwM+rq9tXlLGJTEi7DrpFxw5NNbsUiM/OPwV3kDmmWu36cJodiAXlSdCv9 m+AQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:references: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=6pEMTZq5rWT0ikjSiFOqMGW0/ayLLsoOFF5CL8qcGVQ=; b=X3MQ1Un7AefQnqalqWMnKoJZ2on8Rwk00W/X0QcrMl6/h4u1FqLJC+1lCjL78Y4tZi lwdkCQLz0Rc9MZrjL1AfZs48Vmw/dxQzgWiNxL3auoqnIpVNkAzjWDkk1VIvlbqLTgkx nv2i+6C5OjYZyQRgZTwHfPK5GcEDypNPl2Csut4EfTIBhd4510H5LJ+Nw7DgJ21+vYEO wDdmt0NyE2WzUu7+YkWnY+VZnumoeW6RspACZ7aPpC0P4N0JvsapIoiEVPLERerb1d9y Wl/SA1RvdzbQOopz74YY4Bp/lGah2CwFKttHFqLw5GFQbvyuHloDrkIGh4Wpb0rhpH2N lJeQ== X-Gm-Message-State: AFqh2kqyVX5QjOL9sFQeO/eBUJw+JkAL8AbAbQCSpG7Xji6qSuzUWebA nL8bKf9WbgfAV35O2Ma6+5xj1A== X-Google-Smtp-Source: AMrXdXsHyc3chqcKODktW8AZ+glx19EsiPsG6A3SVu3ouL/gWiULTW7qi+aP0yRdVoba3tPxkasiKA== X-Received: by 2002:a05:6512:2624:b0:4b4:a224:96e with SMTP id bt36-20020a056512262400b004b4a224096emr9462478lfb.50.1672416200569; Fri, 30 Dec 2022 08:03:20 -0800 (PST) Received: from [192.168.0.20] (088156142067.dynamic-2-waw-k-3-2-0.vectranet.pl. [88.156.142.67]) by smtp.gmail.com with ESMTPSA id x4-20020a19f604000000b004cb0d2735c0sm1764481lfe.266.2022.12.30.08.03.19 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 30 Dec 2022 08:03:19 -0800 (PST) Message-ID: <75de9fd1-2309-2d7a-41e9-f2efe2766c08@linaro.org> Date: Fri, 30 Dec 2022 17:03:18 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.6.1 Subject: Re: [PATCH 1/7] arm64: dts: qcom: sc8280xp: remove GCC from CX power domain Content-Language: en-US To: 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: <20221230160103.250996-1-krzysztof.kozlowski@linaro.org> From: Krzysztof Kozlowski In-Reply-To: <20221230160103.250996-1-krzysztof.kozlowski@linaro.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org On 30/12/2022 17:00, Krzysztof Kozlowski wrote: > Bindings do not allow power-domain property in GCC clock controller and > documentation does not indicate that GCC is part of VDD_CX. > > Signed-off-by: Krzysztof Kozlowski > > --- > > Maybe the bindings should be fixed? Maybe this was added as workaround? > Anyway looking at documentation I do not see such relation, except > downstream vdd_cx-supply (which is the same as in other SoCs and we do > not represent it in upstream). > --- This one patch is a duplicate - I sent it already as RFT. Sorry for the noise. Best regards, Krzysztof