From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 16662C77B61 for ; Fri, 28 Apr 2023 21:41:46 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1346497AbjD1Vlp (ORCPT ); Fri, 28 Apr 2023 17:41:45 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:54622 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229647AbjD1Vlo (ORCPT ); Fri, 28 Apr 2023 17:41:44 -0400 Received: from mail-wr1-x430.google.com (mail-wr1-x430.google.com [IPv6:2a00:1450:4864:20::430]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D4B7926B9 for ; Fri, 28 Apr 2023 14:41:42 -0700 (PDT) Received: by mail-wr1-x430.google.com with SMTP id ffacd0b85a97d-2fbb99cb297so208517f8f.1 for ; Fri, 28 Apr 2023 14:41:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; t=1682718101; x=1685310101; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=E1Eb5RgOQ6G6T/ToVAmMxv+nVh8+Egk1H9oMyEZ/kPI=; b=B/Iiy08dVrTDqQP14DEVLVYhm+dghBPD41nm5Po2ZOuME8qd4mRykxC/KUS1dma/B8 OYe4mDjjXpKf/mjMk/TINQ2iqlM7f9KPy3QRKOW4LctPN9VjIQFkKZ9bMxW3L71cjS4n 5Vg0L1BGlUKVQxuvhloewhVnEI5cwoh1WLquTnvm8+uN8LOIW8L5mxApE/yg0hq+CPvf AxJx5nX4jrGwm5xKVJ4ZcxJLOV8AzTqeA5Rlp/1R318ochH9XwDOwv5ykAM+4socbTnM 3GDRpzhwcs1Yc2y0k6suRwULbbgiY2ZDeB51EF4xiUDHCQlaAuVq2nInSiOXRthJQS+q hOgg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1682718101; x=1685310101; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=E1Eb5RgOQ6G6T/ToVAmMxv+nVh8+Egk1H9oMyEZ/kPI=; b=cPQgekoww1WFheffxUYbSU/DgdfEykueyknuoz0gz5MWV4KkHYhMThG1KgQftUmJbU T3ij0h+1nQHl+cHWREbs75AfTQuZwiEawz9oEEbVTgJ76ZK/kyAky7ed4JOc+0x4pPfS DIbmC3ZLvnQpZYwHTV5m+QONgnCCD9DdmR8JVStIVG2v3wo0UaqAjO+AXmnDDqgqTMUR OFBdnMuowXHgek4JL/MYxUJYFxYQ4cKH1BoQpRy9aSMt6gYAwYyFR1FUkIkWT1qcxZpT 0cApwFL1zjyX6JSvD3Dxh+sQiNs//ATigcre7jZVci4gdeh+dzLxndCkZ6HnFitDTKEx KbPA== X-Gm-Message-State: AC+VfDws33hUvrFS0h5exPdRF2R7R/DUjVeD9QfARCvWP46qnL9bnX4f iKZvWJwfavds4Xy0gxOG0FBTmg== X-Google-Smtp-Source: ACHHUZ5RGdr21sjT6mATshpr/YItNaJEnWe3GQDudidU/5n3YX0H1yKJh85dhh6eziC69IuYXUMV6Q== X-Received: by 2002:adf:e481:0:b0:2ee:f1f0:14bb with SMTP id i1-20020adfe481000000b002eef1f014bbmr5138651wrm.49.1682718101303; Fri, 28 Apr 2023 14:41:41 -0700 (PDT) Received: from [10.6.26.43] ([212.140.138.202]) by smtp.gmail.com with ESMTPSA id d15-20020adfe84f000000b002fb60c7995esm22205929wrn.8.2023.04.28.14.41.40 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 28 Apr 2023 14:41:40 -0700 (PDT) Message-ID: <3dc6e993-bcca-4e0d-5aca-686fcc8b5b73@linaro.org> Date: Sat, 29 Apr 2023 00:41:39 +0300 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.10.0 Subject: Re: [PATCH v1 0/6] arm64: qcom: sa8775p: add support for USB Content-Language: en-GB To: Adrien Thierry Cc: Shazad Hussain , agross@kernel.org, andersson@kernel.org, robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org, Konrad Dybcio , Vinod Koul , Kishon Vijay Abraham I , Greg Kroah-Hartman , Wesley Cheng , linux-arm-msm@vger.kernel.org, linux-phy@lists.infradead.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org References: <20230421133922.8520-1-quic_shazhuss@quicinc.com> From: Dmitry Baryshkov In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org On 25/04/2023 21:03, Adrien Thierry wrote: > Hi Dmitry, > >> Semi-random suggestion, but could you please try using >> clk_regmap_phy_mux/clk_regmap_phy_mux_ops for USB pipe clk src? > > Which specific clock are you refering to? I'm not very familiar with > those, in the device tree I'm seeing "pipe" clocks for usb_0 and usb_1 > phys, but not for usb_2, which is the one that's causing issues. > Ah, I see. Could you please try adding the 'qcom,select-utmi-as-pipe-clk' property to the usb_2 host node and running the test again? -- With best wishes Dmitry