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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 2A8E4C433EF for ; Sat, 12 Mar 2022 20:04:49 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232559AbiCLUFq (ORCPT ); Sat, 12 Mar 2022 15:05:46 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:42316 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231804AbiCLUFp (ORCPT ); Sat, 12 Mar 2022 15:05:45 -0500 Received: from vps0.lunn.ch (vps0.lunn.ch [185.16.172.187]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 68C44532F1; Sat, 12 Mar 2022 12:04:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lunn.ch; s=20171124; h=In-Reply-To:Content-Transfer-Encoding:Content-Disposition: Content-Type:MIME-Version:References:Message-ID:Subject:Cc:To:From:Date:From: Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Content-Disposition: In-Reply-To:References; bh=rGqBRcNw4s56JzIh4WiyNNxrcGXW+DdMyOtuGHG9ozs=; b=Th q7cmAGUFE8nRztSu7eUZNV1O7EeMSsqNdrjI7WI0cQIeFuv1kPRsRUaRvYA/UY7L5Tt3Q0ZoidFMw XmV+pmrS23Qb/0J6GhIRUbv+cKaLmt2leNehEFa7JYwmSxqNoQzGBgLmhyce+dzrBbqVuKqPKjFlX ph1KD5vJHJVUG90=; Received: from andrew by vps0.lunn.ch with local (Exim 4.94.2) (envelope-from ) id 1nT7yZ-00AVKz-Qt; Sat, 12 Mar 2022 21:04:31 +0100 Date: Sat, 12 Mar 2022 21:04:31 +0100 From: Andrew Lunn To: Richard Cochran Cc: Woojung.Huh@microchip.com, linux@armlinux.org.uk, Horatiu.Vultur@microchip.com, Divya.Koppera@microchip.com, netdev@vger.kernel.org, hkallweit1@gmail.com, davem@davemloft.net, kuba@kernel.org, robh+dt@kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, UNGLinuxDriver@microchip.com, Madhuri.Sripada@microchip.com, Manohar.Puri@microchip.com Subject: Re: [PATCH net-next 2/3] dt-bindings: net: micrel: Configure latency values and timestamping check for LAN8814 phy Message-ID: References: <20220308154345.l4mk2oab4u5ydn5r@soft-dev3-1.localhost> <20220308221404.bwhujvsdp253t4g3@soft-dev3-1.localhost> <20220309132443.axyzcsc5kyb26su4@soft-dev3-1.localhost> <20220309195252.GB9663@hoboy.vegasvil.org> <20220312024828.GA15046@hoboy.vegasvil.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20220312024828.GA15046@hoboy.vegasvil.org> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > PTP4l(8) System Manager's Manual PTP4l(8) > > NAME > ptp4l - PTP Boundary/Ordinary/Transparent Clock > > ... > > egressLatency > Specifies the difference in nanoseconds between the actual > transmission time at the reference plane and the reported trans‐ > mit time stamp. This value will be added to egress time stamps > obtained from the hardware. The default is 0. > > ingressLatency > Specifies the difference in nanoseconds between the reported re‐ > ceive time stamp and the actual reception time at reference > plane. This value will be subtracted from ingress time stamps > obtained from the hardware. The default is 0. > Hi Richard Do these get passed to the kernel so the hardware can act on them, or are they used purely in userspace by ptp4l? If they has passed to the kernel, could we provide a getter as well as a setter, so the defaults hard coded in the driver can be read back? Andrew