[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240329150116.67da2b07@kernel.org>
Date: Fri, 29 Mar 2024 15:01:16 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Chintan Vankar <c-vankar@...com>
Cc: Dan Carpenter <dan.carpenter@...aro.org>, Siddharth Vadapalli
<s-vadapalli@...com>, Grygorii Strashko <grygorii.strashko@...com>, "Heiner
Kallweit" <hkallweit1@...il.com>, Vladimir Oltean
<vladimir.oltean@....com>, Andrew Lunn <andrew@...n.ch>, Roger Quadros
<rogerq@...nel.org>, Richard Cochran <richardcochran@...il.com>, Paolo
Abeni <pabeni@...hat.com>, Eric Dumazet <edumazet@...gle.com>, "David S.
Miller" <davem@...emloft.net>, <linux-kernel@...r.kernel.org>,
<netdev@...r.kernel.org>
Subject: Re: [PATCH net-next v4 1/3] net: ethernet: ti: am65-cpts: Enable
PTP RX HW timestamp using CPTS FIFO
On Wed, 27 Mar 2024 11:12:32 +0530 Chintan Vankar wrote:
> CPTS module supports capturing timestamp for every packet it receives,
> add a new function named "am65_cpts_find_rx_ts()" to get the timestamp
> of received packets from CPTS FIFO.
>
> Add another function named "am65_cpts_rx_timestamp()" which internally
> calls "am65_cpts_find_rx_ts()" function and timestamps the received
> PTP packets.
Maybe i'm unusually tied today but reading this patch without reading
the next one makes no sense. I mean, you say:
CPTS module supports capturing timestamp for every packet it
receives...
How is that relevant here.
When you post v5 please make sure to include a cover letter, explaining
the overall goal and impact of the series.
> + list_del_init(&event->list);
> + list_add(&event->list, &cpts->pool);
list_move() ?
--
pw-bot: cr
Powered by blists - more mailing lists