NET: mcan: Move runtime PM enable/disable to m_can_platform
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v2 Latest1 patch 2 repliesIn review
- v11 patch 4 repliesSuperseded
Patches in v2 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/1 | NET: mcan: Move runtime PM enable/disable to m_can_platformdrivers/ drivers/ | +8 | 2 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v2 yet.
Cover letter [PATCH v2 0/1] NET: mcan: Move runtime PM enable/disable to m_can_platform
Hi,This is a preparatory patch for modifying PM enabling due to PCI based M_CAN devices. As the functionality is right now, adding a PCI based M_CAN driver causes the core PCI functionality to call pm_runtime_enable() from pci_pm_init() when the PCI device is added. When the device is added, it is registered with m_can_class_register(), which ends up calling pm_runtime_enable() once more and causes the kernel to log an angry 'Unbalanced pm_runtime_enable!' message, as dev->power.disable_depth has gone down to zero.
To resolve this situation, I have added a patch that moves runtime PM enabling from m_can.c to the m_can_platform.c driver, which currently is the only driver that ends up enabling runtime PM.
Thanks,
Patrik
Patrik Flykt (1):
NET: mcan: Move runtime PM enable/disable to m_can_platform
drivers/net/can/m_can/m_can.c | 9 ++------- drivers/net/can/m_can/m_can_platform.c | 7 ++++++- 2 files changed, 8 insertions(+), 8 deletions(-)
Signature · 1 line
2.28.0