Received: by 2002:a05:6358:16cc:b0:ea:6187:17c9 with SMTP id r12csp5225408rwl; Sun, 8 Jan 2023 10:46:47 -0800 (PST) X-Google-Smtp-Source: AMrXdXsZMw+C7P9K3TQIwlYVHIwwGcUllSbARfLcxOuQRjA/dct2MLKh47tcvlOq5R+kf9R2SE47 X-Received: by 2002:a17:906:958:b0:7c0:be4d:46d6 with SMTP id j24-20020a170906095800b007c0be4d46d6mr48311629ejd.59.1673203606873; Sun, 08 Jan 2023 10:46:46 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1673203606; cv=none; d=google.com; s=arc-20160816; b=PIaczg0qmQcynJO0nexUK7s2PYtkdCccmxo0ChX9Wf93iUbELF78tS0/z6qRAiRaV1 5nCrkGX81IcoB00jykIOz9iAKyo/moI8unGTupCfbV0CO1etmeLqy5+dPkH617dGobqe BPsfqQiAqvIdF61Fs2J3ZiDuLT2FM7gfanaKIy7Xz31ehuwZ3w2WJsFqU4l+eLo+atiW Nt1DfLYxKduvrpa+UUiYK4d6lIVSmT/w32CpYR6tl8Ccc1/WKpfp9bMlnij8eDYzUpvM JZtoQILouyjscb53F3p4VW8IAq36x1jy6jRmw22XBViIihew0AeFzTkCpv3db7QZxSmd /guA== 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=4ChnjU9YbuZ13rH7KVo18kVjbNMaQprgxl7zjJjRkWs=; b=l/A0tfoEqSoM46vX7to2jcZoPyKJaMJYuDm/pXOUA5K0wyo1t/FT4VDqjhe/29D1yl eKSj+PePiCnHYL55pSkk38BUPHbZFaDdlnBk2KuckhlsWRTMKAuki5CFO1U+xtNT3Nhm Evv+SOorDQKMl46XSdzIX4E+V8MjS1zOduePbxrvIyyUY1UWQghCKpX0T0hwGZlFz5LF 4CDbxk4Pmub539FaEJIl5jqoj7eOh4uLT+i/nGGdGC/HICTTdVYNTzr+CWcMLNLHzQB4 EA8rTVDGfqjrYseOFqvxOkGvcDWSvM3t+jM5fESEHJO+gmZloTnyPOBS9U4teE+ZNgQy p/CA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=toYtzeXX; 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=NONE dis=NONE) header.from=linaro.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id xb13-20020a170907070d00b0081a9c3ca4c3si7248516ejb.374.2023.01.08.10.46.34; Sun, 08 Jan 2023 10:46:46 -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=@linaro.org header.s=google header.b=toYtzeXX; 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=NONE dis=NONE) header.from=linaro.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236066AbjAHSIZ (ORCPT + 51 others); Sun, 8 Jan 2023 13:08:25 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:42290 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236107AbjAHSID (ORCPT ); Sun, 8 Jan 2023 13:08:03 -0500 Received: from mail-yw1-x1136.google.com (mail-yw1-x1136.google.com [IPv6:2607:f8b0:4864:20::1136]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E834663A1 for ; Sun, 8 Jan 2023 10:08:01 -0800 (PST) Received: by mail-yw1-x1136.google.com with SMTP id 00721157ae682-4c15c4fc8ccso86695667b3.4 for ; Sun, 08 Jan 2023 10:08:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=4ChnjU9YbuZ13rH7KVo18kVjbNMaQprgxl7zjJjRkWs=; b=toYtzeXXIY+ryyN/f69MbTo8Z5aAe370LB5gvHIxQjmXPMWILeSldYQP6IzvF8oejM /fdLRUQrf+lRX1QTRfBAyVVCTwEQXXVaZEmhDzpLjQArCSHMxB4cU9ZiEsL8emYb1uik r92XRXg9VAgbeXMxwnsKABj74UtVMhCOO5p08U2zZWgOb0AFO/SGKbc+KZQUjj6flgkM qNAR86sMj14ynmE1gzSKh4/rveMur3xaPgKVq3u9cAZ3z/E+h/5JsMbY0V1gwxmJEgzI qK56zVXwbYio5ajXB3psUfc76m+cdnwuGIXeqpZu1M9Xy4aeA/S7miYi0rRnkjVpGwSF U6+A== 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=4ChnjU9YbuZ13rH7KVo18kVjbNMaQprgxl7zjJjRkWs=; b=pWo/qkgVkRF1aq7J3/R0g7u4ur8RqUM1xKaJt1hRlAj+zOeOoXNf7oNdVyjCxxRuQo uCJW/y8jtf6ea97iMTLWSYdwWDWr40J2ZfJ5s6EPA69xAttHCFAFWN1xa3VQgyVnXpPn 3TwK5V4Nzq3lrmitBm2eAAStsmcE5ywLRXzd45aMAebi511cGCMSZBrhjYf+ZOQ6OkHj 0P0PrklLLA3H6wEzLF1pH0EC8DUoqSb9J/+zR2Kt21KAXlLnXP25apttXV7hpafmcJ5T U2BLOc4JoAU1MqLGUDWWMjFvLlOhs+7yfvCtmre/qBFJFhM9NRT5XDHVVl+n9Xx10lsm X8Sw== X-Gm-Message-State: AFqh2kqsxw27lMxciiigua1Qle6vXlhOgQowU6lrGUCEVB2H/zEGI3YU dIWF0w4FIKGrMIuf/DAgrIP0EmSc9R2+8SwIGYuTGg== X-Received: by 2002:a0d:e3c3:0:b0:432:2458:f6ca with SMTP id m186-20020a0de3c3000000b004322458f6camr1262710ywe.138.1673201281164; Sun, 08 Jan 2023 10:08:01 -0800 (PST) MIME-Version: 1.0 References: <20230108130440.670181-1-robimarko@gmail.com> <20230108130440.670181-2-robimarko@gmail.com> In-Reply-To: From: Dmitry Baryshkov Date: Sun, 8 Jan 2023 20:07:50 +0200 Message-ID: Subject: Re: [PATCH 2/2] arm64: dts: qcom: ipq8074: correct USB3 QMP PHY-s clock output names To: Robert Marko 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,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_PASS autolearn=unavailable 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 20:04, Robert Marko wrote: > > 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. 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. -- With best wishes Dmitry