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 A7008CCA47E for ; Fri, 24 Jun 2022 15:57:55 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229607AbiFXP5y (ORCPT ); Fri, 24 Jun 2022 11:57:54 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:59682 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229533AbiFXP5y (ORCPT ); Fri, 24 Jun 2022 11:57:54 -0400 Received: from mail-ej1-x62f.google.com (mail-ej1-x62f.google.com [IPv6:2a00:1450:4864:20::62f]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 84E19AD for ; Fri, 24 Jun 2022 08:57:52 -0700 (PDT) Received: by mail-ej1-x62f.google.com with SMTP id q6so5507282eji.13 for ; Fri, 24 Jun 2022 08:57:52 -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=0znaSH1nVDQVgpmhIs5rMZ+BhzfTMBgXnaj++3f6TvA=; b=UUDhsj7ULQ4PeB1uK/kA0qMYQrQCzC2Q3ohlToCDL7nhXdNBxMnMtVTpAdQLeAc4I1 +DwPkd5y5zGDJmLek29RAQqVRY7gw9qJyJ2AiSNkC01EpHsdYA5QMenCdBQ8/oOsH+Vs zKjYVpEe9FFC14Qanxqs796VdF+iYFfhgJG3+0sPOIOAP5XEklw94uwGN5A9wqOC6evK Pxfvw3NCUqiH/qcBLXTGdQPB2AC3zfrvKLOyvcHTaN7tIvG08Gmh4lDS9Wt5laR58Tgl bEXkI8OjrvJF63CZj0OIGpEgH+vYn54o/mMBPXUwckT2Sm1MN6970cs4nw0W7AR2J0IA lJ/Q== 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=0znaSH1nVDQVgpmhIs5rMZ+BhzfTMBgXnaj++3f6TvA=; b=aGeWVqgbkJ04VFc2gBgYZVKlEe6f4miZ31of1R+X0eIQYMva0LLPqxIPH2gaVTSfHq WyMliAolImvINMhvPw/F4s2Y2kLZBJtcLhITzywS2uCeAGW5hx1iEwE/flJCQ99Uuq1N BCWmii9mt8ZzzmplALdFj4YQ7kXm6iSwI6JtOsikxaaXdFwdS3JlBbbDHWsYRCnRUh2Q 1LiZWyBkzWDu+bXDlpZRMcS7t2Hb22MNstYtp6erfRnmXnpD4+CzqAWiod0UM8/++8LX gLSg/Zih7p+sPvaVg0xSaTvu5TIruvmsiR3QgIMDzHwYZLwtfLVsZbHzLT4cd75l/fA9 OXnw== X-Gm-Message-State: AJIora/yAQPkntUwd0HkEd0wzsdkDsbjhM1ZS9FX5hw/YrQGwpRg4CZa +6LtuhLHoOxqQv4SCJvy11PW8A== X-Google-Smtp-Source: AGRyM1vjjpp5meQC7xcv51xr6LCMNiZJlsPCBgY2/hKwi7VZpdAAhayWVqXgkaik+O5RtfsZw04bug== X-Received: by 2002:a17:906:6c82:b0:709:f868:97f6 with SMTP id s2-20020a1709066c8200b00709f86897f6mr14365853ejr.555.1656086271135; Fri, 24 Jun 2022 08:57:51 -0700 (PDT) Received: from [192.168.0.237] (xdsl-188-155-176-92.adslplus.ch. [188.155.176.92]) by smtp.gmail.com with ESMTPSA id n3-20020a170906724300b00722e660f16fsm1380209ejk.23.2022.06.24.08.57.50 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 24 Jun 2022 08:57:50 -0700 (PDT) Message-ID: <21efbf73-74af-8f80-3577-b82f39e161e6@linaro.org> Date: Fri, 24 Jun 2022 17:57:49 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.10.0 Subject: Re: [PATCH 02/15] dt-bindings: clocks: qcom,mmcc: define clocks/clock-names for MSM8960 Content-Language: en-US To: Dmitry Baryshkov , Andy Gross , Bjorn Andersson , Stephen Boyd , Michael Turquette , Rob Herring , Krzysztof Kozlowski , Taniya Das Cc: linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org, devicetree@vger.kernel.org References: <20220623120418.250589-1-dmitry.baryshkov@linaro.org> <20220623120418.250589-3-dmitry.baryshkov@linaro.org> From: Krzysztof Kozlowski In-Reply-To: <20220623120418.250589-3-dmitry.baryshkov@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 23/06/2022 14:04, Dmitry Baryshkov wrote: > Define clock/clock-names properties of the MMCC device node to be used > on MSM8960/APQ8064 platform. > > Signed-off-by: Dmitry Baryshkov > --- > .../devicetree/bindings/clock/qcom,mmcc.yaml | 31 +++++++++++++++++++ > 1 file changed, 31 insertions(+) > > diff --git a/Documentation/devicetree/bindings/clock/qcom,mmcc.yaml b/Documentation/devicetree/bindings/clock/qcom,mmcc.yaml > index d02fe6dc79b5..c13243682365 100644 > --- a/Documentation/devicetree/bindings/clock/qcom,mmcc.yaml > +++ b/Documentation/devicetree/bindings/clock/qcom,mmcc.yaml > @@ -82,6 +82,37 @@ then: > - clock-names > > allOf: > + - if: > + properties: > + compatible: > + contains: > + enum: > + - qcom,mmcc-apq8064 > + - qcom,mmcc-msm8960 > + then: > + properties: > + clocks: > + items: > + - description: Board PXO source > + - description: PLL 3 clock > + - description: PLL 3 Vote clock > + - description: DSI phy instance 1 dsi clock > + - description: DSI phy instance 1 byte clock > + - description: DSI phy instance 2 dsi clock > + - description: DSI phy instance 2 byte clock > + - description: HDMI phy PLL clock > + > + clock-names: > + items: > + - const: pxo > + - const: pll3 > + - const: pll8_vote > + - const: dsi1pll > + - const: dsi1pllbyte > + - const: dsi2pll > + - const: dsi2pllbyte > + - const: hdmipll The clocks are listed in properties, so they have min/max constraints set implicitly. Are you sure this now works fine? Best regards, Krzysztof