From mboxrd@z Thu Jan 1 00:00:00 1970 From: Richard Cochran Subject: Re: [PATCH net-next 00/10] PTP support for DSA and mv88e6xxx driver. Date: Tue, 13 Feb 2018 19:59:40 -0800 Message-ID: <20180214035939.qlamdershe7ydllk@localhost> References: <1518566871-12213-1-git-send-email-andrew@lunn.ch> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: David Miller , netdev , Vivien Didelot , brandon.streiff@ni.com To: Andrew Lunn Return-path: Received: from mail-pf0-f176.google.com ([209.85.192.176]:42848 "EHLO mail-pf0-f176.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S966717AbeBND7o (ORCPT ); Tue, 13 Feb 2018 22:59:44 -0500 Received: by mail-pf0-f176.google.com with SMTP id b25so3411660pfd.9 for ; Tue, 13 Feb 2018 19:59:44 -0800 (PST) Content-Disposition: inline In-Reply-To: <1518566871-12213-1-git-send-email-andrew@lunn.ch> Sender: netdev-owner@vger.kernel.org List-ID: On Wed, Feb 14, 2018 at 01:07:41AM +0100, Andrew Lunn wrote: > Further work is requires to support bridges using Boundary Clock or > Transparent Clock mode. Small correction: Boundary Clock (BC) works just fine if the DSA ports are separate (not in a bridge device). If the DSA ports *are* connected together in a bridge device, the multicast PTP messages are incorrectly (?) forwarded out all ports by the kernel SW bridge code. The work around is to add a bridge rule to drop these frames. With the rule in place, BC also works in this configuration. Transparent Clock would work as far as the driver and kernel go, but ptp4l does not yet implement it. Thanks, Richard