Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   Heiko Stuebner <heiko@sntech.de>
To:     Johan Jonker <jbx6244@gmail.com>
Cc:     Heiko Stuebner <heiko@sntech.de>,
        linux-arm-kernel@lists.infradead.org,
        krzysztof.kozlowski+dt@linaro.org, linux-kernel@vger.kernel.org,
        robh+dt@kernel.org, devicetree@vger.kernel.org,
        linux-rockchip@lists.infradead.org
Subject: Re: [PATCH v2] ARM: dts: rockchip: rk3xx: disable arm_global_timer
Date:   Tue, 15 Nov 2022 12:10:17 +0100
Message-Id: <166851058436.863884.13293855526499863813.b4-ty@sntech.de>
In-Reply-To: <f275ca8d-fd0a-26e5-b978-b7f3df815e0a@gmail.com>
References: <f275ca8d-fd0a-26e5-b978-b7f3df815e0a@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Sun, 30 Oct 2022 21:56:29 +0100, Johan Jonker wrote:
> The clock source and the sched_clock provided by the arm_global_timer
> on Rockchip rk3066a/rk3188 are quite unstable because their rates
> depend on the CPU frequency.
> 
> Recent changes to the arm_global_timer driver makes it impossible to use.
> 
> On the other side, the arm_global_timer has a higher rating than the
> ROCKCHIP_TIMER, it will be selected by default by the time framework
> while we want to use the stable Rockchip clock source.
> 
> [...]

Applied, thanks!

[1/1] ARM: dts: rockchip: rk3xx: disable arm_global_timer
      commit: da74858a475782a3f16470907814c8cc5950ad68

Best regards,
-- 
Heiko Stuebner <heiko@sntech.de>