From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Vivek Yadav <vivek.2311@samsung.com>
Cc: rcsekar@samsung.com, krzysztof.kozlowski+dt@linaro.org,
wg@grandegger.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, pankaj.dubey@samsung.com,
ravi.patel@samsung.com, alim.akhtar@samsung.com,
linux-fsd@tesla.com, robh+dt@kernel.org,
linux-can@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, devicetree@vger.kernel.org,
aswani.reddy@samsung.com, sriranjani.p@samsung.com
Subject: Re: [Patch v4 1/2] can: m_can: Call the RAM init directly from m_can_chip_config
Date: Thu, 8 Dec 2022 10:12:11 +0100 [thread overview]
Message-ID: <20221208091211.622jm5raebedxboa@pengutronix.de> (raw)
In-Reply-To: <20221207100632.96200-2-vivek.2311@samsung.com>
[-- Attachment #1: Type: text/plain, Size: 786 bytes --]
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@pengutronix.de>
> Signed-off-by: Vivek Yadav <vivek.2311@samsung.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 |
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-12-08 9:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20221207100642epcas5p26c8f3f898ad8ac434092c702a788c0ff@epcas5p2.samsung.com>
2022-12-07 10:06 ` [Patch v4 0/2] can: mcan: Add MCAN support for FSD SoC Vivek Yadav
[not found] ` <CGME20221207100650epcas5p408d280e0e2d2d6acfb5e252e37f504b2@epcas5p4.samsung.com>
2022-12-07 10:06 ` [Patch v4 1/2] can: m_can: Call the RAM init directly from m_can_chip_config Vivek Yadav
2022-12-08 9:12 ` Marc Kleine-Budde [this message]
[not found] ` <CGME20221207100700epcas5p408c436aaaf0edd215b54f36f500cd02c@epcas5p4.samsung.com>
2022-12-07 10:06 ` [Patch v4 2/2] arm64: dts: fsd: Add MCAN device node Vivek Yadav
2022-12-07 11:10 ` Krzysztof Kozlowski
2022-12-07 11:11 ` (subset) " Krzysztof Kozlowski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221208091211.622jm5raebedxboa@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=alim.akhtar@samsung.com \
--cc=aswani.reddy@samsung.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-fsd@tesla.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pankaj.dubey@samsung.com \
--cc=ravi.patel@samsung.com \
--cc=rcsekar@samsung.com \
--cc=robh+dt@kernel.org \
--cc=sriranjani.p@samsung.com \
--cc=vivek.2311@samsung.com \
--cc=wg@grandegger.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).