Received: by 2002:a05:6602:2086:0:0:0:0 with SMTP id a6csp3362077ioa; Tue, 26 Apr 2022 01:59:13 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzJk9ox+W7soauxWa2RD8ATA0vRHQw61Wc2nRXOlpM1OpAne0/mOynnJ+nHfV6fkQf6nMy/ X-Received: by 2002:a05:6a00:24cc:b0:50d:58bf:5104 with SMTP id d12-20020a056a0024cc00b0050d58bf5104mr2400229pfv.36.1650963552998; Tue, 26 Apr 2022 01:59:12 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1650963552; cv=none; d=google.com; s=arc-20160816; b=PnPT8oQYx17SwlVCmeUBgNVX1pcrB+Wk7C4rgSggYp0gtPd8jz6mlAXCrFix/bqXer MPtz13mVrbI7C47Slg/GW6ESRi1gr6XdljgLF9tS2e5/zphd+D6dz5PAwjmerC1BQb/1 qIkr4JXd6Yj5bUA1EAltOIYYNF/AKdirFNJ6vRV7pjUzDfkaf1OzOxYrFRzw+HamWvs6 Wosj4p7jidczBX0k7DySSIOylhN3L+pO8InmdcZwJcu2DsHCOjfpqwpM6ClWKrHGMCOM QrEOKfGX7CQPx7w3+Ull32hsc+i4KP+z6V4L9/kAtBRIwgnOBbprGnwwb/ii+lAAkGSJ de/g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from:dkim-signature; bh=vEOSnXjfcH/l5Es8VtB/ak1K3hreA1C3eDBJ8dHARyo=; b=by3+jCAe6+zL2EfNsJIgiD2XuRY/GotQIMQkV4y6dVFNZPntNJVG4YUCxqG4snIvFH irFEvKg5b9EgpymCmQIl6/2cY0SPK5DyKBLJmO7A4uericNBis0CsSc8oHfzEzaAs9q+ 9OGazhTEC/0azmmgMoQ+vLK5hqXwfdJKV8QeCFA672IpIdjpxmGPVR69QacJGkPyenAV 8u+8kGs/64uV6QbZ2fXZpxkrPT4VOQPXRGpdsTeKO0rR6lavq7FrTMuhE16sISUhhISi WSlpJArK1cT6aNzlEY3oQZv7qJMxfqHRSujsxMOikPhJOSs4J5Jedu2f/G089jx3ZHd2 2CTg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=bASAClY6; 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 x17-20020a17090aca1100b001d99e27cc99si1781048pjt.81.2022.04.26.01.58.59; Tue, 26 Apr 2022 01:59:12 -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=bASAClY6; 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 S1343490AbiDZGqL (ORCPT + 99 others); Tue, 26 Apr 2022 02:46:11 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:58620 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S245749AbiDZGp7 (ORCPT ); Tue, 26 Apr 2022 02:45:59 -0400 Received: from mail-ej1-x62b.google.com (mail-ej1-x62b.google.com [IPv6:2a00:1450:4864:20::62b]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id DAB0012C406 for ; Mon, 25 Apr 2022 23:42:46 -0700 (PDT) Received: by mail-ej1-x62b.google.com with SMTP id gh6so9959969ejb.0 for ; Mon, 25 Apr 2022 23:42:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=vEOSnXjfcH/l5Es8VtB/ak1K3hreA1C3eDBJ8dHARyo=; b=bASAClY6Ytda/4xUhup8MUSUMsRpRAR50cqsJ0XAhppisIw/yr3Xf8wWEbZ5+xFHAI TOHWNUaLKHbhBnYaZ2Q9x9tGRWB0zFVJFafT2ODZVUTXhAMONRvUCRUf2QdJ7NOT3Xdi GtfHjgDwHJKBPP6tvv+uw318ezvkJt13nlj2HrLqud15LIUkl+IzyVCZ7DJ0QlV2CrcQ G9fFDlVrRM3nHlVe/lfOa6Oq+iQuNKfkFOs6uC/DXvxAtb6pVhPTws9BjtCfeQW/AXxm /t2ybFAayhGpTecMphERvHj25Qx0POiUlJLQe2OOQUCoeXGzWX9AFfPMTBWMvmKmPCaX u4Cw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=vEOSnXjfcH/l5Es8VtB/ak1K3hreA1C3eDBJ8dHARyo=; b=qsI9m6TYigP/I238dl189f0hGOIzL4AHUoxu258KL7hOgt0YhlWWCPRgRn6IujbYTc U+kJ58YEvAr8TbPNHEXzI/uuznnQb1Ou4bxemQCqgiLSQEeWUpchyOZlPUN8vpbJ0ami AO1Mzt2/gnYR0cr/7BEv+V5qidq89myv50sQEa0eDgsNVl/8gDM5uz7k87JPhC0iayz+ NW2OEWauayRGKMjjD18aafUgtPs2HGzO41bb5ulDzo+ChFxtNfiHaLkbWyf6na6nqFw0 JYAjlVB3fNDWenOAns2Ut6CU6WARviw7twg/jelWU6HPAco1DIYWhp5Leu2rJktoh8l8 IxjA== X-Gm-Message-State: AOAM5332yeUnnpPBw/lipd2j1U239hYrGYOEtMtcY4/E20cES7xi66km Rgnt+VIBCl5KS8eViiGpvTNboA== X-Received: by 2002:a17:906:1315:b0:6ef:5903:c5d1 with SMTP id w21-20020a170906131500b006ef5903c5d1mr19635606ejb.537.1650955365291; Mon, 25 Apr 2022 23:42:45 -0700 (PDT) Received: from localhost.localdomain (xdsl-188-155-176-92.adslplus.ch. [188.155.176.92]) by smtp.gmail.com with ESMTPSA id fx3-20020a170906b74300b006daecedee44sm4386885ejb.220.2022.04.25.23.42.44 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 25 Apr 2022 23:42:44 -0700 (PDT) From: Krzysztof Kozlowski To: Bjorn Andersson , Andy Gross , Michael Turquette , Stephen Boyd , Rob Herring , Krzysztof Kozlowski , Taniya Das , Ansuel Smith , linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Cc: Krzysztof Kozlowski , Rob Herring Subject: [PATCH v2] dt-bindings: clock: qcom,gcc-apq8064: Fix typo in compatible and split apq8084 Date: Tue, 26 Apr 2022 08:42:41 +0200 Message-Id: <20220426064241.6379-1-krzysztof.kozlowski@linaro.org> X-Mailer: git-send-email 2.32.0 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_PASS autolearn=ham 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 The qcom,gcc-apq8064.yaml was meant to describe only APQ8064 and APQ8084 should have slightly different bindings (without Qualcomm thermal sensor device). Add new bindings for APQ8084. Fixes: a469bf89a009 ("dt-bindings: clock: simplify qcom,gcc-apq8064 Documentation") Reported-by: Rob Herring Signed-off-by: Krzysztof Kozlowski --- Changes since v1: 1. Correct Taniya's email. 2. Correct chipset name in description. 3. Extend commit msg. --- .../bindings/clock/qcom,gcc-apq8064.yaml | 4 +- ...gcc-apq8064.yaml => qcom,gcc-apq8084.yaml} | 57 +++++-------------- 2 files changed, 16 insertions(+), 45 deletions(-) copy Documentation/devicetree/bindings/clock/{qcom,gcc-apq8064.yaml => qcom,gcc-apq8084.yaml} (31%) diff --git a/Documentation/devicetree/bindings/clock/qcom,gcc-apq8064.yaml b/Documentation/devicetree/bindings/clock/qcom,gcc-apq8064.yaml index 97936411b6b4..9fafcb080069 100644 --- a/Documentation/devicetree/bindings/clock/qcom,gcc-apq8064.yaml +++ b/Documentation/devicetree/bindings/clock/qcom,gcc-apq8064.yaml @@ -20,12 +20,10 @@ description: | See also: - dt-bindings/clock/qcom,gcc-msm8960.h - dt-bindings/reset/qcom,gcc-msm8960.h - - dt-bindings/clock/qcom,gcc-apq8084.h - - dt-bindings/reset/qcom,gcc-apq8084.h properties: compatible: - const: qcom,gcc-apq8084 + const: qcom,gcc-apq8064 nvmem-cells: minItems: 1 diff --git a/Documentation/devicetree/bindings/clock/qcom,gcc-apq8064.yaml b/Documentation/devicetree/bindings/clock/qcom,gcc-apq8084.yaml similarity index 31% copy from Documentation/devicetree/bindings/clock/qcom,gcc-apq8064.yaml copy to Documentation/devicetree/bindings/clock/qcom,gcc-apq8084.yaml index 97936411b6b4..397fb918e032 100644 --- a/Documentation/devicetree/bindings/clock/qcom,gcc-apq8064.yaml +++ b/Documentation/devicetree/bindings/clock/qcom,gcc-apq8084.yaml @@ -1,69 +1,42 @@ -# SPDX-License-Identifier: GPL-2.0-only +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause %YAML 1.2 --- -$id: http://devicetree.org/schemas/clock/qcom,gcc-apq8064.yaml# +$id: http://devicetree.org/schemas/clock/qcom,gcc-apq8084.yaml# $schema: http://devicetree.org/meta-schemas/core.yaml# -title: Qualcomm Global Clock & Reset Controller Binding for APQ8064 - -allOf: - - $ref: qcom,gcc.yaml# +title: Qualcomm Global Clock & Reset Controller Binding for APQ8084 maintainers: - Stephen Boyd - - Taniya Das + - Taniya Das description: | Qualcomm global clock control module which supports the clocks, resets and - power domains on APQ8064. + power domains on APQ8084. - See also: - - dt-bindings/clock/qcom,gcc-msm8960.h - - dt-bindings/reset/qcom,gcc-msm8960.h + See also:: - dt-bindings/clock/qcom,gcc-apq8084.h - dt-bindings/reset/qcom,gcc-apq8084.h +allOf: + - $ref: qcom,gcc.yaml# + properties: compatible: const: qcom,gcc-apq8084 - nvmem-cells: - minItems: 1 - maxItems: 2 - description: - Qualcomm TSENS (thermal sensor device) on some devices can - be part of GCC and hence the TSENS properties can also be part - of the GCC/clock-controller node. - For more details on the TSENS properties please refer - Documentation/devicetree/bindings/thermal/qcom-tsens.yaml - - nvmem-cell-names: - minItems: 1 - items: - - const: calib - - const: calib_backup - - '#thermal-sensor-cells': - const: 1 - required: - compatible - - nvmem-cells - - nvmem-cell-names - - '#thermal-sensor-cells' unevaluatedProperties: false examples: - | - clock-controller@900000 { - compatible = "qcom,gcc-apq8064"; - reg = <0x00900000 0x4000>; - nvmem-cells = <&tsens_calib>, <&tsens_backup>; - nvmem-cell-names = "calib", "calib_backup"; - #clock-cells = <1>; - #reset-cells = <1>; - #power-domain-cells = <1>; - #thermal-sensor-cells = <1>; + clock-controller@fc400000 { + compatible = "qcom,gcc-apq8084"; + reg = <0xfc400000 0x4000>; + #clock-cells = <1>; + #reset-cells = <1>; + #power-domain-cells = <1>; }; ... -- 2.32.0