From: Adrien Thierry <athierry@redhat.com>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Shazad Hussain <quic_shazhuss@quicinc.com>,
agross@kernel.org, andersson@kernel.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Vinod Koul <vkoul@kernel.org>,
Kishon Vijay Abraham I <kishon@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Wesley Cheng <quic_wcheng@quicinc.com>,
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
Subject: Re: [PATCH v1 0/6] arm64: qcom: sa8775p: add support for USB
Date: Tue, 25 Apr 2023 14:03:36 -0400 [thread overview]
Message-ID: <ZEgV+H3yZLp48Dlc@fedora> (raw)
In-Reply-To: <CAA8EJpr27=2jAXbamN6J7yF+7G=L5Af8+XReB5UnFuihcEwMQA@mail.gmail.com>
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.
Best,
Adrien
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
next prev parent reply other threads:[~2023-04-25 18:03 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-21 13:39 [PATCH v1 0/6] arm64: qcom: sa8775p: add support for USB Shazad Hussain
2023-04-21 13:39 ` [PATCH v1 1/6] dt-bindings: usb: qcom,dwc3: Add bindings for SA8775P Shazad Hussain
2023-04-27 14:22 ` Rob Herring
2023-04-27 16:48 ` Shazad Hussain
2023-04-21 13:39 ` [PATCH v1 2/6] dt-bindings: phy: qcom,usb-snps-femto-v2: " Shazad Hussain
2023-04-27 14:22 ` Rob Herring
2023-04-21 13:39 ` [PATCH v1 3/6] dt-bindings: phy: qcom,sc8280xp-qmp-usb3-uni: Add SA8775P USB PHY binding Shazad Hussain
2023-04-27 14:22 ` Rob Herring
2023-04-21 13:39 ` [PATCH v1 4/6] phy: qcom-qmp: Add SA8775P USB3 UNI phy Shazad Hussain
2023-04-22 0:09 ` Dmitry Baryshkov
2023-04-21 13:39 ` [PATCH v1 5/6] arm64: dts: qcom: sa8775p: add USB nodes Shazad Hussain
2023-04-21 13:39 ` [PATCH v1 6/6] arm64: dts: qcom: sa8775p-ride: enable " Shazad Hussain
2023-04-22 0:10 ` Dmitry Baryshkov
2023-04-24 22:35 ` [PATCH v1 0/6] arm64: qcom: sa8775p: add support for USB Adrien Thierry
2023-04-24 23:03 ` Dmitry Baryshkov
2023-04-25 18:03 ` Adrien Thierry [this message]
2023-04-28 21:41 ` Dmitry Baryshkov
2023-05-02 18:49 ` Adrien Thierry
2023-04-26 12:05 ` Shazad Hussain
2023-04-26 23:42 ` Konrad Dybcio
2023-04-27 3:05 ` Shazad Hussain
2023-04-27 17:24 ` Adrien Thierry
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZEgV+H3yZLp48Dlc@fedora \
--to=athierry@redhat.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=kishon@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-usb@vger.kernel.org \
--cc=quic_shazhuss@quicinc.com \
--cc=quic_wcheng@quicinc.com \
--cc=robh+dt@kernel.org \
--cc=vkoul@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).