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 9D2F8C001B0 for ; Wed, 26 Jul 2023 15:34:18 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233413AbjGZPeR (ORCPT ); Wed, 26 Jul 2023 11:34:17 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:42528 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229939AbjGZPeP (ORCPT ); Wed, 26 Jul 2023 11:34:15 -0400 Received: from mail-pf1-x42c.google.com (mail-pf1-x42c.google.com [IPv6:2607:f8b0:4864:20::42c]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id C72B8B5; Wed, 26 Jul 2023 08:34:14 -0700 (PDT) Received: by mail-pf1-x42c.google.com with SMTP id d2e1a72fcca58-6864c144897so1561073b3a.1; Wed, 26 Jul 2023 08:34:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1690385654; x=1690990454; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=PWbwYwSV7iiV6v9eT8C4182R5bKMpB+kkZZ7eQ6vX84=; b=O9NuTZlCFyepHw+5xc11xK0qyBnILVl1oSHaNXjEcYMPOpFk2SIywI6Hc94q7dB/i4 k7BDk0dCPgAkXd748xfFiko2FtThKPgfVB8p7ufDi0GCfjRLfa9iCE6SmkuY2MBNUQyX /koVe2eClI7gEGcJrhFUeImHiZDDrj4eHk2o9I0Fg9GSvol/jp/JnOklLns+J4Tnmk9n hraaPzk8JBASi0E/52rKC9dAgzj8sjJwrY34kwu08FczCzb/MjND23mq2aFh3R8K4meF p4wTjN9QMqZjRVvVHItwJMXNWCjIZJEp4c5N+ELlPtiEC7Mwq3IUOSQjP0XGjJS+JE2O w8Kg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1690385654; x=1690990454; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=PWbwYwSV7iiV6v9eT8C4182R5bKMpB+kkZZ7eQ6vX84=; b=LuT4z6LV7brMr5ajcXvfzhIiy3LiSP6IWnvQ3yB/bzQm8UoLxDzz1OSeYgBkDRilMF UvstNeouNSQSlNz3YARPYMCkxaAOpZtEVcK1w0FfmDJclei50HVCEzusReMPdLkcYDH5 JPo+mKetWJ6/kchNdg8d/f0Lx9X3wdLLtSQi5uz/invh4e6XfQRiSNro+DF1QgUXMCYd Wm20Vh8BUctZL0w5QuParZxmkzWYaVkZyf1+eKVlKJjuvGKN04IqDk3wD8APY4uRpSwv IfSXbySY9NyRpYl2/cbjzxQh+ajXtfogWoJpYboe8f5jAkfEpQOTX9F3rdkLWAtN1eYC IWgw== X-Gm-Message-State: ABy/qLYpca6IbO91reWKj6PDWxRO9DaHefKqYw57/0gsNDGhJEpCveex caxJt/rajD74QhkTQnK7LGI= X-Google-Smtp-Source: APBJJlGSV4nZT1u6Y+/+kpLnfP8AtBGmz13jE940isfGl8JKoJTH8WT3igY56rfoJorcXH1FFrBmWA== X-Received: by 2002:a17:903:2441:b0:1b8:95fc:cfe with SMTP id l1-20020a170903244100b001b895fc0cfemr3017435pls.3.1690385654076; Wed, 26 Jul 2023 08:34:14 -0700 (PDT) Received: from hoboy.vegasvil.org ([2601:640:8000:54:e2d5:5eff:fea5:802f]) by smtp.gmail.com with ESMTPSA id jw11-20020a170903278b00b001b89d9a58e9sm5963541plb.132.2023.07.26.08.34.12 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 26 Jul 2023 08:34:13 -0700 (PDT) Date: Wed, 26 Jul 2023 08:34:10 -0700 From: Richard Cochran To: Marc Kleine-Budde Cc: Jakub Kicinski , Johannes Zink , linux-kernel@vger.kernel.org, kernel@pengutronix.de, netdev@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com, Alexandre Torgue , Russell King , kernel test robot , Eric Dumazet , Jose Abreu , Maxime Coquelin , Giuseppe Cavallaro , Paolo Abeni , "David S. Miller" , linux-arm-kernel@lists.infradead.org, patchwork-jzi@pengutronix.de Subject: Re: [PATCH v2] net: stmmac: correct MAC propagation delay Message-ID: References: <20230719-stmmac_correct_mac_delay-v2-1-3366f38ee9a6@pengutronix.de> <20230725200606.5264b59c@kernel.org> <20230726-dreamboat-cornhusk-1bd71d19d0d4-mkl@pengutronix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20230726-dreamboat-cornhusk-1bd71d19d0d4-mkl@pengutronix.de> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jul 26, 2023 at 08:04:37AM +0200, Marc Kleine-Budde wrote: > At least the datasheet of the IP core tells to read the MAC delay from > the IP core (1), add the PHY delay (2) and the clock domain crossing > delay (3) and write it to the time stamp correction register. That is great, until they change the data sheet. Really, this happens. Thanks, Richard