Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756218AbdDGNVu (ORCPT ); Fri, 7 Apr 2017 09:21:50 -0400 Received: from mail-wr0-f170.google.com ([209.85.128.170]:33182 "EHLO mail-wr0-f170.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755935AbdDGNVm (ORCPT ); Fri, 7 Apr 2017 09:21:42 -0400 Date: Fri, 7 Apr 2017 15:21:38 +0200 From: Daniel Lezcano To: Nicolai Stange Cc: John Stultz , linux-kernel@vger.kernel.org, Thomas Gleixner Subject: Re: [PATCH] x86/numachip timer: set ->min_delta_ticks and ->max_delta_ticks Message-ID: <20170407132138.GG2078@mai> References: <20170326134403.16226-1-nicstange@gmail.com> <20170330200849.8417-1-nicstange@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20170330200849.8417-1-nicstange@gmail.com> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1123 Lines: 27 On Thu, Mar 30, 2017 at 10:08:49PM +0200, Nicolai Stange wrote: > In preparation for making the clockevents core NTP correction aware, > all clockevent device drivers must set ->min_delta_ticks and > ->max_delta_ticks rather than ->min_delta_ns and ->max_delta_ns: a > clockevent device's rate is going to change dynamically and thus, the > ratio of ns to ticks ceases to stay invariant. > > Make the numachip clockevent driver initialize these fields properly. > > This patch alone doesn't introduce any change in functionality as the > clockevents core still looks exclusively at the (untouched) ->min_delta_ns > and ->max_delta_ns. As soon as this has changed, a followup patch will > purge the initialization of ->min_delta_ns and ->max_delta_ns from this > driver. > > Signed-off-by: Nicolai Stange > --- Acked-by: Daniel Lezcano -- Linaro.org │ Open source software for ARM SoCs Follow Linaro: Facebook | Twitter | Blog