Received: by 2002:ad5:4acb:0:0:0:0:0 with SMTP id n11csp3013588imw; Wed, 6 Jul 2022 15:58:18 -0700 (PDT) X-Google-Smtp-Source: AGRyM1s2HAUlp9I08QIhck9LBwJzQVoKwre2J8xLYBoixNBgYbYU9SKch0t3wSzWcCNQvKqrbtmv X-Received: by 2002:a17:907:60d3:b0:726:b4ef:9bfa with SMTP id hv19-20020a17090760d300b00726b4ef9bfamr42598756ejc.7.1657148297949; Wed, 06 Jul 2022 15:58:17 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1657148297; cv=none; d=google.com; s=arc-20160816; b=H+BQo2UbppwOPIzyoZCqCk4rxTI1OyF3Ijbay75zGHFIb52ZhgentLWcTpvBKFQRSr Qwjr6fbxzcayGKSr2wchDgDUxu9ipdOXXQFiia35z1NYPr3xlwpAMTjjJd9C4mYA3mrd GJ/v5BdDavPM63508TYYepRZnG9Ss7CDQOFL4+QqDxrU7/gzxJaW0kEX36jTH+7iAxUa A5Cx7KMo5qCXTAXyHfFmXeW7CTBXrFKmvu5F0xw9nSkyDtmtT5E/ye8KTzFlDHxrA//L uytcR/HwcAOY8sGGVtKuax1oqG4NtrCgwAMUTMeUozdPSUonDiUJUgESW41q7cezAsNP gjTA== 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=7/oAWvKanO4cSeNPe/XMaWgSS54K0jHxPM6w4qmhtko=; b=VDLRrTdWtUQQAPUcV0qa9KIGJWUgo5XEzaIOst0O69nnVA6jGUyKjj94DqOa/6WpTM TDUdm5EqJOSKijtPRH7IuWUt0bbmPKvl/iM54ebELqamMK1opouQGbvWfvz7xdCeBD+p JbyFufihurcFtDf82nLDeuSGAcMoadxPGxgNs+igy7bOKbqvmFKqA/1+/YLPR0xiMZLd mzZ54IP4Rs6lulRgYlHoDOM7sXYSJd7FF+cQS4ExU51xWkfTtGVOgUtXuYeEFTBvwa9A 87eT6nJIV24RMChJ/lrNJmUy/iLvRcbtvkpfAxXf3bEYFNikY3Fnca+T7CmcmPooNb5S chmw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20210112 header.b="q7SEN/Nm"; 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=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id x69-20020a50bacb000000b00435583af2b3si1741616ede.86.2022.07.06.15.57.52; Wed, 06 Jul 2022 15:58:17 -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=@gmail.com header.s=20210112 header.b="q7SEN/Nm"; 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=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234048AbiGFWyb (ORCPT + 99 others); Wed, 6 Jul 2022 18:54:31 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:47502 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233425AbiGFWy2 (ORCPT ); Wed, 6 Jul 2022 18:54:28 -0400 Received: from mail-ej1-x633.google.com (mail-ej1-x633.google.com [IPv6:2a00:1450:4864:20::633]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 05A2E2AE01; Wed, 6 Jul 2022 15:54:26 -0700 (PDT) Received: by mail-ej1-x633.google.com with SMTP id d2so29547457ejy.1; Wed, 06 Jul 2022 15:54:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=7/oAWvKanO4cSeNPe/XMaWgSS54K0jHxPM6w4qmhtko=; b=q7SEN/NmDZonxy6H4bNWTGEeJak28goH3x+I/idgjolnE6sb5W3mpodc8EVxz+Kyia ijIOEAPx7Qd/Cp6PlxXF2t+D5A51tI0kSRWPw70hl0Mocibu1zqDQJxrJzDp/i1IY20U 0XrHs94NGXE1JgzSXaqIJ/9iH4eDNfu9QCW0fVIUvWzYLSwFXkaTQRGi2S8E2qVXBVme 1Z9KgV7eBe/a5GMgH8Dbtc2vByM/GAVxmfxz9oedYy8Man0O8SBI1xswWl8A4zeJt9Zm 0ycz0gSTsJ5qFkZGXKGTY4Le8Hp8rI/NP+Y7oYYuD3e3Ag8qaOX0w0rOJgIrh+MoOdPD cm+A== 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=7/oAWvKanO4cSeNPe/XMaWgSS54K0jHxPM6w4qmhtko=; b=YXF/ihq11gC1KKdqtQY85y/EaqE8e62p3sxQSB7RRsa5y4yOk5r6AeJq6JDWuCaiiU hb3L686NSEwQvEYUmBWVwTmTtCjY91HGvq637evAoCSt5JY+ndYd/UuaV0vdMuyaBbBE iS/lEaUpxcCX7aPW388LLpQe/phj62vQKV6DhAoinfpSzgRw15dq3xOEEtqcwtQcSJuD NGnVaCiCsJbWvjnc346d6VQExm7Hrm+Ax8250uImFzj4S+JaF2BUTzz2lqAde5k/C7wE X9gCAtEhEjp4e4YTIEGLeoU7DkF1fdaJJd+TmdNKluGDCSfaU4jVMeutvdpo9P7bM68b kEbA== X-Gm-Message-State: AJIora+bzPbsiciS62at71yh5MWfd60jYHGz0szglpse3AWJmOKxspXd IDWMk5I7s3ExSh6mKFtLCCA= X-Received: by 2002:a17:907:9005:b0:715:76ce:4476 with SMTP id ay5-20020a170907900500b0071576ce4476mr41077848ejc.560.1657148064512; Wed, 06 Jul 2022 15:54:24 -0700 (PDT) Received: from localhost.localdomain (93-42-70-190.ip85.fastwebnet.it. [93.42.70.190]) by smtp.googlemail.com with ESMTPSA id d7-20020a170906304700b006fe921fcb2dsm1767637ejd.49.2022.07.06.15.54.23 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 06 Jul 2022 15:54:24 -0700 (PDT) From: Christian Marangi To: Bjorn Andersson , Andy Gross , Konrad Dybcio , 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 Cc: Christian Marangi Subject: [PATCH v2 0/4] clk: qcom: Drop use of pxo/cxo_board for rpm devices Date: Thu, 7 Jul 2022 00:53:17 +0200 Message-Id: <20220706225321.26215-1-ansuelsmth@gmail.com> X-Mailer: git-send-email 2.36.1 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,FREEMAIL_FROM, RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE 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 Trying to convert every driver used by ipq806x to parent_data api, I notice RPM was still using pxo_board clk. pxo and pxo_board are the same clock and are defined just to handle old clock definition. It was discovered that rpm is the last driver using pxo_board instead of pxo. While updating the rpm driver I notice the documentation was also wrong, so this series also fix that. v2: - Add review tag to DTS patch - Drop clock-output-names patch - Use pxo/cxo_board clock names - Remove if nesting from Documentation - Use min/maxItems in Documentation to describe clocks Christian Marangi (4): dt-bindings: clock: fix wrong clock documentation for qcom,rpmcc ARM: DTS: qcom: add rpmcc missing clocks for apq/ipq8064 and msm8660 clk: qcom: clk-rpm: convert to parent_data API clk: qcom: gcc-ipq806x: remove cc_register_board for pxo and cxo .../devicetree/bindings/clock/qcom,rpmcc.yaml | 85 ++++++++++++++++++- arch/arm/boot/dts/qcom-apq8064.dtsi | 2 + arch/arm/boot/dts/qcom-ipq8064.dtsi | 2 + arch/arm/boot/dts/qcom-msm8660.dtsi | 4 +- drivers/clk/qcom/clk-rpm.c | 24 ++++-- drivers/clk/qcom/gcc-ipq806x.c | 8 -- 6 files changed, 106 insertions(+), 19 deletions(-) -- 2.36.1