Received: by 2002:ac0:e34a:0:0:0:0:0 with SMTP id g10csp541654imn; Tue, 26 Jul 2022 02:59:36 -0700 (PDT) X-Google-Smtp-Source: AGRyM1tKsuCul/Hb6uFLAXYyUcrjKgMMRo/617FQZ6QvcZgugj0KpXdNfwGEfL4z+8Ris6xCtrLR X-Received: by 2002:aa7:cb87:0:b0:43b:e650:6036 with SMTP id r7-20020aa7cb87000000b0043be6506036mr13188340edt.350.1658829576293; Tue, 26 Jul 2022 02:59:36 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1658829576; cv=none; d=google.com; s=arc-20160816; b=tx7qo36cs/zL0TeERq9t/I7C2aKu6F7kz//JzvAdvKeD0OtEmlbCB7CaBMJkwKHa7k legd2Rq2QhmA8pB6KujXKiEmlChtIkPVjk4J9KiMq1TY/NiANqja0OhPcR2wWs8IHkLw efHtbEYxGsc9JT3WU/equ3xoNqocCw/1x5bEpg4ghxg9C9VRAjtZTfC8/XTb6nNDpciF 5CnV3Evl36a2kIk4F56t0SN29uHEWBBkDQ3ePCj2zPdxTIn5amM1Cs+UvatsfeoE/wf2 ohIMwaZKCqvMazRZtBPfn3kz8E4gYwl5TZVPNotaCLnbj9HKEXG3xJi905xl7LGrn++D 3ZFA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:from :references:cc:to:content-language:subject:user-agent:mime-version :date:message-id:dkim-signature; bh=CaAorG4BYFUosNioD1hfjI7j/Y8uoX4/ARwNzmf43cw=; b=DpVINYj8EmU71yu/U/nY5bJOtXVvKZB3LNyEVrGp9P7aS68IWQ0FHeZQCXby5eBNWI fBbQeBj0EprAHAqcXgpZwDPTcVkkJZQpQy6LYDr7199Fv2I6g6+3kPhcdoChRF1a6tt+ ou80q6cqZ7FqYpRjqVvFdlZgoHTgZCdTCGtTmYhj1yV6RgRFrP/GkPKNKVwpwTJSC4XI rnqtjYrHClAuUbdoZW71g4yU3SoS6hGJkOXn2581KDqs84Hj0iq0CISYeOO2IeVdnUTp W5PHEDyBSC25xG0bNpWScYK3IrSeosyovuKbBQm8a/G9ZzB1dTSt6FTZ1cpnfF3ZkACg Pv6w== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=p3n5O0Gt; 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 hd35-20020a17090796a300b0072b9b3d42cbsi17600095ejc.525.2022.07.26.02.59.02; Tue, 26 Jul 2022 02:59:36 -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=p3n5O0Gt; 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 S238587AbiGZJw6 (ORCPT + 99 others); Tue, 26 Jul 2022 05:52:58 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:54286 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S238332AbiGZJw4 (ORCPT ); Tue, 26 Jul 2022 05:52:56 -0400 Received: from mail-lj1-x232.google.com (mail-lj1-x232.google.com [IPv6:2a00:1450:4864:20::232]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 0093A2BB18 for ; Tue, 26 Jul 2022 02:52:54 -0700 (PDT) Received: by mail-lj1-x232.google.com with SMTP id b34so10721248ljr.7 for ; Tue, 26 Jul 2022 02:52:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=message-id:date:mime-version:user-agent:subject:content-language:to :cc:references:from:in-reply-to:content-transfer-encoding; bh=CaAorG4BYFUosNioD1hfjI7j/Y8uoX4/ARwNzmf43cw=; b=p3n5O0GtUJad0vTXMoPkX2ckqhPr5UafevVhNH5JTi6wy0W2gaHkP5DNy6FGqEQt4M nRj5+HKbZtTmwcspNWsbBHOax1/QKpF9A1DEebDg+AhMGTJZV/1jVkV5Re8w06P8ug1U MVIgkg0hAHBI+L37PvNiuBhkonn2AZ4NsygjD0SYIkK2InScTRd7KBXo4Vej/NLpT+Pt WpNC+P0tYihyUQq4ISoWfY0V54NbhEgLbFafQfclvnZbr8MBqLzEphCRdPTmt8gmHCEH rN+LnAOMeOxqgpFM3cB3vdMDRCMJ9Vj5vE917dvA0Lu9IRYzBQn/xOmRMrtmXEnI7YQ5 exww== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:cc:references:from:in-reply-to :content-transfer-encoding; bh=CaAorG4BYFUosNioD1hfjI7j/Y8uoX4/ARwNzmf43cw=; b=ccCU0GOhnbw/+5GQt0FFA76VpFKxV57U5stx3BoDXBvhdGEuS0OdN6oNug4gE40/q+ rBgMxtCedKkQSdkpmy+R+4UUa0GN3LPmTqzi3I7m/9Z2zIRKSAUETCbian/C98lZbE3g y8w8xmgDq971puESyo3Iws++h6H52oTfEXVgaOV2QdVT8i8iRbuQ7T9j6NylJlOIsVx4 ElWBRUnRw5cgPvflDn/KRIpRg73ImtvUIPnUzrikxaCNVUeDHjEhX8hH6Jbhyaolpo/e OqG35r2ydeP2qvi802p98tfnwm/LTPmSUVNYZoJ9ubhBSKykLy4QwvEgz8oVNlKQRYIs Lb/Q== X-Gm-Message-State: AJIora+Q1pmhdHBWuQOiyujVzB0D5lChUl4NAC58gWHcUrPZ+zwjxb01 /Xv+KSyIroYY2sZRKNX9u38+pw== X-Received: by 2002:a2e:8e2c:0:b0:25d:e021:ba8f with SMTP id r12-20020a2e8e2c000000b0025de021ba8fmr5533140ljk.491.1658829173391; Tue, 26 Jul 2022 02:52:53 -0700 (PDT) Received: from [192.168.3.197] (78-26-46-173.network.trollfjord.no. [78.26.46.173]) by smtp.gmail.com with ESMTPSA id c25-20020ac25f79000000b0048a8f097713sm1035410lfc.80.2022.07.26.02.52.52 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 26 Jul 2022 02:52:52 -0700 (PDT) Message-ID: Date: Tue, 26 Jul 2022 11:52:51 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.12.0 Subject: Re: [PATCH v3 2/3] dt-bindings: clock: add SM6375 QCOM global clock bindings Content-Language: en-US To: Konrad Dybcio , ~postmarketos/upstreaming@lists.sr.ht Cc: martin.botka@somainline.org, angelogioacchino.delregno@somainline.org, marijn.suijten@somainline.org, jamipkettunen@somainline.org, Andy Gross , Bjorn Andersson , Michael Turquette , Stephen Boyd , Rob Herring , Krzysztof Kozlowski , linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org References: <20220723100135.91784-1-konrad.dybcio@somainline.org> <20220723100135.91784-2-konrad.dybcio@somainline.org> <27154a09-d79b-7814-22ec-c84496596abc@linaro.org> <6a33d026-9f30-358e-8498-dbe315fccc5b@somainline.org> From: Krzysztof Kozlowski In-Reply-To: <6a33d026-9f30-358e-8498-dbe315fccc5b@somainline.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,NICE_REPLY_A,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 On 23/07/2022 22:56, Konrad Dybcio wrote: > > > On 23.07.2022 19:46, Krzysztof Kozlowski wrote: >> On 23/07/2022 12:01, Konrad Dybcio wrote: >>> Add device tree bindings for global clock controller for SM6375 SoCs. >>> >>> Signed-off-by: Konrad Dybcio >>> --- >>> Changes since v2: >>> - reference qcom,gcc.yaml >>> >>> .../bindings/clock/qcom,sm6375-gcc.yaml | 48 ++++ >>> include/dt-bindings/clock/qcom,sm6375-gcc.h | 234 ++++++++++++++++++ >>> 2 files changed, 282 insertions(+) >>> create mode 100644 Documentation/devicetree/bindings/clock/qcom,sm6375-gcc.yaml >>> create mode 100644 include/dt-bindings/clock/qcom,sm6375-gcc.h >>> >>> diff --git a/Documentation/devicetree/bindings/clock/qcom,sm6375-gcc.yaml b/Documentation/devicetree/bindings/clock/qcom,sm6375-gcc.yaml >>> new file mode 100644 >>> index 000000000000..fb1c36888d18 >>> --- /dev/null >>> +++ b/Documentation/devicetree/bindings/clock/qcom,sm6375-gcc.yaml >>> @@ -0,0 +1,48 @@ >>> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) >>> +%YAML 1.2 >>> +--- >>> +$id: http://devicetree.org/schemas/clock/qcom,sm6375-gcc.yaml# >>> +$schema: http://devicetree.org/meta-schemas/core.yaml# >>> + >>> +title: Qualcomm Global Clock & Reset Controller Binding for SM6375 >>> + >>> +maintainers: >>> + - Konrad Dybcio >>> + >>> +description: | >>> + Qualcomm global clock control module which supports the clocks, resets and >>> + power domains on SM6375 >>> + >>> + See also: >>> + - dt-bindings/clock/qcom,sm6375-gcc.h >>> + >>> +allOf: >>> + - $ref: qcom,gcc.yaml# >>> + >>> +properties: >>> + compatible: >>> + const: qcom,sm6375-gcc >>> + >>> + clocks: >>> + items: >>> + - description: Board XO source >>> + - description: Board XO Active-Only source >>> + - description: Sleep clock source >> >> What happened to clock-names? >> >>> + >> >> I would assume these are required for the clock controller... and they >> were before, so what happened? > I dropped them in v2, as with switching the .c driver to use the > index matching, they are no longer used. OK, but what about clocks as required? Why aren't these now required? Best regards, Krzysztof