[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20221123224146.iic52cuhhnwqk2te@pengutronix.de>
Date: Wed, 23 Nov 2022 23:41:46 +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 v3 1/2] can: m_can: Move mram init to mcan device setup
On 22.11.2022 16:24:54, Vivek Yadav wrote:
> When we try to access the mcan message ram addresses, hclk is
> gated by any other drivers or disabled, because of that probe gets
> failed.
>
> Move the mram init functionality to mcan device setup called by
> mcan class register from mcan probe function, by that time clocks
> are enabled.
Why not call the RAM init directly from m_can_chip_config()?
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