[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250819082746.m3ergnluhr2wqr2p@skbuf>
Date: Tue, 19 Aug 2025 11:27:46 +0300
From: Vladimir Oltean <vladimir.oltean@....com>
To: Horatiu Vultur <horatiu.vultur@...rochip.com>
Cc: andrew@...n.ch, hkallweit1@...il.com, linux@...linux.org.uk,
davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org,
pabeni@...hat.com, richardcochran@...il.com,
rmk+kernel@...linux.org.uk, rosenp@...il.com,
christophe.jaillet@...adoo.fr, viro@...iv.linux.org.uk,
quentin.schulz@...tlin.com, atenart@...nel.org,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH net v4] phy: mscc: Fix timestamping for vsc8584
On Mon, Aug 18, 2025 at 10:10:29AM +0200, Horatiu Vultur wrote:
> There was a problem when we received frames and the frames were
> timestamped. The driver is configured to store the nanosecond part of
> the timestmap in the ptp reserved bits and it would take the second part
> by reading the LTC. The problem is that when reading the LTC we are in
> atomic context and to read the second part will go over mdio bus which
> might sleep, so we get an error.
> The fix consists in actually put all the frames in a queue and start the
> aux work and in that work to read the LTC and then calculate the full
> received time.
>
> Fixes: 7d272e63e0979d ("net: phy: mscc: timestamping and PHC support")
> Signed-off-by: Horatiu Vultur <horatiu.vultur@...rochip.com>
Reviewed-by: Vladimir Oltean <vladimir.oltean@....com>
I think the patch is in "Changes Requested" in patchwork because of me,
so I'll try this, see if it helps:
pw-bot: under-review
Powered by blists - more mailing lists