From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751141AbbEYSsF (ORCPT ); Mon, 25 May 2015 14:48:05 -0400 Received: from www.linutronix.de ([62.245.132.108]:49665 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750903AbbEYSsD (ORCPT ); Mon, 25 May 2015 14:48:03 -0400 Date: Mon, 25 May 2015 20:48:06 +0200 (CEST) From: Thomas Gleixner To: Alexandre Belloni cc: Daniel Lezcano , Nicolas Ferre , Boris Brezillon , Maxime Ripard , sylvain.rochet@finsecur.com, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] clockevents: don't suspend/resume if unused In-Reply-To: <1421399151-26800-1-git-send-email-alexandre.belloni@free-electrons.com> Message-ID: References: <1421399151-26800-1-git-send-email-alexandre.belloni@free-electrons.com> User-Agent: Alpine 2.11 (DEB 23 2013-08-11) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Linutronix-Spam-Score: -1.0 X-Linutronix-Spam-Level: - X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required, ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 16 Jan 2015, Alexandre Belloni wrote: > There is no point in calling suspend/resume for unused > clockevents as they are already stopped and disabled. > > Furthermore, it can take some time to wait for some IPs to stop counting. While I agree with the patch itself, I really can't understand that last sentence. If stuff is stopped and disabled, what takes time to stop counting? Thanks, tglx