From: Ritesh Kumar <quic_riteshk@quicinc.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: <robin.clark@oss.qualcomm.com>, <lumag@kernel.org>,
<abhinav.kumar@linux.dev>, <jessica.zhang@oss.qualcomm.com>,
<sean@poorly.run>, <marijn.suijten@somainline.org>,
<maarten.lankhorst@linux.intel.com>, <mripard@kernel.org>,
<tzimmermann@suse.de>, <airlied@gmail.com>, <simona@ffwll.ch>,
<robh@kernel.org>, <krzk+dt@kernel.org>, <conor+dt@kernel.org>,
<quic_mahap@quicinc.com>, <andersson@kernel.org>,
<konradybcio@kernel.org>, <mani@kernel.org>,
<James.Bottomley@hansenpartnership.com>,
<martin.petersen@oracle.com>, <vkoul@kernel.org>,
<kishon@kernel.org>, <cros-qcom-dts-watchers@chromium.org>,
<linux-phy@lists.infradead.org>, <linux-arm-msm@vger.kernel.org>,
<dri-devel@lists.freedesktop.org>,
<freedreno@lists.freedesktop.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-scsi@vger.kernel.org>,
<quic_vproddut@quicinc.com>
Subject: Re: [PATCH v2 0/3] Add edp reference clock for lemans
Date: Wed, 15 Oct 2025 14:49:08 +0530 [thread overview]
Message-ID: <4bd619e7-e9ca-44a8-9d36-10c18d7a8157@quicinc.com> (raw)
In-Reply-To: <7jmk3txdrnit6zn7ufra7davmomggd3graizdu6wqonp3lljza@mfnxt2owpknq>
On 10/13/2025 6:04 PM, Dmitry Baryshkov wrote:
> On Mon, Oct 13, 2025 at 04:18:03PM +0530, Ritesh Kumar wrote:
> > On lemans chipset, edp reference clock is being voted by ufs mem phy
> > (ufs_mem_phy: phy@1d87000). But after commit 77d2fa54a9457
> > ("scsi: ufs: qcom : Refactor phy_power_on/off calls") edp reference
> > clock is getting turned off, leading to below phy poweron failure on
> > lemans edp phy.
>
> How does UFS turn on eDP reference clock?
In lemans, GCC_EDP_REF_CLKREF_EN is voted as qref clock in ufs_mem_phy.
ufs_mem_phy: phy@1d87000 {
compatible = "qcom,sa8775p-qmp-ufs-phy";
reg = <0x0 0x01d87000 0x0 0xe10>;
/*
* Yes, GCC_EDP_REF_CLKREF_EN is correct in qref. It
* enables the CXO clock to eDP *and* UFS PHY.
*/
clocks = <&rpmhcc RPMH_CXO_CLK>,
<&gcc GCC_UFS_PHY_PHY_AUX_CLK>,
<&gcc GCC_EDP_REF_CLKREF_EN>;
clock-names = "ref", "ref_aux", "qref";
>
>
next prev parent reply other threads:[~2025-10-15 9:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-13 10:48 Ritesh Kumar
2025-10-13 10:48 ` [PATCH v2 1/3] dt-bindings: phy: qcom-edp: Add edp ref clk for sa8775p Ritesh Kumar
2025-10-13 12:34 ` Dmitry Baryshkov
2025-10-28 9:54 ` Ritesh Kumar
2025-10-13 12:37 ` Dmitry Baryshkov
2025-10-15 14:43 ` Rob Herring
2025-10-28 9:57 ` Ritesh Kumar
2025-10-27 17:05 ` Bjorn Andersson
2025-10-28 10:16 ` Ritesh Kumar
2025-10-13 10:48 ` [PATCH v2 2/3] dt-bindings: display/msm: qcom,sa8775p-mdss: update edp phy example Ritesh Kumar
2025-10-13 12:35 ` [PATCH v2 2/3] dt-bindings: display/msm: qcom, sa8775p-mdss: " Dmitry Baryshkov
2025-10-13 10:48 ` [PATCH v2 3/3] arm64: dts: qcom: lemans: Add edp reference clock for edp phy Ritesh Kumar
2025-10-13 12:35 ` Dmitry Baryshkov
2025-10-28 10:17 ` Ritesh Kumar
2025-10-13 12:34 ` [PATCH v2 0/3] Add edp reference clock for lemans Dmitry Baryshkov
2025-10-15 9:19 ` Ritesh Kumar [this message]
2025-10-19 12:14 ` Dmitry Baryshkov
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=4bd619e7-e9ca-44a8-9d36-10c18d7a8157@quicinc.com \
--to=quic_riteshk@quicinc.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=abhinav.kumar@linux.dev \
--cc=airlied@gmail.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=cros-qcom-dts-watchers@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=jessica.zhang@oss.qualcomm.com \
--cc=kishon@kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=lumag@kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mani@kernel.org \
--cc=marijn.suijten@somainline.org \
--cc=martin.petersen@oracle.com \
--cc=mripard@kernel.org \
--cc=quic_mahap@quicinc.com \
--cc=quic_vproddut@quicinc.com \
--cc=robh@kernel.org \
--cc=robin.clark@oss.qualcomm.com \
--cc=sean@poorly.run \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
--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
all inboxes | Powered by JetHome®