summaryrefslogtreecommitdiff
path: root/scripts/include
diff options
context:
space:
mode:
authorMeghana Malladi <m-malladi@ti.com>2024-12-23 20:45:50 +0530
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2025-01-09 13:33:42 +0100
commit4ac8e8bf70b436294534d06e5d500e950e20c13d (patch)
tree4a1c3ea77ce869912b06634bae00fec4bae791a2 /scripts/include
parent771ab379e87d881b4f487faf36059de9c6385548 (diff)
downloadlinux-4ac8e8bf70b436294534d06e5d500e950e20c13d.tar.gz
linux-4ac8e8bf70b436294534d06e5d500e950e20c13d.tar.bz2
linux-4ac8e8bf70b436294534d06e5d500e950e20c13d.zip
net: ti: icssg-prueth: Fix clearing of IEP_CMP_CFG registers during iep_init
[ Upstream commit 9b115361248dc6cce182a2dc030c1c70b0a9639e ] When ICSSG interfaces are brought down and brought up again, the pru cores are shut down and booted again, flushing out all the memories and start again in a clean state. Hence it is expected that the IEP_CMP_CFG register needs to be flushed during iep_init() to ensure that the existing residual configuration doesn't cause any unusual behavior. If the register is not cleared, existing IEP_CMP_CFG set for CMP1 will result in SYNC0_OUT signal based on the SYNC_OUT register values. After bringing the interface up, calling PPS enable doesn't work as the driver believes PPS is already enabled, (iep->pps_enabled is not cleared during interface bring down) and driver will just return true even though there is no signal. Fix this by disabling pps and perout. Fixes: c1e0230eeaab ("net: ti: icss-iep: Add IEP driver") Signed-off-by: Meghana Malladi <m-malladi@ti.com> Reviewed-by: Roger Quadros <rogerq@kernel.org> Signed-off-by: David S. Miller <davem@davemloft.net> Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'scripts/include')
0 files changed, 0 insertions, 0 deletions