From: petter@ka-long.de
To: linux-can@vger.kernel.org
Cc: mkl@pengutronix.de
Subject: MCP2518FD : Failed to detect MCP2518FD (osc=0x00000000)
Date: Mon, 31 Jan 2022 09:33:04 +0100 (CET) [thread overview]
Message-ID: <20220131083304.122C45B0007E@dd15738.kasserver.com> (raw)
Hi Folks,
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.
BR
Niels
mcp2518fd_clk: mcp2818fd_clk {
compatible = "fixed-clock";
#clock-cells = <0>;
clock-frequency = <40000000>;
};
&ecspi2 {
pinctrl-names = "default";
pinctrl-0 = <&pinctrl_ecspi2>;
status = "okay";
fsl,spi-num-chipselects = <2>;
cs-gpios = <&gpio5 1 0>, <&gpio1 3 0>;
mcp2518fd@0 {
compatible = "microchip,mcp2518fd";
reg = <0>;
interrupts-extended = <&gpio3 0 IRQ_TYPE_LEVEL_LOW>;
spi-max-frequency = <20000000>;
clocks = <&mcp2518fd_clk>;
};
mcp2518fd@1 {
compatible = "microchip,mcp2518fd";
reg = <1>;
interrupts-extended = <&gpio4 23 IRQ_TYPE_LEVEL_LOW>;
spi-max-frequency = <20000000>;
clocks = <&mcp2518fd_clk>;
};
};
next reply other threads:[~2022-01-31 8:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-31 8:33 petter [this message]
2022-01-31 8:42 ` MCP2518FD : Failed to detect MCP2518FD (osc=0x00000000) Marc Kleine-Budde
2022-01-31 9:35 ` petter
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=20220131083304.122C45B0007E@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