From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from vps0.lunn.ch (vps0.lunn.ch [156.67.10.101]) (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 A381961FCE; Tue, 26 Aug 2025 02:22:15 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=156.67.10.101 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1756174937; cv=none; b=SUg4TQeb3kQq8rJjdy4x2mY9B6fGy+2gGLWSi1t/bYAZOAouoah4samyQUfjQWHKZRkjQKQCozgbqtbMTsxrSoE/2LIEvPjVaTPD1u8ekNz/4MFfF3wqSJZD73BU3wqw233PqZWeBluD1eDVUVPxN67H2Hber5Nxl8gZAXk0o24= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1756174937; c=relaxed/simple; bh=tmT/tLAdcoowbyD+cIQdPgCED88KbN3cZAQcTx5kPnk=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=Ou2dj47YvIcR8l7LXC7FDQNMP7gBqyKOPxmRe3keZCWsdCplFf2itlb7yatrPMNhY0N/3L+DrUV4nW9AEQSnlCTTcm+5c2Rl64ml4njlPOs3wzJBrN31/kmy9u6XDp6orMaDWrUC9qAlTc/5ZavW1htcvTn4Yf8npuItAgIhuOo= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=lunn.ch; spf=pass smtp.mailfrom=lunn.ch; dkim=pass (1024-bit key) header.d=lunn.ch header.i=@lunn.ch header.b=lsFB/2yS; arc=none smtp.client-ip=156.67.10.101 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=lunn.ch Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=lunn.ch Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=lunn.ch header.i=@lunn.ch header.b="lsFB/2yS" DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lunn.ch; s=20171124; h=In-Reply-To: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=g3/SB8WVXUI9MW5KiqhvBEppVZwamrXCShDQl7NKXqU=; b=lsFB/2ySab8xzmslwml7+LxKRV GXfCIehZvf1IHYXp6XeSx6v2zDPbK/um552AljNY2OS07OgrmcHCQqnlDT7XPi4mEpBWTgGUdHDVD viorhoS5eYgoszCjltQ+XwCcSfZv0GeL1spHRo+rHx95NXrG247x0KQqyn0y04LyIzaM=; Received: from andrew by vps0.lunn.ch with local (Exim 4.94.2) (envelope-from ) id 1uqjJz-0061ZI-SP; Tue, 26 Aug 2025 04:22:03 +0200 Date: Tue, 26 Aug 2025 04:22:03 +0200 From: Andrew Lunn To: Wei Fang Cc: "robh@kernel.org" , "krzk+dt@kernel.org" , "conor+dt@kernel.org" , "richardcochran@gmail.com" , Claudiu Manoil , Vladimir Oltean , Clark Wang , "andrew+netdev@lunn.ch" , "davem@davemloft.net" , "edumazet@google.com" , "kuba@kernel.org" , "pabeni@redhat.com" , "vadim.fedorenko@linux.dev" , Frank Li , "shawnguo@kernel.org" , "s.hauer@pengutronix.de" , "festevam@gmail.com" , "F.S. Peng" , "devicetree@vger.kernel.org" , "netdev@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "imx@lists.linux.dev" , "kernel@pengutronix.de" Subject: Re: [PATCH v5 net-next 08/15] ptp: netc: add debugfs support to loop back pulse signal Message-ID: References: <20250825041532.1067315-1-wei.fang@nxp.com> <20250825041532.1067315-9-wei.fang@nxp.com> <13c4fe5a-878c-4a08-87df-f5bb96f0b589@lunn.ch> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: On Tue, Aug 26, 2025 at 01:50:06AM +0000, Wei Fang wrote: > > On Mon, Aug 25, 2025 at 12:15:25PM +0800, Wei Fang wrote: > > > The NETC Timer supports to loop back the output pulse signal of Fiper-n > > > into Trigger-n input, so that we can leverage this feature to validate > > > some other features without external hardware support. > > > > This seems like it should be a common feature which more PTP clocks > > will support? Did you search around and see if there are other devices > > with this? > > Actually, the NETC v4 Timer is the same IP used in the QorIQ platforms, > but it is a different version, and the ptp_qoriq driver is not compatible > with NETC v4 Timer, I have stated in the patch ("ptp: netc: add NETC V4 > Timer PTP driver support"). That does not answer my question. Does Marvell have this loopback concept? Intel? Freescale? Microchip? Is there anything which prevents other vendors implementing it? Andrew