From: Ansuel Smith <ansuelsmth@gmail.com>
To: Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: Ansuel Smith <ansuelsmth@gmail.com>
Subject: [PATCH v2 0/2] PXO fixes for ipq8064 dtsi
Date: Sat, 30 Apr 2022 07:51:16 +0200 [thread overview]
Message-ID: <20220430055118.1947-1-ansuelsmth@gmail.com> (raw)
This small series is a fix for a long lasting error present in ipq8064
dtsi. At times the kpss-gcc driver was defined in the dts with
<&gcc PXO_SRC> a pxo clock. While PXO_SRC exist in the includes, the gcc
driver never expose it and if a driver try to actually use it the result
is a kernel panic even before any log is init.
To prepare for correct conversion of the different krait drivers to
parent data and to reflect what is defined in the Documentation with
actual driver and dts implementation, fix this error by using the now
defined pxo_board fixed clock.
v2:
- Swap patch 1 with patch 2 (fixes first changes second)
- Add fixes tag
Ansuel Smith (2):
ARM: dts: qcom: replace gcc PXO with pxo_board fixed clock
ARM: dts: qcom: add syscon and cxo/pxo clock to gcc node for ipq8064
arch/arm/boot/dts/qcom-ipq8064.dtsi | 10 ++++++----
1 file changed, 6 insertions(+), 4 deletions(-)
--
2.34.1
next reply other threads:[~2022-04-30 12:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-30 5:51 Ansuel Smith [this message]
2022-04-30 5:51 ` [PATCH v2 1/2] ARM: dts: qcom: replace gcc PXO with pxo_board fixed clock Ansuel Smith
2022-04-30 13:25 ` Dmitry Baryshkov
2022-04-30 5:51 ` [PATCH v2 2/2] ARM: dts: qcom: add syscon and cxo/pxo clock to gcc node for ipq8064 Ansuel Smith
2022-04-30 13:26 ` Dmitry Baryshkov
2022-07-03 3:55 ` [PATCH v2 0/2] PXO fixes for ipq8064 dtsi Bjorn Andersson
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=20220430055118.1947-1-ansuelsmth@gmail.com \
--to=ansuelsmth@gmail.com \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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).