From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-10.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_CR_TRAILER, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id DFFD4C433E6 for ; Mon, 11 Jan 2021 10:13:33 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 91B44222B6 for ; Mon, 11 Jan 2021 10:13:33 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728977AbhAKKNd (ORCPT ); Mon, 11 Jan 2021 05:13:33 -0500 Received: from Galois.linutronix.de ([193.142.43.55]:37678 "EHLO galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728862AbhAKKNc (ORCPT ); Mon, 11 Jan 2021 05:13:32 -0500 From: Thomas Gleixner DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020; t=1610359970; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=ELTMBG/piRAicwVwlOp7eFBbH/3LfbXixUnmMHwZ0aU=; b=HZ46lrmNU50/Ja+TXetTWLzIGyNL3iCTC+111NZ66zJcLdRR+VvPrdeicua+9JryMz/xHF vVCyry0uZFyq/sen8wJbQFwNyz8FNfaRdkmbYc00YI0L8O/VmPWMCnGjIsw2jLJLoQSgLe fcGuKEW9ooraOxoGoADUILWsp6u7ccqDGV4FxhBurS7scQJQhVLWZXpNruScnSK021gAOx EGFCbyEPYKIr6TFuNOcZAw07STaKNrDXgiob747cvPznPEGmb+faHkceFyirf58Pz4bmoD Qoi6cNxy+XSwFmcGI8cF7WIvlbq9k7CiZisiqLTSR5OmEyur7ftE3v6EdHRmww== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020e; t=1610359970; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=ELTMBG/piRAicwVwlOp7eFBbH/3LfbXixUnmMHwZ0aU=; b=36FA3kIrpGPfrJHjkJusvwimGZcvZLrNY8NvUZvKJGO8tl2GxvJBc8x9sjJWa8AT60h7mP 2mFYFVj+1kv4iUCg== To: Geert Uytterhoeven Cc: LKML , Alexandre Belloni , Jason Gunthorpe , Miroslav Lichvar , John Stultz , Prarit Bhargava , Alessandro Zummo , linux-rtc@vger.kernel.org, Peter Zijlstra , Wolfram Sang , Linux-Renesas Subject: Re: [patch 5/8] ntp: Make the RTC synchronization more reliable In-Reply-To: References: <20201206214613.444124194@linutronix.de> <20201206220542.062910520@linutronix.de> Date: Mon, 11 Jan 2021 11:12:49 +0100 Message-ID: <87lfcz7pem.fsf@nanos.tec.linutronix.de> MIME-Version: 1.0 Content-Type: text/plain Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Dec 29 2020 at 20:41, Geert Uytterhoeven wrote: > Hi Thomas, >> Reported-by: Miroslav Lichvar >> Signed-off-by: Thomas Gleixner > > Thanks for your patch, which is now commit c9e6189fb03123a7 ("ntp: Make > the RTC synchronization more reliable"). > > Since this commit, the I2C RTC on the R-Car M2-W Koelsch development > board is accessed every two seconds. Sticking a WARN() in the I2C > activation path gives e.g. Huch? Every two seconds? The timer is armed with 11 * 60 * NSEC_PER_SEC, which is 11 minutes. Confused.... Thanks, tglx