Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751881AbdDCGmj (ORCPT ); Mon, 3 Apr 2017 02:42:39 -0400 Received: from cassarossa.samfundet.no ([193.35.52.29]:59517 "EHLO cassarossa.samfundet.no" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751822AbdDCGmh (ORCPT ); Mon, 3 Apr 2017 02:42:37 -0400 Date: Mon, 3 Apr 2017 08:42:27 +0200 From: Hans-Christian Noren Egtvedt To: Nicolai Stange Cc: Haavard Skinnemoen , John Stultz , linux-kernel@vger.kernel.org, Thomas Gleixner Subject: Re: [PATCH] avr32/time: set ->min_delta_ticks and ->max_delta_ticks Message-ID: <20170403064227.GA27597@samfundet.no> References: <20170326134403.16226-1-nicstange@gmail.com> <20170330193933.6660-1-nicstange@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170330193933.6660-1-nicstange@gmail.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1004 Lines: 27 Around Thu 30 Mar 2017 21:39:33 +0200 or thereabout, 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 avr32 arch's 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 -1 Please do not spend time on AVR32 architecture. It will be removed in the next merge window. -- Best regards, Hans-Christian Noren Egtvedt