diff options
| author | Vladimir Oltean <vladimir.oltean@nxp.com> | 2023-06-27 19:31:12 +0300 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2023-07-19 16:36:42 +0200 |
| commit | ad95418b5d8be248a5092a0b8c814736f52010f9 (patch) | |
| tree | ca0d86645493fd99f49a74de76a9e96205f4314e /include | |
| parent | ce77da4747f56ffffb25b35f040931d6139e929c (diff) | |
| download | linux-stable-ad95418b5d8be248a5092a0b8c814736f52010f9.tar.gz linux-stable-ad95418b5d8be248a5092a0b8c814736f52010f9.tar.bz2 linux-stable-ad95418b5d8be248a5092a0b8c814736f52010f9.zip | |
net: mscc: ocelot: don't report that RX timestamping is enabled by default
[ Upstream commit 4fd44b82b7aceaa35c2901c6546d2c4198e0799d ]
PTP RX timestamping should be enabled when the user requests it, not by
default. If it is enabled by default, it can be problematic when the
ocelot driver is a DSA master, and it sidesteps what DSA tries to avoid
through __dsa_master_hwtstamp_validate().
Additionally, after the change which made ocelot trap PTP packets only
to the CPU at ocelot_hwtstamp_set() time, it is no longer even true that
RX timestamping is enabled by default, because until ocelot_hwtstamp_set()
is called, the PTP traps are actually not set up. So the rx_filter field
of ocelot->hwtstamp_config reflects an incorrect reality.
Fixes: 96ca08c05838 ("net: mscc: ocelot: set up traps for PTP packets")
Fixes: 4e3b0468e6d7 ("net: mscc: PTP Hardware Clock (PHC) support")
Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>
Signed-off-by: Paolo Abeni <pabeni@redhat.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions