From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933668AbcHYPAX (ORCPT ); Thu, 25 Aug 2016 11:00:23 -0400 Received: from Galois.linutronix.de ([146.0.238.70]:34636 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758902AbcHYPAR (ORCPT ); Thu, 25 Aug 2016 11:00:17 -0400 Date: Thu, 25 Aug 2016 16:56:53 +0200 (CEST) From: Thomas Gleixner To: Nicolai Stange cc: John Stultz , linux-kernel@vger.kernel.org Subject: Re: [RFC v4 22/22] timekeeping: inform clockevents about freq adjustments In-Reply-To: <20160822233320.4548-23-nicstange@gmail.com> Message-ID: References: <20160822233320.4548-1-nicstange@gmail.com> <20160822233320.4548-23-nicstange@gmail.com> User-Agent: Alpine 2.20 (DEB 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 23 Aug 2016, Nicolai Stange wrote: > Upon adjustments of the monotonic clock's frequencies from the > timekeeping core, the clockevents devices' ->mult_adjusted should be > changed accordingly, too. > > Introduce clockevents_adjust_all_freqs() which traverses all registered > clockevent devices and recalculates their ->mult_adjusted based on the > monotonic clock's current frequency. I'm not sure whether adjusting all devices is a good idea. We have systems where the clockevent device is operated from a totally different crystal than the clocksource device which is used for timekeeping. At least we want an opt-out flag for this. Thanks, tglx