Received: by 2002:a05:6358:3188:b0:123:57c1:9b43 with SMTP id q8csp22542093rwd; Fri, 30 Jun 2023 09:14:37 -0700 (PDT) X-Google-Smtp-Source: APBJJlEIl2m7oXwWXZ2iwC9jM0/yYnvMQXvt/LxMaZeUcD4Wf6cpigMxOnpXchdw1+wDbm+kqust X-Received: by 2002:a17:902:b682:b0:1b8:10aa:d2fa with SMTP id c2-20020a170902b68200b001b810aad2famr1909119pls.48.1688141677125; Fri, 30 Jun 2023 09:14:37 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1688141677; cv=none; d=google.com; s=arc-20160816; b=ynLHKfC6j4xYrooRlU8gSbAUPdW6WC+vKiz1mcdVD1oBf6X2f29A9YD+tKeKKL8Lpr Q4mEFDnwMhIw0iGIVIsBG6xqVt0DkFrYU5EGC8NQloFwbcJUrSLfbxGvcJkBFJB8b7ST 5W0Gw0Rm4kAjx3wd/FMt7YslvNFWKAHv+2ducfpfsh7sJKwlz0fAwR2c5gSu514bDmT4 7yFi0CmVoahWQKHaerJepUp6IZuWgMK9/Crt+JRESAJr4gsYWBx0Xod7cNRIWnDT+D9A Zone78Wawvot1sYiCPIyZoxjWtHEZdWl+fxl009aQSaTQ2WErmIh+R9avm+fpdzy/T+B PVvg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from:dkim-signature; bh=mb3ZyytePmgU5kXtBpOaRC5ZBHhiy7A4A4l54PC6cxA=; fh=0/guCqG4ShANjkiFjdZfzHEGB4TQr4v57gGIDaVPXlk=; b=WPjL+Qg5p/+4KCTcL3B3u7ptur6E9LlZ/tp7NA+pzKNiLrGgxRcmUUEmBjQ9UU2clz 33WNTdVmd4SN6n6Qbc4ZOOtVQg+ZIkdblRpxxtLTbxbr7Nl4Jcru/2mnfEUJKHcoR6mA n5j8ljVKJhuozcU3Fhnvl9eyEUx5KwYhTqxXW8181f8ZKuKvz67Dn1xxuRZze8eVksoD AgQpxT+6aBX1BG68q+uZ8Mt6KBYoF6KO2HGAg2n8H5Zal2f0sYksqDiRF5zpJ7kXCRhc Lt48WfLbTtd8kZQ4dnNPs/WLmWhrNUrv3DWY6P9ZtMh2fJp368tJoMYh7EmFKdY4hcA+ AcYg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@smile-fr.20221208.gappssmtp.com header.s=20221208 header.b=mbzR+eTI; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id d7-20020a170902cec700b001b392bf919bsi13405140plg.407.2023.06.30.09.14.21; Fri, 30 Jun 2023 09:14:36 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@smile-fr.20221208.gappssmtp.com header.s=20221208 header.b=mbzR+eTI; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232701AbjF3PmT (ORCPT + 99 others); Fri, 30 Jun 2023 11:42:19 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:53996 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232200AbjF3PmS (ORCPT ); Fri, 30 Jun 2023 11:42:18 -0400 Received: from mail-wm1-x330.google.com (mail-wm1-x330.google.com [IPv6:2a00:1450:4864:20::330]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 0773E1B1 for ; Fri, 30 Jun 2023 08:42:16 -0700 (PDT) Received: by mail-wm1-x330.google.com with SMTP id 5b1f17b1804b1-3fa94ea1caaso18391175e9.1 for ; Fri, 30 Jun 2023 08:42:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=smile-fr.20221208.gappssmtp.com; s=20221208; t=1688139734; x=1690731734; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:from:to:cc:subject:date:message-id:reply-to; bh=mb3ZyytePmgU5kXtBpOaRC5ZBHhiy7A4A4l54PC6cxA=; b=mbzR+eTISbWi7Y5Tsf5ak7r4fJt1OPPu7ahtEdhOEJP6KyhnEi+PItlXGZSzDui7Xl lwndVSYLHmk1WL4+s6KCnd5mvzjWuXFspaBo3GK5Vo8Ekm/qUsbxsICnkhdUX058NpNl fVusEGlk9xmWFQWn8LWnT0uJGV//uUXMKWdiKf/8MOggluQArEUuvGLA3EjMmg08qkpJ KjD/pB0llsOA7XbEtGY0RCitaWdW4i4HWjfXW/g1hFeB5GDxGk4EBumoB+k7MJ/OaOJl cQyF14RHuGBBdbbRwvzVwsJoVwVo1Nc6h30zAQyn2bJQ4hxWAGXaynNR7LG2/dpNE4Bk rfKg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1688139734; x=1690731734; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=mb3ZyytePmgU5kXtBpOaRC5ZBHhiy7A4A4l54PC6cxA=; b=OZWunOFgtO7R8tYXP3rAd3nrjEFtp5EcZyG1m5oe7ZMdVNtWAOaVZoKutoQYU+b43k BI3SIvGO1AVxsj7KKh2GbQ73Ue9VHlBcuwqU6ZcZIHHiz0vQpUajKwysWKOzc2+//H2F VYIVNtyd8T3R1TkLCJh6r37bQWq8JPEWvLhksFLAXTE9JJFOB6MejTZc3OkjQTZKCxBm 94tglYU+6FbtCOsu/47YGc5ANXBiWd0uLTltQNZiQ1RnTNniVp3uaxZLcC0dBWWrdHyC u3O5X84tkOEpVS6srYbo6baRD28cTx3GN+YSBBDL66fFYslW0qY8l63Kp7w0nVJ1wjSr f0pA== X-Gm-Message-State: AC+VfDyWCVfrxT3dNpRdspbn3X9JCoE2UOEqP2sYeGQGJXIos5ixOtqU vdLrIhk8GXEXA311qlR0OuEFIPovIMqmrOUHDK9D1A== X-Received: by 2002:a05:600c:3d9b:b0:3fb:c257:9f48 with SMTP id bi27-20020a05600c3d9b00b003fbc2579f48mr3220754wmb.16.1688139734419; Fri, 30 Jun 2023 08:42:14 -0700 (PDT) Received: from P-ASN-ECS-830T8C3.numericable.fr ([89.159.1.53]) by smtp.gmail.com with ESMTPSA id g14-20020a7bc4ce000000b003fbaf9abf2fsm7690279wmk.23.2023.06.30.08.42.13 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 30 Jun 2023 08:42:13 -0700 (PDT) From: Yoann Congal To: Jesse Brandeburg , Tony Nguyen , "David S. Miller" , Eric Dumazet , Jakub Kicinski , Paolo Abeni , Richard Cochran Cc: Yoann Congal , intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org Subject: [PATCH RFC] igb: Use TAI clock to reset PHC value Date: Fri, 30 Jun 2023 17:41:38 +0200 Message-Id: <20230630154138.4041809-1-yoann.congal@smile.fr> X-Mailer: git-send-email 2.30.2 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS, T_SCC_BODY_TEXT_LINE autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org The PHC is usually synchronised in TAI (from PTP). By resetting it with the kernel TAI clock we avoid having to correct the PHC from REALTIME (usually UTC) to TAI (37s as of today). RFC: While this patch looks trivial and it does make linuxptp/ptp4l complain about a driver bug: timed out while polling for tx timestamp increasing tx_timestamp_timeout may correct this issue, but it is likely caused by a driver bug port 1: send peer delay response failed Increasing tx_timestamp_timeout to 1s does nothing different so I guess the driver does indeed freeze with this change but I can't figure out why... Do you have any idea/pointers? Thanks! Signed-off-by: Yoann Congal --- drivers/net/ethernet/intel/igb/igb_ptp.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/net/ethernet/intel/igb/igb_ptp.c b/drivers/net/ethernet/intel/igb/igb_ptp.c index 15e57460e19ea..65e5de2ccb279 100644 --- a/drivers/net/ethernet/intel/igb/igb_ptp.c +++ b/drivers/net/ethernet/intel/igb/igb_ptp.c @@ -1526,12 +1526,12 @@ void igb_ptp_reset(struct igb_adapter *adapter) /* Re-initialize the timer. */ if ((hw->mac.type == e1000_i210) || (hw->mac.type == e1000_i211)) { - struct timespec64 ts = ktime_to_timespec64(ktime_get_real()); + struct timespec64 ts = ktime_to_timespec64(ktime_get_clocktai()); igb_ptp_write_i210(adapter, &ts); } else { timecounter_init(&adapter->tc, &adapter->cc, - ktime_to_ns(ktime_get_real())); + ktime_to_ns(ktime_get_clocktai())); } out: spin_unlock_irqrestore(&adapter->tmreg_lock, flags); -- 2.30.2