From: Christian Lamparter <chunkeey@gmail.com>
To: linux-arm-msm@vger.kernel.org
Cc: David Brown <david.brown@linaro.org>,
Andy Gross <agross@kernel.org>,
Marc Gonzalez <marc.w.gonzalez@free.fr>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Pavel Kubelun <be.dissent@gmail.com>,
Sricharan R <sricharan@codeaurora.org>
Subject: [PATCH v3] ARM: dts: qcom: ipq4019: fix high resolution timer
Date: Thu, 20 Jun 2019 18:13:07 +0200 [thread overview]
Message-ID: <20190620161308.15936-1-chunkeey@gmail.com> (raw)
From: Abhishek Sahu <absahu@codeaurora.org>
The kernel is not switching the timer to the high resolution
mode and clock source keeps operating in with a just a lousy
10ms resolution.
The always-on property needs to be given for xo clock source
(which is the sole external oscillator) in the device tree
node to get to the 1ns high resolution mode.
Signed-off-by: Abhishek Sahu <absahu@codeaurora.org>
Signed-off-by: Pavel Kubelun <be.dissent@gmail.com>
Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
---
v3: fixed empty line, removed changeid reference and fluff,
reworded message.
v2: fixed subject [Abhishek Sahu is bouncing]
---
arch/arm/boot/dts/qcom-ipq4019.dtsi | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/boot/dts/qcom-ipq4019.dtsi b/arch/arm/boot/dts/qcom-ipq4019.dtsi
index bbcb7db810f7..0e3e79442c50 100644
--- a/arch/arm/boot/dts/qcom-ipq4019.dtsi
+++ b/arch/arm/boot/dts/qcom-ipq4019.dtsi
@@ -169,6 +169,7 @@
<1 4 0xf08>,
<1 1 0xf08>;
clock-frequency = <48000000>;
+ always-on;
};
soc {
--
2.20.1
next reply other threads:[~2019-06-20 16:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-20 16:13 Christian Lamparter [this message]
2019-06-24 12:09 ` [PATCH v3] ARM: dts: qcom: ipq4019: fix high resolution timer Sricharan R
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=20190620161308.15936-1-chunkeey@gmail.com \
--to=chunkeey@gmail.com \
--cc=agross@kernel.org \
--cc=be.dissent@gmail.com \
--cc=bjorn.andersson@linaro.org \
--cc=david.brown@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=marc.w.gonzalez@free.fr \
--cc=sricharan@codeaurora.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).