From patchwork Thu Nov 29 22:13:53 2018 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Evan Green X-Patchwork-Id: 10705443 Return-Path: Received: from mail.wl.linuxfoundation.org (pdx-wl-mail.web.codeaurora.org [172.30.200.125]) by pdx-korg-patchwork-2.web.codeaurora.org (Postfix) with ESMTP id DB2AE1057 for ; Thu, 29 Nov 2018 22:14:23 +0000 (UTC) Received: from mail.wl.linuxfoundation.org (localhost [127.0.0.1]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id C29A72A1A7 for ; Thu, 29 Nov 2018 22:14:23 +0000 (UTC) Received: by mail.wl.linuxfoundation.org (Postfix, from userid 486) id B5FB32AC85; Thu, 29 Nov 2018 22:14:23 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on pdx-wl-mail.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-8.0 required=2.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,RCVD_IN_DNSWL_HI autolearn=ham version=3.3.1 Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id 55B5C2A1A7 for ; Thu, 29 Nov 2018 22:14:23 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726403AbeK3JVU (ORCPT ); Fri, 30 Nov 2018 04:21:20 -0500 Received: from mail-pf1-f193.google.com ([209.85.210.193]:45202 "EHLO mail-pf1-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726264AbeK3JVU (ORCPT ); Fri, 30 Nov 2018 04:21:20 -0500 Received: by mail-pf1-f193.google.com with SMTP id g62so1705266pfd.12 for ; Thu, 29 Nov 2018 14:14:21 -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; bh=rToTEUbJH/iXENfLh5TeV3laYOOSQBG/Wi0PxG4NA78=; b=eK9iSwYTmkn6KztqkuQBv4CL3UdxkA+wXlZY5O+uCFedw3AVHe1txgnIiML2XD2rGo LnBCg9tx7tJSu8a52pI5xfAwv56tgGFlKD/kB8rvZTxAecxAnUgH3eMWubpFkqWGlUcr evFGV1PG7ByEadALaceJFiI8tx8db/Pjauc6A= 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; bh=rToTEUbJH/iXENfLh5TeV3laYOOSQBG/Wi0PxG4NA78=; b=oGzJmXtszrkaHvH6G1Yrp8D79JWM1F0HHrGBHbxIfmrdNVm9aRkEh1Qh5oE2htuNJv 8x6HNYFbmsTOzeiu5PqvL3yPjUTxLp+b6pRmho8ZnLkPrg65fHqMltHxJv6S72z493y5 8WP8lX5zBPLRXJh9ELi+5PuA3FGSQHR/mAeZl0zCd05oCj1c4lh99vGv4UTknVGRLIfP PlemfyHDiTl7ICHMQNbmPqQw6MtRZVTiLb1bZi1psF/sSVkrp2IQCtP892VxAHq3mV5x bVyY0FHf8Lzj5mtI8umP6qkQ04f6Q9l/WFdIuEzaHWAanUL8QEPvNyRgkFvqgoT7B4Eo U/EA== X-Gm-Message-State: AA+aEWZmmBYQF0r48Z5LZkguU3JB34ru1g/TkIzUki+X+zITUvqiFCTY z2/CBOsnzpo1ToZGqpy3J0+NlA== X-Google-Smtp-Source: AFSGD/WMwGf4pU+VGNB4AcZCJ/n0oDHA1oPTsL3+GJsnoc+kEq6IG24XUCMOkBnLp8n84KKMja15/Q== X-Received: by 2002:a62:2cf:: with SMTP id 198mr3158558pfc.67.1543529661149; Thu, 29 Nov 2018 14:14:21 -0800 (PST) Received: from evgreen2.mtv.corp.google.com ([2620:15c:202:201:ffda:7716:9afc:1301]) by smtp.gmail.com with ESMTPSA id c67sm4697690pfg.170.2018.11.29.14.14.19 (version=TLS1_2 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 29 Nov 2018 14:14:20 -0800 (PST) From: Evan Green To: Kishon Vijay Abraham I , Rob Herring , Andy Gross Cc: Douglas Anderson , Stephen Boyd , Evan Green , devicetree@vger.kernel.org, Rob Herring , linux-arm-msm@vger.kernel.org, Can Guo , linux-kernel@vger.kernel.org, Vivek Gautam , Manu Gautam , David Brown , Mark Rutland , linux-soc@vger.kernel.org Subject: [PATCH v1 0/4] phy: qcom-qmp: Fix clock-cells binding and provider Date: Thu, 29 Nov 2018 14:13:53 -0800 Message-Id: <20181129221357.67417-1-evgreen@chromium.org> X-Mailer: git-send-email 2.18.1 Sender: linux-arm-msm-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-arm-msm@vger.kernel.org X-Virus-Scanned: ClamAV using ClamSMTP This series fixes the QMP PHY bindings, which had specified #clock-cells in the parent node, and had set it to 1. Putting it in the parent node is wrong because the clock providers are the child nodes, so this change moves it there. Having it set to 1 is also wrong, since nothing is ever specified as to what should go in that cell. So this changes it to zero. Finally, this change completes a little bit of code to actually allow these exposed clocks to be pointed at in DT. I had no idea how to fix up ipq8074.dtsi. It seems to be completely wrong in that it doesn't specify #clock-cells at all, has no child nodes, and specifies clock-output-names in the parent node. As far as I can tell this doesn't work at all. But I can't add the child nodes myself because I don't know 1) how many there are, and 2) the registers in them. I also have no way to test it. Speaking of testing, I was able to test this on sdm845, but haven't tested msm8996. This patch sits atop the UFS device nodes series [1]. [1] https://lore.kernel.org/lkml/20181026173544.136037-1-evgreen@chromium.org/ Evan Green (4): dt-bindings: phy-qcom-qmp: Move #clock-cells to child arm64: dts: qcom: msm8996: Fix QMP PHY #clock-cells arm64: dts: qcom: sdm845: Fix QMP PHY #clock-cells phy: qcom-qmp: Expose provided clocks to DT .../devicetree/bindings/phy/qcom-qmp-phy.txt | 11 ++++----- arch/arm64/boot/dts/qcom/msm8996.dtsi | 6 +++-- arch/arm64/boot/dts/qcom/sdm845.dtsi | 4 ++-- drivers/phy/qualcomm/phy-qcom-qmp.c | 23 ++++++++++++++++++- 4 files changed, 33 insertions(+), 11 deletions(-)