On 15/06/2019 18:29, Christian Lamparter wrote:
> From: Abhishek Sahu <absahu@xxxxxxxxxxxxxx>
>
>
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@xxxxxxxxxxxxxx>
> Signed-off-by: Pavel Kubelun <be.dissent@xxxxxxxxx>
> Signed-off-by: Christian Lamparter <chunkeey@xxxxxxxxx>
> ---
>
> 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 {
>
