From: Lucas Stach <l.stach@pengutronix.de> Date: 2020-08-11 08:16:02
0704c5743694 (can: m_can_platform: remove unnecessary m_can_class_resume()
call) removed the m_can_class_resume() call in the runtime resume path
to get rid of a infinite recursion, so the runtime resume now only handles
the device clocks. Unfortunately it did not remove the complementary
m_can_class_suspend() call in the runtime suspend function, so those paths
are now unbalanced, which causes the pinctrl state to get stuck on the
"sleep" state, which breaks all CAN functionality on SoCs where this state
is defined. Remove the m_can_class_suspend() call to fix this.
Fixes: 0704c5743694 (can: m_can_platform: remove unnecessary
m_can_class_resume() call)
Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
---
drivers/net/can/m_can/m_can_platform.c | 2 --
1 file changed, 2 deletions(-)
From: Lucas Stach <l.stach@pengutronix.de> Date: 2020-08-11 08:16:00
0704c5743694 (can: m_can_platform: remove unnecessary m_can_class_resume()
call) removed the m_can_class_resume() call in the runtime resume path
to get rid of a infinite recursion, so the runtime resume now only handles
the device clocks. Unfortunately it did not remove the complementary
m_can_class_suspend() call in the runtime suspend function, so those paths
are now unbalanced, which causes the pinctrl state to get stuck on the
"sleep" state, which breaks all CAN functionality on SoCs where this state
is defined. Remove the m_can_class_suspend() call to fix this.
Fixes: 0704c5743694 (can: m_can_platform: remove unnecessary
m_can_class_resume() call)
Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
---
drivers/net/can/m_can/m_can_platform.c | 2 --
1 file changed, 2 deletions(-)
From: Dan Murphy <hidden> Date: 2020-09-01 18:21:04
Lucase
On 8/11/20 3:15 AM, Lucas Stach wrote:
0704c5743694 (can: m_can_platform: remove unnecessary m_can_class_resume()
call) removed the m_can_class_resume() call in the runtime resume path
to get rid of a infinite recursion, so the runtime resume now only handles
the device clocks. Unfortunately it did not remove the complementary
m_can_class_suspend() call in the runtime suspend function, so those paths
are now unbalanced, which causes the pinctrl state to get stuck on the
"sleep" state, which breaks all CAN functionality on SoCs where this state
is defined. Remove the m_can_class_suspend() call to fix this.
Fixes: 0704c5743694 (can: m_can_platform: remove unnecessary
m_can_class_resume() call)
Not sure about this wrap around for the fixes in the commit msg.
Otherwise
Acked-by: Dan Murphy <redacted>