From: Vladimir Oltean <vladimir.oltean@nxp.com>
To: Horatiu Vultur <horatiu.vultur@microchip.com>
Cc: andrew@lunn.ch, hkallweit1@gmail.com, linux@armlinux.org.uk,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, richardcochran@gmail.com,
rmk+kernel@armlinux.org.uk, rosenp@gmail.com,
christophe.jaillet@wanadoo.fr, viro@zeniv.linux.org.uk,
quentin.schulz@bootlin.com, atenart@kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v4] phy: mscc: Fix timestamping for vsc8584
Date: Tue, 19 Aug 2025 11:27:46 +0300 [thread overview]
Message-ID: <20250819082746.m3ergnluhr2wqr2p@skbuf> (raw)
In-Reply-To: <20250818081029.1300780-1-horatiu.vultur@microchip.com>
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@microchip.com>
Reviewed-by: Vladimir Oltean <vladimir.oltean@nxp.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
next prev parent reply other threads:[~2025-08-19 8:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-18 8:10 [PATCH net v4] phy: mscc: Fix timestamping for vsc8584 Horatiu Vultur
2025-08-18 11:09 ` Vadim Fedorenko
2025-08-18 13:21 ` Vladimir Oltean
2025-08-18 13:53 ` Vadim Fedorenko
2025-08-18 14:01 ` Vladimir Oltean
2025-08-18 13:56 ` Horatiu Vultur
2025-08-18 14:13 ` Vladimir Oltean
2025-08-18 14:19 ` Horatiu Vultur
2025-08-18 14:37 ` Vladimir Oltean
2025-08-19 6:40 ` Horatiu Vultur
2025-08-19 8:25 ` Vladimir Oltean
2025-08-19 8:27 ` Vladimir Oltean [this message]
2025-08-20 3:11 ` patchwork-bot+netdevbpf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250819082746.m3ergnluhr2wqr2p@skbuf \
--to=vladimir.oltean@nxp.com \
--cc=andrew@lunn.ch \
--cc=atenart@kernel.org \
--cc=christophe.jaillet@wanadoo.fr \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=horatiu.vultur@microchip.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=quentin.schulz@bootlin.com \
--cc=richardcochran@gmail.com \
--cc=rmk+kernel@armlinux.org.uk \
--cc=rosenp@gmail.com \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox