summaryrefslogtreecommitdiffstats
path: root/drivers/net/can/m_can/m_can_platform.c
diff options
context:
space:
mode:
authorVivek Yadav <vivek.2311@samsung.com>2022-12-07 15:36:31 +0530
committerMarc Kleine-Budde <mkl@pengutronix.de>2022-12-12 11:42:33 +0100
commiteaacfeaca7ad0804b9a6eff7afeba93a87db7638 (patch)
tree4b586d83bf6c18fcd1fded6393a72303e6e3f661 /drivers/net/can/m_can/m_can_platform.c
parentbd4a52bf9d56abaabc6926f68c3cc3528937a864 (diff)
downloadlinux-eaacfeaca7ad0804b9a6eff7afeba93a87db7638.tar.bz2
can: m_can: Call the RAM init directly from m_can_chip_config
When we try to access the mcan message ram addresses during the probe, hclk is gated by any other drivers or disabled, because of that probe gets failed. Move the mram init functionality to mcan chip config called by m_can_start from mcan open function, by that time clocks are enabled. Suggested-by: Marc Kleine-Budde <mkl@pengutronix.de> Signed-off-by: Vivek Yadav <vivek.2311@samsung.com> Link: https://lore.kernel.org/all/20221207100632.96200-2-vivek.2311@samsung.com Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
Diffstat (limited to 'drivers/net/can/m_can/m_can_platform.c')
-rw-r--r--drivers/net/can/m_can/m_can_platform.c4
1 files changed, 0 insertions, 4 deletions
diff --git a/drivers/net/can/m_can/m_can_platform.c b/drivers/net/can/m_can/m_can_platform.c
index b5a5bedb3116..9c1dcf838006 100644
--- a/drivers/net/can/m_can/m_can_platform.c
+++ b/drivers/net/can/m_can/m_can_platform.c
@@ -140,10 +140,6 @@ static int m_can_plat_probe(struct platform_device *pdev)
platform_set_drvdata(pdev, mcan_class);
- ret = m_can_init_ram(mcan_class);
- if (ret)
- goto probe_fail;
-
pm_runtime_enable(mcan_class->dev);
ret = m_can_class_register(mcan_class);
if (ret)