From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 8E75030F94; Mon, 16 Oct 2023 17:03:16 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="EH4nY8b7" Received: by smtp.kernel.org (Postfix) with ESMTPSA id D479DC433C7; Mon, 16 Oct 2023 17:03:14 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1697475796; bh=Vx73FpVlkBN9x5VuKdWHHh99ktLX7tsDFLYW1HUCKH4=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=EH4nY8b7LAH1scjlTuimouVGxGT5eSdosXd9Se89Zx5CvqrOAtDsHntyKHAkUkpWL oa35WUwna7wUxKwdIg/AEs3t2dKClNvhXKrst+SSqGUCE0iTtJaOMfQmOtW8lv9V24 VLNLgQagLyI+FwKISdE+NzYGMpS+VfTxGH5JHg3ohzagV9hEluwUtlsNXlsMqjY3Zd WzLhmkzP2A3RWj/ygqZIu82vGEv/P28vOmw8zVUA6n4EqZGc3s1fCZgxqB+ei/37Bt 5dNy+9+OSlw5dKS1OHCl/NutMIrnXlfsPQ+oXGFb46dXXHEpiZwwlw3U4vGTxmkCXx N10yao1Q8PJ8g== Date: Mon, 16 Oct 2023 10:03:13 -0700 From: Jakub Kicinski To: =?UTF-8?B?S8O2cnk=?= Maincent Cc: Andrew Lunn , Florian Fainelli , netdev@vger.kernel.org, linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org, Thomas Petazzoni , "David S . Miller" , Eric Dumazet , Paolo Abeni , Jonathan Corbet , Jay Vosburgh , Andy Gospodarek , Nicolas Ferre , Claudiu Beznea , Horatiu Vultur , UNGLinuxDriver@microchip.com, Broadcom internal kernel review list , Heiner Kallweit , Russell King , Richard Cochran , Radu Pirea , Willem de Bruijn , Vladimir Oltean , Michael Walle , Jacob Keller , Maxime Chevallier Subject: Re: [PATCH net-next v5 08/16] net: ethtool: Add a command to expose current time stamping layer Message-ID: <20231016100313.36d4eab9@kernel.org> In-Reply-To: <20231016182307.18c5dcf1@kmaincent-XPS-13-7390> References: <20231009155138.86458-1-kory.maincent@bootlin.com> <20231009155138.86458-9-kory.maincent@bootlin.com> <2fbde275-e60b-473d-8488-8f0aa637c294@broadcom.com> <20231010102343.3529e4a7@kmaincent-XPS-13-7390> <20231013090020.34e9f125@kernel.org> <6ef6418d-6e63-49bd-bcc1-cdc6eb0da2d5@lunn.ch> <20231016124134.6b271f07@kmaincent-XPS-13-7390> <20231016072204.1cb41eab@kernel.org> <20231016170027.42806cb7@kmaincent-XPS-13-7390> <20231016084346.10764b4a@kernel.org> <20231016182307.18c5dcf1@kmaincent-XPS-13-7390> Precedence: bulk X-Mailing-List: netdev@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Mon, 16 Oct 2023 18:23:07 +0200 K=C3=B6ry Maincent wrote: > > What's the reason for timestamp precision differences? > > My understanding so far was the the differences come from: > > 1. different stamping device (i.e. separate "piece of silicon", > > accessed over a different bus, with different PHC etc.) > > 2. different stamping point (MAC vs DMA) > >=20 > > I don't think any "integrated" device would support stamps which > > differ under category 1. =20 >=20 > It was a case reported by Maxime on v3: > https://lore.kernel.org/netdev/20230324112541.0b3dd38a@pc-7.home/=20 IMHO this talks about how clock control/disciplining works which is a somewhat independent topic of timestamping.