can: m_can_platform: don't call m_can_class_suspend in runtime suspend
authorLucas Stach <l.stach@pengutronix.de>
Tue, 11 Aug 2020 08:15:44 +0000 (10:15 +0200)
committerMarc Kleine-Budde <mkl@pengutronix.de>
Tue, 6 Oct 2020 21:29:30 +0000 (23:29 +0200)
commit81f1f5ae8b3cbd54fdd994c9e9aacdb7b414a802
tree649e819359837b0a99381bef60550662923ba689
parentd91dc434f2baa592e9793597421231174d57bbbf
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>
drivers/net/can/m_can/m_can_platform.c