[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <13c4fe5a-878c-4a08-87df-f5bb96f0b589@lunn.ch>
Date: Mon, 25 Aug 2025 14:36:31 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Wei Fang <wei.fang@....com>
Cc: robh@...nel.org, krzk+dt@...nel.org, conor+dt@...nel.org,
richardcochran@...il.com, claudiu.manoil@....com,
vladimir.oltean@....com, xiaoning.wang@....com,
andrew+netdev@...n.ch, davem@...emloft.net, edumazet@...gle.com,
kuba@...nel.org, pabeni@...hat.com, vadim.fedorenko@...ux.dev,
Frank.Li@....com, shawnguo@...nel.org, s.hauer@...gutronix.de,
festevam@...il.com, fushi.peng@....com, devicetree@...r.kernel.org,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
imx@...ts.linux.dev, kernel@...gutronix.de
Subject: Re: [PATCH v5 net-next 08/15] ptp: netc: add debugfs support to loop
back pulse signal
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?
Ah:
ptp_qoriq_debugfs.c: if (!debugfs_create_file_unsafe("fiper1-loopback", 0600, root,
ptp_qoriq_debugfs.c: if (!debugfs_create_file_unsafe("fiper2-loopback", 0600, root,
Rather than hiding this in debugfs where each vendor will implement it
differently, i'm just think it might make sense to have an official
kernel API for it.
Andrew
Powered by blists - more mailing lists