> -----Original Message----- > From: Marc Kleine-Budde <mkl@xxxxxxxxxxxxxx> > Sent: 24 November 2022 04:12 > To: Vivek Yadav <vivek.2311@xxxxxxxxxxx> > Cc: rcsekar@xxxxxxxxxxx; krzysztof.kozlowski+dt@xxxxxxxxxx; > wg@xxxxxxxxxxxxxx; davem@xxxxxxxxxxxxx; edumazet@xxxxxxxxxx; > kuba@xxxxxxxxxx; pabeni@xxxxxxxxxx; pankaj.dubey@xxxxxxxxxxx; > ravi.patel@xxxxxxxxxxx; alim.akhtar@xxxxxxxxxxx; linux-fsd@xxxxxxxxx; > robh+dt@xxxxxxxxxx; linux-can@xxxxxxxxxxxxxxx; netdev@xxxxxxxxxxxxxxx; > linux-kernel@xxxxxxxxxxxxxxx; linux-arm-kernel@xxxxxxxxxxxxxxxxxxx; linux- > samsung-soc@xxxxxxxxxxxxxxx; devicetree@xxxxxxxxxxxxxxx; > aswani.reddy@xxxxxxxxxxx; sriranjani.p@xxxxxxxxxxx > 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()? > m_can_chip_config function is called from m_can open. Configuring RAM init every time we open the CAN instance is not needed, I think only once during the probe is enough. If message RAM init failed then fifo Transmit and receive will fail and there will be no communication. So there is no point to "open and Configure CAN chip". >From my understanding it's better to keep RAM init inside the probe and if there is a failure happened goes to CAN probe failure. > Marc Thanks for reviewing the patch. > > -- > Pengutronix e.K. | Marc Kleine-Budde | > Embedded Linux | > https://protect2.fireeye.com/v1/url?k=818c3690-e0f1dc13-818dbddf- > 74fe48600158-a08b6a4bfa0b043e&q=1&e=315ed8d1-1645-4c16-b5e7- > 2a250ae36941&u=https%3A%2F%2Fwww.pengutronix.de%2F | > Vertretung West/Dortmund | Phone: +49-231-2826-924 | > Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
