From: petter@ka-long.de
To: linux-can@vger.kernel.org
Cc: mkl@pengutronix.de
Subject: Re: MCP2518FD : Failed to detect MCP2518FD (osc=0x00000000)
Date: Mon, 31 Jan 2022 10:35:54 +0100 (CET) [thread overview]
Message-ID: <20220131093554.505C65B0025F@dd15738.kasserver.com> (raw)
In-Reply-To: <20220131084205.53otmukeyt2dt4zj@pengutronix.de>
Hi Marc,
I have disabled DMAs in imx7s.dtsi for all ecspis and recompile the device tree.
Still get the same failure.
Thanks
Niels
ecspi2: spi@30830000 {
#address-cells = <1>;
#size-cells = <0>;
compatible = "fsl,imx7d-ecspi", "fsl,imx51-ecspi";
reg = <0x30830000 0x10000>;
interrupts = <GIC_SPI 32 IRQ_TYPE_LEVEL_HIGH>;
clocks = <&clks IMX7D_ECSPI2_ROOT_CLK>,
<&clks IMX7D_ECSPI2_ROOT_CLK>;
clock-names = "ipg", "per";
/*
dmas = <&sdma 2 7 1>, <&sdma 3 7 2>;
dma-names = "rx", "tx";
*/
status = "disabled";
};
Marc Kleine-Budde schrieb am 31.01.2022 08:42 (GMT +00:00):
> On 31.01.2022 09:33:04, petter@ka-long.de wrote:
>> I am working on an IMX7D board. Some time ago I have back-ported the
>> MCP2518FD driver to the official 5.4.70 NXP kernel and it works fine.
>>
>> I am struggleing to get the mcp driver working on the latest nxp
>> kernel 5.10.72.
>>
>> Same hardware.
>>
>> I did not find any unusal in the logs. pinctrl did not complain, spi
>> seems to initialize normal.
>>
>> The old kernel with the new (almost old one) device tree works. The
>> new kernel did not work with the old or new device tree.
>>
>> At the moment I am stuck. Could be anything. Must not be the driver
>> itself.
>
> Is SPI DMA enabled? Try disabling it.
>
> regards,
> 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 |
>
next prev parent reply other threads:[~2022-01-31 9:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-31 8:33 MCP2518FD : Failed to detect MCP2518FD (osc=0x00000000) petter
2022-01-31 8:42 ` Marc Kleine-Budde
2022-01-31 9:35 ` petter [this message]
2022-01-31 9:58 ` Marc Kleine-Budde
2022-01-31 12:44 ` petter
2022-01-31 13:09 ` Marc Kleine-Budde
2022-01-31 14:15 ` petter
2022-01-31 15:17 ` Marc Kleine-Budde
2022-02-01 9:08 ` petter
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=20220131093554.505C65B0025F@dd15738.kasserver.com \
--to=petter@ka-long.de \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
/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