From: Marc Gonzalez <marc.w.gonzalez@free.fr>
To: Christian Lamparter <chunkeey@gmail.com>
Cc: Abhishek Sahu <absahu@codeaurora.org>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Pavel Kubelun <be.dissent@gmail.com>,
MSM <linux-arm-msm@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] ARM: dts: qcom: ipq4019: fix high resolution timer
Date: Tue, 18 Jun 2019 16:01:01 +0200 [thread overview]
Message-ID: <91de77a5-c823-3e90-989e-8459c91abed9@free.fr> (raw)
In-Reply-To: <20190615162918.29120-1-chunkeey@gmail.com>
On 15/06/2019 18:29, Christian Lamparter wrote:
> From: Abhishek Sahu <absahu@codeaurora.org>
>
>
Isn't there a spurious newline there?
> Cherry-picked from CAF QSDK repo with Change-Id
> I7c00b3c74d97c2a30ac9f05e18b511a0550fd459.
Do we really care about the downstream change-id?
Is this publicly available somewhere?
> Original commit message:
Not sure this introduction brings any info.
> The kernel is failing in switching the timer for high resolution
> mode and clock source operates in 10ms resolution. The always-on
> property needs to be given for timer device tree node to make
> clock source working in 1ns resolution.
>
> 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>
> ---
>
> 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 {
>
prev parent reply other threads:[~2019-06-18 14:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-15 16:29 Christian Lamparter
2019-06-18 14:01 ` Marc Gonzalez [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=91de77a5-c823-3e90-989e-8459c91abed9@free.fr \
--to=marc.w.gonzalez@free.fr \
--cc=absahu@codeaurora.org \
--cc=agross@kernel.org \
--cc=be.dissent@gmail.com \
--cc=bjorn.andersson@linaro.org \
--cc=chunkeey@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.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®