Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp1003213ybl; Wed, 21 Aug 2019 08:40:22 -0700 (PDT) X-Google-Smtp-Source: APXvYqz9MKJg3UIHDEOpfXOp6zyuVYW35m9cRqZim4IoxTg92DzVB/TgU+q7khpI3MfFl4od93Jz X-Received: by 2002:a65:64cf:: with SMTP id t15mr29141954pgv.88.1566402021914; Wed, 21 Aug 2019 08:40:21 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1566402021; cv=none; d=google.com; s=arc-20160816; b=HrwX3yCHwiEx5/tFCoV2i1Rr+FRDCH6r11dT78CbZZBVSjFMhS+q3SUowREa+NR0iB guKM77lNIBbbR50eJlQgUzxNRhdJ69C7sUZ4JZIT/9271Mp0p/AquVkSxDtA6wtOQlW7 jbiZkbRZ/QnjCkXJEkF3pJ082dUoDT2855WPajG8YH4tI9EqLL+6QBtT61TbiQnmx4EL rnZH7xzTWNJgOMR8euHUcSTwulcQfBoTpInImo5z4yNYQEiYTC/wWOUhKIIvvsKkQSMC OeDl0P7s2K3v345jdnzB85Fdo7KdcgRSbdIXG0uuh0PN86Hok4VxSdVKnfusgr4NVQra mGvw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=hofOP5PR+MTmbmzcLo7PFMdD3aq/G1/hbKveUSW+b9o=; b=OxSgC+7WkTJQiyeR/aSvaFeyYo7RXcEvvWsJHmK32mwWTdAbtRy9u7LMeLMLW2Kyx9 VSmoXJ/+u+h4QkreWzW7DIY4u/F3CxntriWGdXgkflJvs0cpon0r1PaP3vnNlvXiqBFe ClNJJfK7kvc7hBTB/VTOmwXJhs6J4YHA6GChV2u4RIPwYPfHSZPfdIXcwDbv6xeGgUC/ zY1m0OkOpwvL8Y0yRf/fYW6/tuBe1s+kAd+djxEEMV+JbzfrS9lJ2Sin9HgDX6upHCo6 HhLYzqZL0jLLt/Qei9xLhc+ATEHG1/dismCk8cnJRyErUvLTbbzs0TdC7xQyOlw1UID4 XEiA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id h14si215718pjt.78.2019.08.21.08.40.05; Wed, 21 Aug 2019 08:40:21 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728289AbfHUO6k (ORCPT + 99 others); Wed, 21 Aug 2019 10:58:40 -0400 Received: from relay12.mail.gandi.net ([217.70.178.232]:35211 "EHLO relay12.mail.gandi.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726530AbfHUO6k (ORCPT ); Wed, 21 Aug 2019 10:58:40 -0400 Received: from localhost (aclermont-ferrand-651-1-259-53.w86-207.abo.wanadoo.fr [86.207.98.53]) (Authenticated sender: alexandre.belloni@bootlin.com) by relay12.mail.gandi.net (Postfix) with ESMTPSA id EB227200005; Wed, 21 Aug 2019 14:58:37 +0000 (UTC) Date: Wed, 21 Aug 2019 16:58:37 +0200 From: Alexandre Belloni To: Sebastian Andrzej Siewior Cc: Alexander Dahl , linux-rt-users@vger.kernel.org, Thomas Gleixner , LKML , Steven Rostedt Subject: Re: [ANNOUNCE] v5.2.9-rt3 Message-ID: <20190821145837.GD27031@piout.net> References: <20190816153616.fbridfzjkmfg4dnr@linutronix.de> <2182739.9IRgZpf3R8@ada> <20190820154418.GM3545@piout.net> <20190821132553.gjvya5lu6j2dfyo5@linutronix.de> <20190821142110.GC27031@piout.net> <20190821144230.knlyrnxz62d75hcb@linutronix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190821144230.knlyrnxz62d75hcb@linutronix.de> User-Agent: Mutt/1.12.1 (2019-06-15) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 21/08/2019 16:42:30+0200, Sebastian Andrzej Siewior wrote: > On 2019-08-21 16:21:10 [+0200], Alexandre Belloni wrote: > > I'm not sure it is worth it as the issue is introduced by > > clocksource-tclib-allow-higher-clockrates.patch. Shouldn't we fix it > > directly? > > you want to get rid of CONFIG_ATMEL_TCB_CLKSRC_USE_SLOW_CLOCK and use > the highest possible frequency by default? > No, I meant the issue fixed by clocksource-tclib-add-proper-depend.patch is introduced by clocksource-tclib-allow-higher-clockrates.patch so I would think fixing clocksource-tclib-allow-higher-clockrates.patch is preferable than having a separate patch. But maybe you meant you wanted a patch to fix clocksource-tclib-allow-higher-clockrates.patch Hopefully, one day we will have a solution for that upstream (i.e. being able to configure the clocksource and clockevent resolutions). -- Alexandre Belloni, Bootlin Embedded Linux and Kernel engineering https://bootlin.com