From: Bjorn Andersson <andersson@kernel.org>
To: Vinod Koul <vkoul@kernel.org>,
Kishon Vijay Abraham I <kishon@kernel.org>,
Neil Armstrong <neil.armstrong@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: linux-arm-msm@vger.kernel.org, linux-phy@lists.infradead.org,
linux-kernel@vger.kernel.org,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
devicetree@vger.kernel.org
Subject: Re: (subset) [PATCH v3 0/5] phy: qcom: qmp-pcie: drop second clock-output-names entry
Date: Fri, 21 Jun 2024 01:11:17 -0500 [thread overview]
Message-ID: <171895028797.12506.8337547267879269845.b4-ty@kernel.org> (raw)
In-Reply-To: <20240614-fix-pcie-phy-compat-v3-0-730d1811acf4@linaro.org>
On Fri, 14 Jun 2024 13:18:23 +0300, Dmitry Baryshkov wrote:
> While testing the linux-next on SM8450-HDK I noticed that one of the
> PCIe hosts stays in the deferred state, because the corresponding PHY
> isn't probed. A quick debug pointed out that while the patches that
> added support for the PIPE AUX clock to the PHY driver have landed,
> corresponding DT changes were not picked up for 6.10. Restore the
> compatibility with the existing DT files by dropping the second entry in
> the clock-output-names array and always generating the corresponding
> name on the fly.
>
> [...]
Applied, thanks!
[3/5] arm64: dts: qcom: sm8450: drop second clock name from clock-output-names
commit: 831f66d3423c22457ec1d686e565e152b10fbd91
[4/5] arm64: dts: qcom: sm8550: drop second clock name from clock-output-names
commit: 84ea430eb0719ebe4c423bdc9c92e0f94a46a47e
[5/5] arm64: dts: qcom: sm8650: drop second clock name from clock-output-names
commit: dc323623c3b87c48c99fe8dbbd1962f0129d3da9
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2024-06-21 6:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-14 10:18 Dmitry Baryshkov
2024-06-14 10:18 ` [PATCH v3 1/5] phy: qcom: qmp-pcie: restore compatibility with existing DTs Dmitry Baryshkov
2024-06-14 10:18 ` [PATCH v3 2/5] dt-bindings: phy: qcom,sc8280xp-qmp-pcie-phy: drop second output clock name Dmitry Baryshkov
2024-06-14 10:18 ` [PATCH v3 3/5] arm64: dts: qcom: sm8450: drop second clock name from clock-output-names Dmitry Baryshkov
2024-06-14 11:54 ` Neil Armstrong
2024-06-14 10:18 ` [PATCH v3 4/5] arm64: dts: qcom: sm8550: " Dmitry Baryshkov
2024-06-14 11:55 ` Neil Armstrong
2024-06-14 10:18 ` [PATCH v3 5/5] arm64: dts: qcom: sm8650: " Dmitry Baryshkov
2024-06-14 11:55 ` Neil Armstrong
2024-06-15 18:52 ` [PATCH v3 0/5] phy: qcom: qmp-pcie: drop second clock-output-names entry Vinod Koul
2024-06-21 6:11 ` Bjorn Andersson [this message]
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=171895028797.12506.8337547267879269845.b4-ty@kernel.org \
--to=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=kishon@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=neil.armstrong@linaro.org \
--cc=robh@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
all inboxes | Powered by JetHome®