[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20221208091211.622jm5raebedxboa@pengutronix.de>
Date: Thu, 8 Dec 2022 10:12:11 +0100
From: Marc Kleine-Budde <mkl@...gutronix.de>
To: Vivek Yadav <vivek.2311@...sung.com>
Cc: rcsekar@...sung.com, krzysztof.kozlowski+dt@...aro.org,
wg@...ndegger.com, davem@...emloft.net, edumazet@...gle.com,
kuba@...nel.org, pabeni@...hat.com, pankaj.dubey@...sung.com,
ravi.patel@...sung.com, alim.akhtar@...sung.com,
linux-fsd@...la.com, robh+dt@...nel.org, linux-can@...r.kernel.org,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
linux-samsung-soc@...r.kernel.org, devicetree@...r.kernel.org,
aswani.reddy@...sung.com, sriranjani.p@...sung.com
Subject: Re: [Patch v4 1/2] can: m_can: Call the RAM init directly from
m_can_chip_config
On 07.12.2022 15:36:31, Vivek Yadav wrote:
> 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@...gutronix.de>
> Signed-off-by: Vivek Yadav <vivek.2311@...sung.com>
Applied to linux-can-next.
Thanks,
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Embedded Linux | https://www.pengutronix.de |
Vertretung West/Dortmund | Phone: +49-231-2826-924 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists