From: Marc Kleine-Budde <mkl@pengutronix.de>
To: "ukrfoil.com, Cтудиопак Украина, Восточный регион" <ukrfoil@gmail.com>
Cc: "Schlüßler, Timo" <t.schluessler@krause.de>,
"Vincent MAILHOL" <mailhol.vincent@wanadoo.fr>,
linux-can <linux-can@vger.kernel.org>
Subject: Re: mcp251x hangs during ifup
Date: Wed, 3 Mar 2021 08:48:41 +0100 [thread overview]
Message-ID: <20210303074841.me5egjpecebrpxc4@pengutronix.de> (raw)
In-Reply-To: <CACGOs=TJhoV99D=V-7xa8LG6Ftx8SWUO_XCHGAP3L1_UGLVm3w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 6149 bytes --]
On 03.03.2021 09:44:54, ukrfoil.com, Cтудиопак Украина, Восточный регион wrote:
| root@nanopi-neo:~#cat /proc/interrupts
| CPU0 CPU1 CPU2 CPU3
| 25: 0 0 0 0 GICv2 50 Level timer@1c20c00
| 26: 0 0 0 0 GICv2 29 Level arch_timer
| 27: 1696369 3348041 3820461 82777 GICv2 30 Level arch_timer
| 30: 0 0 0 0 GICv2 82 Level 1c02000.dma-controller
| 32: 5404 0 0 0 GICv2 92 Level sunxi-mmc
| 34: 0 0 0 0 GICv2 103 Level musb-hdrc.2.auto
| 35: 0 0 0 0 GICv2 104 Level ehci_hcd:usb1
| 36: 0 0 0 0 GICv2 105 Level ohci_hcd:usb2
| 37: 0 0 0 0 GICv2 110 Level ehci_hcd:usb3
| 38: 0 0 0 0 GICv2 111 Level ohci_hcd:usb4
| 42: 9952 0 0 0 GICv2 114 Level eth0
| 43: 4 0 0 0 GICv2 97 Level sun6i-spi
| 46: 49 0 0 0 GICv2 32 Level ttyS0
| 47: 211302239 0 0 0 GICv2 38 Level mv64xxx_i2c
| 48: 18992623 0 0 0 GICv2 39 Level mv64xxx_i2c
| 49: 0 0 0 0 GICv2 72 Level 1f00000.rtc
| 63: 0 0 0 0 GICv2 152 Level arm-pmu
| 64: 0 0 0 0 GICv2 153 Level arm-pmu
| 65: 0 0 0 0 GICv2 154 Level arm-pmu
| 66: 0 0 0 0 GICv2 155 Level arm-pmu
| 111: 1 0 0 0 sunxi_pio_edge 44 Edge usb0-id-det
| IPI0: 0 0 0 0 CPU wakeup interrupts
| IPI1: 0 0 0 0 Timer broadcast interrupts
| IPI2: 47 88 79 82 Rescheduling interrupts
| IPI3: 304963 2353917 362091 1661 Function call interrupts
| IPI4: 0 0 0 0 CPU stop interrupts
| IPI5: 0 0 0 0 IRQ work interrupts
| IPI6: 0 0 0 0 completion interrupts
| Err: 0
[...]
| root@nanopi-neo:~#cat /proc/interrupts
| CPU0 CPU1 CPU2 CPU3
| 25: 0 0 0 0 GICv2 50 Level timer@1c20c00
| 26: 0 0 0 0 GICv2 29 Level arch_timer
| 27: 1711040 3437940 3850320 84900 GICv2 30 Level arch_timer
| 30: 0 0 0 0 GICv2 82 Level 1c02000.dma-controller
| 32: 5516 0 0 0 GICv2 92 Level sunxi-mmc
| 34: 0 0 0 0 GICv2 103 Level musb-hdrc.2.auto
| 35: 0 0 0 0 GICv2 104 Level ehci_hcd:usb1
| 36: 0 0 0 0 GICv2 105 Level ohci_hcd:usb2
| 37: 0 0 0 0 GICv2 110 Level ehci_hcd:usb3
| 38: 0 0 0 0 GICv2 111 Level ohci_hcd:usb4
| 42: 10190 0 0 0 GICv2 114 Level eth0
| 43: 18 0 0 0 GICv2 97 Level sun6i-spi
| 46: 49 0 0 0 GICv2 32 Level ttyS0
| 47: 214592622 0 0 0 GICv2 38 Level mv64xxx_i2c
| 48: 19314189 0 0 0 GICv2 39 Level mv64xxx_i2c
| 49: 0 0 0 0 GICv2 72 Level 1f00000.rtc
| 63: 0 0 0 0 GICv2 152 Level arm-pmu
| 64: 0 0 0 0 GICv2 153 Level arm-pmu
| 65: 0 0 0 0 GICv2 154 Level arm-pmu
| 66: 0 0 0 0 GICv2 155 Level arm-pmu
| 107: 1 0 0 0 sunxi_pio_edge 40 Edge spi0.0
| 111: 1 0 0 0 sunxi_pio_edge 44 Edge usb0-id-det
| IPI0: 0 0 0 0 CPU wakeup interrupts
| IPI1: 0 0 0 0 Timer broadcast interrupts
| IPI2: 48 88 85 83 Rescheduling interrupts
| IPI3: 305542 2828247 362982 1704 Function call interrupts
| IPI4: 0 0 0 0 CPU stop interrupts
| IPI5: 0 0 0 0 IRQ work interrupts
| IPI6: 0 0 0 0 completion interrupts
| Err: 0
That looks good, the IRQ is not shared. Can you test again with
IRQ_TYPE_EDGE_FALLING in the DT instead of IRQ_TYPE_LEVEL_LOW?
| can0: can@0 {
| reg = <0>;
| compatible = "microchip,mcp2515";
| pinctrl-names = "default";
| pinctrl-0 = <&can0_pin_irq>;
| interrupt-parent = <&pio>;
| interrupts = <6 8 IRQ_TYPE_EDGE_FALLING>;
You better use IRQ_TYPE_LEVEL_LOW instead of IRQ_TYPE_EDGE_FALLING, but
that's unrelated to this problem.
| clocks = <&can0_osc_fixed>;
| spi-max-frequency = <10000000>;
| gpio-controller;
| gpio-cells = <2>;
| status = "okay";
| };
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 |
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-03-04 0:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-01 16:58 mcp251x hangs during ifup Marc Kleine-Budde
2021-03-02 1:40 ` Vincent MAILHOL
2021-03-02 7:19 ` Marc Kleine-Budde
2021-03-02 8:28 ` Schlüßler, Timo
[not found] ` <CACGOs=TG4jyXKHBfPGDEJp1gSA+PyNVqCM7grPGMpe9+wYDBLA@mail.gmail.com>
2021-03-03 7:26 ` Marc Kleine-Budde
[not found] ` <CACGOs=TJhoV99D=V-7xa8LG6Ftx8SWUO_XCHGAP3L1_UGLVm3w@mail.gmail.com>
2021-03-03 7:48 ` Marc Kleine-Budde [this message]
[not found] ` <CACGOs=SOxiN1PKhZvhTizH92vneKUOfjxL+9fg4-=JmHHgYtNw@mail.gmail.com>
2021-03-03 8:08 ` Marc Kleine-Budde
[not found] ` <CACGOs=SSEvb=5AG9a7dSpOuiaq-wX+FLe3NAMEtKcMFdwJx8Pw@mail.gmail.com>
2021-03-03 8:33 ` Marc Kleine-Budde
2021-03-03 9:40 ` Schlüßler, Timo
[not found] ` <CACGOs=Ry7DtLooobKzuK7PWLOaWVnawMNTkErKC8e4OJKjNJPQ@mail.gmail.com>
2021-03-03 21:19 ` Marc Kleine-Budde
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=20210303074841.me5egjpecebrpxc4@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=linux-can@vger.kernel.org \
--cc=mailhol.vincent@wanadoo.fr \
--cc=t.schluessler@krause.de \
--cc=ukrfoil@gmail.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