From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>
Cc: linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/2] clk: qcom: gcc-msm8996: Fix CLKREF parenting
Date: Mon, 6 Jan 2020 00:05:44 -0800 [thread overview]
Message-ID: <20200106080546.3192125-1-bjorn.andersson@linaro.org> (raw)
We've always seen intermittent resets of msm8996 during boot, seemingly related
to PCIe somehow. The likely cause of these errors are the fact that the CLKREF
of all PHYs are parented by LN_BB, which while being on during boot is disabled
by the UFS host driver if it fails to find its PHY.
As such, depending on the timeing (and success) of the UFS initialization, PCIe
might loose its clocking.
These two patches ensures that LN_BB, connected to the CXO2 pad on the SoC, is
described as parent for all the CLKREF clocks. So that they all vote for this
clock appropriately.
Bjorn Andersson (2):
clk: qcom: gcc-msm8996: Fix parent for CLKREF clocks
arm64: dts: qcom: msm8996: Define parent clocks for gcc
.../devicetree/bindings/clock/qcom,gcc.yaml | 10 ++++++
arch/arm64/boot/dts/qcom/msm8996.dtsi | 3 ++
drivers/clk/qcom/gcc-msm8996.c | 35 +++++++++++++++----
3 files changed, 41 insertions(+), 7 deletions(-)
--
2.24.0
next reply other threads:[~2020-01-06 8:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-06 8:05 Bjorn Andersson [this message]
2020-01-06 8:05 ` [PATCH v2 1/2] clk: qcom: gcc-msm8996: Fix parent for CLKREF clocks Bjorn Andersson
2020-01-06 16:55 ` Stephen Boyd
2020-01-06 8:05 ` [PATCH v2 2/2] arm64: dts: qcom: msm8996: Define parent clocks for gcc Bjorn Andersson
2020-03-06 4:37 ` Vinod Koul
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=20200106080546.3192125-1-bjorn.andersson@linaro.org \
--to=bjorn.andersson@linaro.org \
--cc=agross@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@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).