Message ID | 20230108130440.670181-2-robimarko@gmail.com |
---|---|
State | New |
Headers |
Return-Path: <linux-kernel-owner@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:a5d:4e01:0:0:0:0:0 with SMTP id p1csp1697044wrt; Sun, 8 Jan 2023 05:09:25 -0800 (PST) X-Google-Smtp-Source: AMrXdXs0hiDncgZk0DaLnWXwgoh97wlJKgGxl+J3Z24ZnaIcWNywjJu8Ya8BnDl6rWh5jYVgBv/L X-Received: by 2002:a17:90a:4282:b0:223:f131:3604 with SMTP id p2-20020a17090a428200b00223f1313604mr65205454pjg.17.1673183364650; Sun, 08 Jan 2023 05:09:24 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1673183364; cv=none; d=google.com; s=arc-20160816; b=arqJ7rRvdpQmG9GKrp3tQXaL1Q6RjFUwt3uEBNdI0jHoN+MlA2NpPYN5G8gmXJFp2r dnfis9Q745rB5fruLhqbjN3feMKnXihCiedOHlLXvNuLmPA8TJOnVnc3x3l2cUsOiyZE kZZDgtWmstTgay8Hb212hA+xUvCEYGwOZam6j9O31IZtFe2kZuG1pl9oj5lUp7WXJ+AS o6nJFMWn4oo3kbYxZ17ya81Q5ctzox6Y6Y5FkGc95FUpVWZtZQUABtzz4SH5lr3KG3ap ZHrcUm/n17Dj7u3ZEaDuL3iusbdloS/1YDvWyHcAD8kdjf2m/Fpv38mJzgi58/1OZqO/ Pfog== 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 :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature; bh=ZSsCe1/vYrCPdq2/qm0aU0QWLaInEUASjxbLN6gEMCs=; b=q20tV9bqDXeKkJetUhkC5uZSPWFJn+yQMsRDyhG9tM4qcaLHeUg9o9BH0lEYBouIrj O+SVbUDFVtpcFvv9jUfvKrc0i7EqpZv9izuwdDUje9YeAOdqNgewi1yNe27OKaqulUFF CLxqo1OOmM5tAMsZ9vsx7u+5ZgiiH/SuDDw+MpT4I61nln3KKlCEH83Vv6mvI3yAJjas o9K1Wx5e6+af4LO3S6AHUSCr5k/+xwLMpDobco+dkYIAAoPoNpMnlgFdKPXMpjpYEKbQ 8Tuw8sRIS18egSjwEVcIHmA1oVqp1r8dfKlSGGlcVKBM+Yyd1uyEVXhQ7SX6AdANb7Ho WFJA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20210112 header.b=LyJWVkmk; 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: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id lr8-20020a17090b4b8800b00218ac70fdefsi8001817pjb.183.2023.01.08.05.09.12; Sun, 08 Jan 2023 05:09:24 -0800 (PST) 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=LyJWVkmk; 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 S233265AbjAHNEv (ORCPT <rfc822;old.home.clock.tower@gmail.com> + 99 others); Sun, 8 Jan 2023 08:04:51 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36790 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232900AbjAHNEs (ORCPT <rfc822;linux-kernel@vger.kernel.org>); Sun, 8 Jan 2023 08:04:48 -0500 Received: from mail-ed1-x52d.google.com (mail-ed1-x52d.google.com [IPv6:2a00:1450:4864:20::52d]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B8633DF83; Sun, 8 Jan 2023 05:04:47 -0800 (PST) Received: by mail-ed1-x52d.google.com with SMTP id c17so8691350edj.13; Sun, 08 Jan 2023 05:04:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:from:to:cc:subject:date :message-id:reply-to; bh=ZSsCe1/vYrCPdq2/qm0aU0QWLaInEUASjxbLN6gEMCs=; b=LyJWVkmkVQDracXJJR1Fnzi4JLU/adPerzQZNgCGezlTDDfY33AgCdT+6EkACT2wI/ gI/6ciVPbG6LDcZvrK9EQwNkvV6SbzOKj3utJzad3cneej0JH7aHqB9gr4ghzZSNS49y y1ZMjiFHO7iiw14O0Go4NNvmJNxAjZBrtcVU020KlNsQGWmx9VELCzujvVjuxbpBmUN1 Hh73QCrZ1+4Hf+NHQn4pCUtcEAEEcS7SCUbkBZn87zPcluoOkFCT2URY3vkidBWTrPXu 0czzc3o/JVBCrfz9xfrSXJQaPEXwNRMhZ0PAaqr07QSWQZiobvF/CTaHSCQcq25rPQTU i8Mg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=ZSsCe1/vYrCPdq2/qm0aU0QWLaInEUASjxbLN6gEMCs=; b=JAqH9Hr1B7AI3mC/goZPotGe/nSyKBGpvsehq3iQoiKQx1D74BhW1jRdVjq+jYMAPH x4FEZfYu51Kjs7SXw6ip2PhkWF1xa6r4Gjs5lmzerCVuF6ZgcweRQFnzemAc29ilEaWM 5rx/c/yTEZ/5sxYqC7aWESVIv/Ay9pJBOcFjgc78jUUNIsSfGRKrOe1Ke3mACaWZnfZs KsrJhIeprpDgJWiEzanYmGfXFsMLyhW5MWkKeEGf5p2aFiO9xiwOO4zhaLbnSh3ZDMA5 0VQ1DFXSOllk5z/7ZS5gJi+TZ03CJNfRE2inzDnmh1vcrB9TzbStmG59QZZnQ429gG3R O+EA== X-Gm-Message-State: AFqh2krQu16ajF7LGKjckR/NR436CyeWyFkkvLM7MtjHR2CPNSvWTKd4 mS8zLi9jlwbHwzwAjQhAK9uZh7VPve64Ow== X-Received: by 2002:aa7:cd49:0:b0:497:d8ea:d79c with SMTP id v9-20020aa7cd49000000b00497d8ead79cmr5259999edw.27.1673183086239; Sun, 08 Jan 2023 05:04:46 -0800 (PST) Received: from fedora.. (cpezg-94-253-128-11-cbl.xnet.hr. [94.253.128.11]) by smtp.googlemail.com with ESMTPSA id l10-20020aa7d94a000000b0048ebf8a5736sm2499285eds.21.2023.01.08.05.04.45 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 08 Jan 2023 05:04:45 -0800 (PST) From: Robert Marko <robimarko@gmail.com> To: agross@kernel.org, andersson@kernel.org, konrad.dybcio@linaro.org, robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org, mturquette@baylibre.com, sboyd@kernel.org, linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org Cc: Robert Marko <robimarko@gmail.com> Subject: [PATCH 2/2] arm64: dts: qcom: ipq8074: correct USB3 QMP PHY-s clock output names Date: Sun, 8 Jan 2023 14:04:40 +0100 Message-Id: <20230108130440.670181-2-robimarko@gmail.com> X-Mailer: git-send-email 2.39.0 In-Reply-To: <20230108130440.670181-1-robimarko@gmail.com> References: <20230108130440.670181-1-robimarko@gmail.com> 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 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: <linux-kernel.vger.kernel.org> X-Mailing-List: linux-kernel@vger.kernel.org X-getmail-retrieved-from-mailbox: =?utf-8?q?INBOX?= X-GMAIL-THRID: =?utf-8?q?1754459920071675548?= X-GMAIL-MSGID: =?utf-8?q?1754459920071675548?= |
Series |
[1/2] clk: qcom: ipq8074: populate fw_name for usb3phy-s
|
|
Commit Message
Robert Marko
Jan. 8, 2023, 1:04 p.m. UTC
It seems that clock-output-names for the USB3 QMP PHY-s where set without
actually checking what is the GCC clock driver expecting, so clock core
could never actually find the parents for usb0_pipe_clk_src and
usb1_pipe_clk_src clocks in the GCC driver.
So, correct the names to be what the driver expects so that parenting
works.
Before:
gcc_usb0_pipe_clk_src 0 0 0 125000000 0 0 50000 Y
gcc_usb1_pipe_clk_src 0 0 0 125000000 0 0 50000 Y
After:
usb3phy_0_cc_pipe_clk 1 1 0 125000000 0 0 50000 Y
usb0_pipe_clk_src 1 1 0 125000000 0 0 50000 Y
gcc_usb0_pipe_clk 1 1 0 125000000 0 0 50000 Y
usb3phy_1_cc_pipe_clk 1 1 0 125000000 0 0 50000 Y
usb1_pipe_clk_src 1 1 0 125000000 0 0 50000 Y
gcc_usb1_pipe_clk 1 1 0 125000000 0 0 50000 Y
Fixes: 5e09bc51d07b ("arm64: dts: ipq8074: enable USB support")
Signed-off-by: Robert Marko <robimarko@gmail.com>
---
arch/arm64/boot/dts/qcom/ipq8074.dtsi | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
Comments
On Sun, 8 Jan 2023 at 15:04, Robert Marko <robimarko@gmail.com> wrote: > > It seems that clock-output-names for the USB3 QMP PHY-s where set without > actually checking what is the GCC clock driver expecting, so clock core > could never actually find the parents for usb0_pipe_clk_src and > usb1_pipe_clk_src clocks in the GCC driver. > > So, correct the names to be what the driver expects so that parenting > works. > > Before: > gcc_usb0_pipe_clk_src 0 0 0 125000000 0 0 50000 Y > gcc_usb1_pipe_clk_src 0 0 0 125000000 0 0 50000 Y > > After: > usb3phy_0_cc_pipe_clk 1 1 0 125000000 0 0 50000 Y > usb0_pipe_clk_src 1 1 0 125000000 0 0 50000 Y > gcc_usb0_pipe_clk 1 1 0 125000000 0 0 50000 Y > usb3phy_1_cc_pipe_clk 1 1 0 125000000 0 0 50000 Y > usb1_pipe_clk_src 1 1 0 125000000 0 0 50000 Y > gcc_usb1_pipe_clk 1 1 0 125000000 0 0 50000 Y > > Fixes: 5e09bc51d07b ("arm64: dts: ipq8074: enable USB support") > Signed-off-by: Robert Marko <robimarko@gmail.com> Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org> Nevertheless, could you please add .fw_name to these entries in gcc driver (as you did for other clocks in 35dc8e101a8e ("clk: qcom: ipq8074: populate fw_name for all parents")) and add all pipe clocks to the gcc node? This way you can drop clock-output-names from the PHY nodes. > --- > arch/arm64/boot/dts/qcom/ipq8074.dtsi | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) [skipped]
On Sun, 8 Jan 2023 at 18:32, Dmitry Baryshkov <dmitry.baryshkov@linaro.org> wrote: > > On Sun, 8 Jan 2023 at 15:04, Robert Marko <robimarko@gmail.com> wrote: > > > > It seems that clock-output-names for the USB3 QMP PHY-s where set without > > actually checking what is the GCC clock driver expecting, so clock core > > could never actually find the parents for usb0_pipe_clk_src and > > usb1_pipe_clk_src clocks in the GCC driver. > > > > So, correct the names to be what the driver expects so that parenting > > works. > > > > Before: > > gcc_usb0_pipe_clk_src 0 0 0 125000000 0 0 50000 Y > > gcc_usb1_pipe_clk_src 0 0 0 125000000 0 0 50000 Y > > > > After: > > usb3phy_0_cc_pipe_clk 1 1 0 125000000 0 0 50000 Y > > usb0_pipe_clk_src 1 1 0 125000000 0 0 50000 Y > > gcc_usb0_pipe_clk 1 1 0 125000000 0 0 50000 Y > > usb3phy_1_cc_pipe_clk 1 1 0 125000000 0 0 50000 Y > > usb1_pipe_clk_src 1 1 0 125000000 0 0 50000 Y > > gcc_usb1_pipe_clk 1 1 0 125000000 0 0 50000 Y > > > > Fixes: 5e09bc51d07b ("arm64: dts: ipq8074: enable USB support") > > Signed-off-by: Robert Marko <robimarko@gmail.com> > > Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org> > > Nevertheless, could you please add .fw_name to these entries in gcc > driver (as you did for other clocks in 35dc8e101a8e ("clk: qcom: > ipq8074: populate fw_name for all parents")) and add all pipe clocks > to the gcc node? This way you can drop clock-output-names from the PHY > nodes. As you noticed they are in the GCC patch already, after the PCI PIPE parenting fixes are merged I plan to add them to the GCC node to avoid global lookup. Regards, Robert > > > --- > > arch/arm64/boot/dts/qcom/ipq8074.dtsi | 4 ++-- > > 1 file changed, 2 insertions(+), 2 deletions(-) > > [skipped] > > -- > With best wishes > Dmitry
On Sun, 8 Jan 2023 at 20:04, Robert Marko <robimarko@gmail.com> wrote: > > On Sun, 8 Jan 2023 at 18:32, Dmitry Baryshkov > <dmitry.baryshkov@linaro.org> wrote: > > > > On Sun, 8 Jan 2023 at 15:04, Robert Marko <robimarko@gmail.com> wrote: > > > > > > It seems that clock-output-names for the USB3 QMP PHY-s where set without > > > actually checking what is the GCC clock driver expecting, so clock core > > > could never actually find the parents for usb0_pipe_clk_src and > > > usb1_pipe_clk_src clocks in the GCC driver. > > > > > > So, correct the names to be what the driver expects so that parenting > > > works. > > > > > > Before: > > > gcc_usb0_pipe_clk_src 0 0 0 125000000 0 0 50000 Y > > > gcc_usb1_pipe_clk_src 0 0 0 125000000 0 0 50000 Y > > > > > > After: > > > usb3phy_0_cc_pipe_clk 1 1 0 125000000 0 0 50000 Y > > > usb0_pipe_clk_src 1 1 0 125000000 0 0 50000 Y > > > gcc_usb0_pipe_clk 1 1 0 125000000 0 0 50000 Y > > > usb3phy_1_cc_pipe_clk 1 1 0 125000000 0 0 50000 Y > > > usb1_pipe_clk_src 1 1 0 125000000 0 0 50000 Y > > > gcc_usb1_pipe_clk 1 1 0 125000000 0 0 50000 Y > > > > > > Fixes: 5e09bc51d07b ("arm64: dts: ipq8074: enable USB support") > > > Signed-off-by: Robert Marko <robimarko@gmail.com> > > > > Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org> > > > > Nevertheless, could you please add .fw_name to these entries in gcc > > driver (as you did for other clocks in 35dc8e101a8e ("clk: qcom: > > ipq8074: populate fw_name for all parents")) and add all pipe clocks > > to the gcc node? This way you can drop clock-output-names from the PHY > > nodes. > > As you noticed they are in the GCC patch already, after the PCI PIPE > parenting fixes > are merged I plan to add them to the GCC node to avoid global lookup. Good! I think the pcie fixes are already in Bjorn's tree. And you might send the dts fix anyway, in the worst case the driver will just ignore the DT clocks.
diff --git a/arch/arm64/boot/dts/qcom/ipq8074.dtsi b/arch/arm64/boot/dts/qcom/ipq8074.dtsi index a0f7460020c2..3d1fccdf37c7 100644 --- a/arch/arm64/boot/dts/qcom/ipq8074.dtsi +++ b/arch/arm64/boot/dts/qcom/ipq8074.dtsi @@ -263,7 +263,7 @@ usb1_ssphy: phy@58200 { #clock-cells = <0>; clocks = <&gcc GCC_USB1_PIPE_CLK>; clock-names = "pipe0"; - clock-output-names = "gcc_usb1_pipe_clk_src"; + clock-output-names = "usb3phy_1_cc_pipe_clk"; }; }; @@ -306,7 +306,7 @@ usb0_ssphy: phy@78200 { #clock-cells = <0>; clocks = <&gcc GCC_USB0_PIPE_CLK>; clock-names = "pipe0"; - clock-output-names = "gcc_usb0_pipe_clk_src"; + clock-output-names = "usb3phy_0_cc_pipe_clk"; }; };