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 7940EC7EE39 for ; Thu, 2 Mar 2023 21:56:05 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229590AbjCBVUR (ORCPT ); Thu, 2 Mar 2023 16:20:17 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:40486 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229518AbjCBVUQ (ORCPT ); Thu, 2 Mar 2023 16:20:16 -0500 Received: from mail-pg1-x52a.google.com (mail-pg1-x52a.google.com [IPv6:2607:f8b0:4864:20::52a]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 7DEDF57D0D for ; Thu, 2 Mar 2023 13:19:42 -0800 (PST) Received: by mail-pg1-x52a.google.com with SMTP id z10so281994pgr.8 for ; Thu, 02 Mar 2023 13:19:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1677791982; 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=J6VnOrULyvJrjoGxWJKUjdKLKs4X5svGtSfEry7FNhw=; b=HcGuyDXU5NerL9dd0DzFRq6Ultbd/0vk3Sc14TM81ASWrFPI9TAG/UUvlYBQ5Q0VP4 ktT27wEcps9bEPjl72ykHBgScSTk9QtVHbC6kZGXf8YWmNOk66vql1FjdZmQ21Z4bJ/0 4WXu7iLDr38eVoMags3fKwPR5rDIfGWy4vS74YHqucvZeFmcR9U/j+PfsFDHBlm2XOnG JN2APV/xK5LMO2r32rw0MZ8dlb0yCrmvBP2ulIz/fAvObm+BDebxvTxQUryiorfYxBxV auFAkp/p/OqKH0FUkB7alCNwyRADMgm9NXAr+UrDq9RNXhSJoy6ef28Gn3hn9tykwpqQ MugQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1677791982; 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=J6VnOrULyvJrjoGxWJKUjdKLKs4X5svGtSfEry7FNhw=; b=tv6tF9GkvN4Bap8paGMwIEr30CYXWpSZLsQeYIRoteun9AzpZIBcBHxHbhFylaMI3P F0XW0ityB309Cr5Amo+uCcFf1TzLab1dAqqKB5X6BgoN107dm/+Y4rTjBidEzcnBivXD AvSo2Y3+HcdekVNO+SzXh66KkKldvR9f8ev4PDz1N2dkSYzlvoZq0rvl8U97HBe5D37x tKh7CSbs3Zw9E48dLFLFtnEpaYFXhlP++I4SPwh5NFCW/Ri16f5KcT6QPcH7u3vwtCSt 3x2kj0JL5geC4PTGn8y7TilsO1I4s23v6coENBihVh1pTVM+dtUxmUcK2ykCTuX4j90f AZ5A== X-Gm-Message-State: AO0yUKVrUODpMTbz0Mx/9B7S/M42TUXwyNzWITHNXRa81omWogQTGrRK dYBj318dtVyhTDXZwRTGIX+PuWmtGdw= X-Google-Smtp-Source: AK7set/IVTkv3+0FAR3NCfiGkPiQLu5/W9dUDKGPZfc3AM+p4d2HgOtSeWTCjMcA4ANZrxNcb1y8IA== X-Received: by 2002:a05:6a00:1da7:b0:5e4:f141:568b with SMTP id z39-20020a056a001da700b005e4f141568bmr10375656pfw.3.1677791981786; Thu, 02 Mar 2023 13:19:41 -0800 (PST) Received: from hoboy.vegasvil.org ([2601:640:8200:33:e2d5:5eff:fea5:802f]) by smtp.gmail.com with ESMTPSA id h16-20020aa786d0000000b005921c46cbadsm139683pfo.99.2023.03.02.13.19.40 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 02 Mar 2023 13:19:41 -0800 (PST) Date: Thu, 2 Mar 2023 13:19:38 -0800 From: Richard Cochran To: "Russell King (Oracle)" Cc: =?iso-8859-1?Q?K=F6ry?= Maincent , Jakub Kicinski , andrew@lunn.ch, davem@davemloft.net, f.fainelli@gmail.com, hkallweit1@gmail.com, netdev@vger.kernel.org, Thomas Petazzoni , Maxime Chevallier Subject: Re: [PATCH RFC net-next] net: phy: add Marvell PHY PTP support [multicast/DSA issues] Message-ID: References: <20230228141630.64d5ef63@kmaincent-XPS-13-7390> <20230228142648.408f26c4@kernel.org> <20230228145911.2df60a9f@kernel.org> <20230301170408.0cc0519d@kmaincent-XPS-13-7390> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org On Thu, Mar 02, 2023 at 11:49:26AM +0000, Russell King (Oracle) wrote: > Therefore, I believe that the Marvell PHY PTP implementation is all > round inferior to that found in the Marvell PP2 MAC, and hence why I > believe that the PP2 MAC implementation should be used by default over > the PHY. Yeah, that phy sure sounds like a lemon. > (In essence, because of all the noise when trying the Marvell PHY with > ptp4l, I came to the conlusion that NTP was a far better solution to > time synchronisation between machines than PTP would ever be due to > the nose induced by MDIO access. However, I should also state that I > basically gave up with PTP in the end because hardware support is > overall poor, and NTP just works - and I'd still have to run NTP for > the machines that have no PTP capabilities. PTP probably only makes > sense if one has a nice expensive grand master PTP clock on ones > network, and all the machines one wants to synchronise have decent > PTP implementations.) Yes, NTP is really what most people need, and with PTP you really must carefully select the hardware. There is lots of PTP junk on the market. Thanks, Richard