[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87h6j154yx.fsf@intel.com>
Date: Thu, 25 Jan 2024 16:11:02 -0800
From: Vinicius Costa Gomes <vinicius.gomes@...el.com>
To: Sai Krishna <saikrishnag@...vell.com>, richardcochran@...il.com,
davem@...emloft.net, kuba@...nel.org, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, sgoutham@...vell.com, gakula@...vell.com,
lcherian@...vell.com, hkelam@...vell.com, sbhatta@...vell.com
Cc: Sai Krishna <saikrishnag@...vell.com>, Naveen Mamindlapalli
<naveenm@...vell.com>
Subject: Re: [net-next PATCH] octeontx2: Add PTP clock driver for Octeon PTM
clock.
Sai Krishna <saikrishnag@...vell.com> writes:
> The PCIe PTM(Precision time measurement) protocol provides precise
> coordination of events across multiple components like PCIe host
> clock, PCIe EP PHC local clocks of PCIe devices. This patch adds
> support for ptp clock based PTM clock. We can use this PTP device
> to sync the PTM time with CLOCK_REALTIME or other PTP PHC
> devices using phc2sys.
>
> Signed-off-by: Sai Krishna <saikrishnag@...vell.com>
> Signed-off-by: Naveen Mamindlapalli <naveenm@...vell.com>
> Signed-off-by: Sunil Kovvuri Goutham <sgoutham@...vell.com>
> ---
I can see that the same device id (PCI_DEVID_OCTEONTX2_PTP) is used by a
ethernet driver.
That brings me a question: why expose a different PTP chardev? In other
words, why can't you just implement .getcrosststamp() for that ethernet
device?
Cheers,
--
Vinicius
Powered by blists - more mailing lists