[net-next 05/16] net/mlx5: Release clock lock before scheduling a PPS work

[saeed]

From: Eran Ben Elisha <era...@mellanox.com>

Holding the clock lock is not required when scheduling a PPS work.

Signed-off-by: Eran Ben Elisha <era...@mellanox.com>
Reviewed-by: Moshe Shemesh <mo...@mellanox.com>
Signed-off-by: Saeed Mahameed <sae...@nvidia.com>
---
 drivers/net/ethernet/mellanox/mlx5/core/lib/clock.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/net/ethernet/mellanox/mlx5/core/lib/clock.c 
b/drivers/net/ethernet/mellanox/mlx5/core/lib/clock.c
index b62daf7b9a5c..f8465e42b238 100644
--- a/drivers/net/ethernet/mellanox/mlx5/core/lib/clock.c
+++ b/drivers/net/ethernet/mellanox/mlx5/core/lib/clock.c
@@ -581,8 +581,8 @@ static int mlx5_pps_event(struct notifier_block *nb,
                cycles_delta = div64_u64(nsec_delta << clock->cycles.shift,
                                         clock->cycles.mult);
                clock->pps_info.start[pin] = cycles_now + cycles_delta;
-               schedule_work(&clock->pps_info.out_work);
                write_sequnlock_irqrestore(&clock->lock, flags);
+               schedule_work(&clock->pps_info.out_work);
                break;
        default:
                mlx5_core_err(mdev, " Unhandled clock PPS event, func %d\n",
-- 
2.26.2