diff options
author | Lucas Stach <l.stach@pengutronix.de> | 2020-08-11 10:15:44 +0200 |
---|---|---|
committer | Marc Kleine-Budde <mkl@pengutronix.de> | 2020-10-06 23:29:30 +0200 |
commit | 81f1f5ae8b3cbd54fdd994c9e9aacdb7b414a802 (patch) | |
tree | 649e819359837b0a99381bef60550662923ba689 /net | |
parent | d91dc434f2baa592e9793597421231174d57bbbf (diff) |
can: m_can_platform: don't call m_can_class_suspend in runtime suspend
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>
Link: https://lore.kernel.org/r/20200811081545.19921-1-l.stach@pengutronix.de
Acked-by: Dan Murphy <dmurphy@ti.com>
Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
Diffstat (limited to 'net')
0 files changed, 0 insertions, 0 deletions