Received-SPF: pass (google.com: domain of linux-kernel+bounces-43718-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.48.161 as permitted sender) client-ip=147.75.48.161;
From: Vinicius Costa Gomes <vinicius.gomes@intel.com>
To: Sai Krishna Gajula <saikrishnag@marvell.com>, "richardcochran@gmail.com"
 <richardcochran@gmail.com>, "davem@davemloft.net" <davem@davemloft.net>,
 "kuba@kernel.org" <kuba@kernel.org>, "netdev@vger.kernel.org"
 <netdev@vger.kernel.org>, "linux-kernel@vger.kernel.org"
 <linux-kernel@vger.kernel.org>, Sunil Kovvuri
 Goutham <sgoutham@marvell.com>, Geethasowjanya Akula <gakula@marvell.com>,
 Linu Cherian <lcherian@marvell.com>, Hariprasad Kelam
 <hkelam@marvell.com>, Subbaraya Sundeep Bhatta <sbhatta@marvell.com>
Cc: Naveen Mamindlapalli <naveenm@marvell.com>
Subject: Re: [net-next PATCH] octeontx2: Add PTP clock driver for Octeon PTM
 clock.
In-Reply-To: <BY3PR18MB4707BB7ADFB58EC7032FBAF7A07E2@BY3PR18MB4707.namprd18.prod.outlook.com>
References: <20240124064156.2577119-1-saikrishnag@marvell.com>
 <87h6j154yx.fsf@intel.com>
 <BY3PR18MB4707BB7ADFB58EC7032FBAF7A07E2@BY3PR18MB4707.namprd18.prod.outlook.com>
Date: Mon, 29 Jan 2024 17:31:12 -0800
Message-ID: <87jznrr4in.fsf@intel.com>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain

Sai Krishna Gajula <saikrishnag@marvell.com> writes:

>> -----Original Message-----
>> From: Vinicius Costa Gomes <vinicius.gomes@intel.com>
>> Sent: Friday, January 26, 2024 5:41 AM
>> To: Sai Krishna Gajula <saikrishnag@marvell.com>;
>> richardcochran@gmail.com; davem@davemloft.net; kuba@kernel.org;
>> netdev@vger.kernel.org; linux-kernel@vger.kernel.org; Sunil Kovvuri
>> Goutham <sgoutham@marvell.com>; Geethasowjanya Akula
>> <gakula@marvell.com>; Linu Cherian <lcherian@marvell.com>; Hariprasad
>> Kelam <hkelam@marvell.com>; Subbaraya Sundeep Bhatta
>> <sbhatta@marvell.com>
>> Cc: Sai Krishna Gajula <saikrishnag@marvell.com>; Naveen Mamindlapalli
>> <naveenm@marvell.com>
>> Subject: Re: [net-next PATCH] octeontx2: Add PTP clock driver for
>> Octeon PTM clock.
>> 
>> Sai Krishna <saikrishnag@marvell.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@marvell.com>
>> > Signed-off-by: Naveen Mamindlapalli <naveenm@marvell.com>
>> > Signed-off-by: Sunil Kovvuri Goutham <sgoutham@marvell.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?
>
> This driver runs on endpoint device and not on the host.
> getcrosststamp() needs ART time, frequency details in case of x86 host
> system. Our use case is to sync the host's PTP/PTM time to the
> endpoint device via PTM interface.

Ah! I see. This is for "the other side", cool :-)


Cheers,
-- 
Vinicius