Received: by 2002:a05:6358:16cc:b0:ea:6187:17c9 with SMTP id r12csp5218077rwl; Sun, 8 Jan 2023 10:37:15 -0800 (PST) X-Google-Smtp-Source: AMrXdXsCkkvvgMxwxt63lO9o6s6fHYjwVhKlZkJa8Js2SzoI06ENETf2PiJbfuP8QJB2UOuBVZHR X-Received: by 2002:a17:906:3a93:b0:7c0:f7b0:9aed with SMTP id y19-20020a1709063a9300b007c0f7b09aedmr49943519ejd.55.1673203035400; Sun, 08 Jan 2023 10:37:15 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1673203035; cv=none; d=google.com; s=arc-20160816; b=kB657Me7CjM8BDWDYf6iqD0DGDPu91svhPlvOJeUjl9GUQSqNuKGHG1NVeGluBLyC/ cfI6jw4bok0faRHMNU5H8Rcd4xMDSNZRtI9xoDQ9JVXR6Hre3pRUtZp8p5z7tx8xpT37 n+qiN9MKLPn9NUYsrkWYP7fUjZXy07KwhPcLIKII3774d46cAayEixHWSBbunqHY2GDa S4hwkmOFkuTb9eHYZzCKHSIwF1KDVTKAthRjLwoLWb3n0XSsMab5vCx+gSPNN/jEyNkr EuL+OlbH2OkpgvOh2F5WRJj0eYTTHg6FMCNxc0+kZ2leq51w2XuMy+JQI1qGNVdzLe+z bTEQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=TK9smNKM8L5ERP2lizjy7Jnwhohf+9dokgzX4r6ntOI=; b=OWHEVgETX7AM6D6R1K0XahTF9AwVM1PZzoJ2hXKblo4X4B2lKSoCl81Gy78+F+UEPQ z4Z6KDDafeeofDhBaM+XyrzoNWmAPQJp5jOyVxS/ySYI5BU3Us+U5WXezNyCmBNjre7Q 6sLxU54P7PUvx9gByQfbzVhI6V12PLg6PNs5helvg+2YTlHoVuSVjT97Sw3WRQIRzHeZ sgqIVXBpdy67wm8wV4WscRdX7n2NZkEsEpUIZDtvtDEq4Q0iTUuPEGpYNzOdXBxR0MjI XQNYjz404N5aGT1EMu32EwA+Im51HJ0kdmOOiKvDBaP3ppFbG1OBkdRcuUNWhuRT66Hq RU7Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20210112 header.b=Qf7hnJIc; 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 gt33-20020a1709072da100b007c151fc73d0si9065118ejc.653.2023.01.08.10.37.03; Sun, 08 Jan 2023 10:37:15 -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=Qf7hnJIc; 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 S235078AbjAHSEb (ORCPT + 51 others); Sun, 8 Jan 2023 13:04:31 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39710 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231410AbjAHSE2 (ORCPT ); Sun, 8 Jan 2023 13:04:28 -0500 Received: from mail-pj1-x1031.google.com (mail-pj1-x1031.google.com [IPv6:2607:f8b0:4864:20::1031]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id DBBF7FADA; Sun, 8 Jan 2023 10:04:26 -0800 (PST) Received: by mail-pj1-x1031.google.com with SMTP id w4-20020a17090ac98400b002186f5d7a4cso10492720pjt.0; Sun, 08 Jan 2023 10:04:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=TK9smNKM8L5ERP2lizjy7Jnwhohf+9dokgzX4r6ntOI=; b=Qf7hnJIcbNkPLRgDeCx1mPkm3FYoZY/ZKQHdqDqtPrbwb3JiWrQJJxODlVbmrM6OKk 5t0UCbk+pKur7Xir5n1lAv9auFRdp3xqsBHGLPWKddFOEtB6Fpx3mLlMHovBc7JgzjJd 1GTSG34qi4u4RZyhAhP3p3edne34Zf7Pzy6MEXAiTDgKuyZtvbpGl5RcdFF97NQ6+y8v atiKgb/c1UgTjgIccFghn9IqqlCidZr790vyEBD9UUXhSZEpbqcJwv1C7noK7TdIRFJz n6ej8uwFD+KB/lLpluuNgPmFBo0c+qk0SeLuGsvPRQW9hCKnKuGYlLaBLPP4G988qyCW Cjbw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=TK9smNKM8L5ERP2lizjy7Jnwhohf+9dokgzX4r6ntOI=; b=ntq+RZjAppx5+pUCj0ReC3C59Ccbv2D8qoB+4ocLWES6T+3DcmMi9HVysHrEV2ZZk7 IXzypfMd4mGGBnVkH7g1QRjvYVEKzloHKxlAfVQyITV9khZjopZF4Gl1bwfc5+51zZuY XP3/SfU2EBUFmLIlFCTa1mRPNCpp43iPvZzKUEkBrBS/jHuQHEFWRjGi7/d3siQJHbGq pXW+yrMsKqk0LbAIab7InuIcMZXe9ggIVpzfOO8q+EtW+66nY2AaboHwhPyj9DRCSv9i iBgvQlrcD6PqNkOZ2QdJWwXRv4uhtSL2ojWFOhd7Cgcl4Wzk4d0gzlhMpufguGLI1d0U c2Gw== X-Gm-Message-State: AFqh2kpcn1jP2U1Fo9s9mC2DF/fXPC7HVUnB+ivaKwtpiUSL6PNxt44C IU2Kh0Y9DImoM3f6tM02G828IeBqS/LVCtmEqEw= X-Received: by 2002:a17:902:e384:b0:191:34ee:8faa with SMTP id g4-20020a170902e38400b0019134ee8faamr2468426ple.111.1673201066408; Sun, 08 Jan 2023 10:04:26 -0800 (PST) MIME-Version: 1.0 References: <20230108130440.670181-1-robimarko@gmail.com> <20230108130440.670181-2-robimarko@gmail.com> In-Reply-To: From: Robert Marko Date: Sun, 8 Jan 2023 19:04:15 +0100 Message-ID: Subject: Re: [PATCH 2/2] arm64: dts: qcom: ipq8074: correct USB3 QMP PHY-s clock output names To: Dmitry Baryshkov Cc: 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 Content-Type: text/plain; charset="UTF-8" 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: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, 8 Jan 2023 at 18:32, Dmitry Baryshkov wrote: > > On Sun, 8 Jan 2023 at 15:04, Robert Marko 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 > > Reviewed-by: Dmitry Baryshkov > > 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