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 X-Spam-Level: X-Spam-Status: No, score=-10.6 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH, MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_PASS,USER_AGENT_GIT autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 3D325C43610 for ; Wed, 28 Nov 2018 18:58:06 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id F3D902081C for ; Wed, 28 Nov 2018 18:58:05 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=chromium.org header.i=@chromium.org header.b="ORPnWLzE" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org F3D902081C Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=chromium.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728873AbeK2GAm (ORCPT ); Thu, 29 Nov 2018 01:00:42 -0500 Received: from mail-pg1-f196.google.com ([209.85.215.196]:39497 "EHLO mail-pg1-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727508AbeK2GAm (ORCPT ); Thu, 29 Nov 2018 01:00:42 -0500 Received: by mail-pg1-f196.google.com with SMTP id w6so9905330pgl.6 for ; Wed, 28 Nov 2018 10:58:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=s5w4IN2H7W8bHGPBbVZSOf6yGCi4eThxvzg0kR6f4Dk=; b=ORPnWLzEOtNhR2Z8E07sRFXQTwvb+7KTAMy8h+G+SnigHFd6vYQRJl07adqmHmZ5g/ sLlEFgcHxVtzE0q3bhjqQeyI3L0GpyDfbEwNuHZRRAB59xsZlc4C+JXoOH8DHKLdO1xZ OeTnq/PfBBgS9SGlNyJUvM0cOCUTmaq+Nm6Zw= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=s5w4IN2H7W8bHGPBbVZSOf6yGCi4eThxvzg0kR6f4Dk=; b=i90EC+aCO88JLepFaHUK7oEHOGwWy++3FO00xSzWMloIiawsS+BkqxJGUwrxgFHLI6 dK4Fvd8p3TNIX3cgNDotLSdj596A0LhE/bcH2FDgTrHSFe90pK0QePHkryNmUbQJTNmk jwyO2pJOTOTNRTqBNC3tWjp2KC17zQ8yrhKpxXkrYWLzjhwblBOPrhqF4L0qGnWX6UOq 3v49WLH/7RnlTuDFpW7XEKE79ldFYZ7L72XkkUzCUepcxk3HHuAjlNuphdzmOLSpHeve aZOCTuOTdYtoNpl68Wj4NZ+5LAIwIg9xUhP2+9bWiDN0/asv2Au7hKRxhAnEVQPiAuc8 IVcw== X-Gm-Message-State: AA+aEWZi7koqzg+obDwjCrJk65vCH/BFDHqgpfAXHzzuUJ6LOhHrFEeb jkbBkPLtUnla3Hsp1iQnxi4wHQ== X-Google-Smtp-Source: AFSGD/ViFzCTzgFemv+Mv4raYZFfi443LSS3nw/HOXRLZodnt2sY4IIlLiBIwccuaEtunULlBz6d0Q== X-Received: by 2002:a62:3948:: with SMTP id g69mr4371089pfa.114.1543431484179; Wed, 28 Nov 2018 10:58:04 -0800 (PST) Received: from tictac2.mtv.corp.google.com ([2620:15c:202:1:c8e0:70d7:4be7:a36]) by smtp.gmail.com with ESMTPSA id f6sm13204214pfg.188.2018.11.28.10.58.02 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 28 Nov 2018 10:58:03 -0800 (PST) From: Douglas Anderson To: Stephen Boyd , Andy Gross Cc: linux-arm-msm@vger.kernel.org, Taniya Das , "Kristian H . Kristensen" , Jordan Crouse , Amit Nischal , Douglas Anderson , devicetree@vger.kernel.org, Michael Turquette , linux-kernel@vger.kernel.org, Rob Herring , Mark Rutland , linux-clk@vger.kernel.org Subject: [PATCH 1/2] dt-bindings: clock: qcom: Fix the xo parent in gpucc example Date: Wed, 28 Nov 2018 10:57:42 -0800 Message-Id: <20181128185743.75328-1-dianders@chromium.org> X-Mailer: git-send-email 2.20.0.rc0.387.gc7a69e6b6c-goog MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org In the bindings that landed for the gpucc we require that the XO clock (one possible parent of the gpucc) be listed. The code doesn't use this yet--this is just to allow us to move toward the day when it does use it. What the code does do today is to hardcode the parent name to "bi_tcxo". That's all well and good. ...but the example in the bindings shows this clock mapping to the clock "xo_board". On the current sdm845.dtsi file the "xo_board" clock is a fixed clock with an output name of "xo_board". The clock with the name "bi_tcxo" is actually provided by the RPMh Clock Controller. Presumably that's the one that was wanted. Let's update the example to make this clearer. Fixes: e431c92188a9 ("dt-bindings: clock: Introduce QCOM Graphics clock bindings") Signed-off-by: Douglas Anderson --- Documentation/devicetree/bindings/clock/qcom,gpucc.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/devicetree/bindings/clock/qcom,gpucc.txt b/Documentation/devicetree/bindings/clock/qcom,gpucc.txt index 9d0358cc08b4..4e5215ef1acd 100644 --- a/Documentation/devicetree/bindings/clock/qcom,gpucc.txt +++ b/Documentation/devicetree/bindings/clock/qcom,gpucc.txt @@ -17,6 +17,6 @@ Example: #clock-cells = <1>; #reset-cells = <1>; #power-domain-cells = <1>; - clocks = <&xo_board>; + clocks = <&rpmhcc RPMH_CXO_CLK>; clock-names = "xo"; }; -- 2.20.0.rc0.387.gc7a69e6b6c-goog