public inbox for linux-can@vger.kernel.org
 help / color / mirror / Atom feed
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 09:08:25 +0100	[thread overview]
Message-ID: <20210303080825.lcpphr2ihvuugfl7@pengutronix.de> (raw)
In-Reply-To: <CACGOs=SOxiN1PKhZvhTizH92vneKUOfjxL+9fg4-=JmHHgYtNw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1316 bytes --]

On 03.03.2021 10:00:47, ukrfoil.com, Cтудиопак Украина, Восточный регион wrote:
> this with the IRQ_TYPE_EDGE_FALLING value

> > 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?

Doh! Need more coffee.

Of course I mean try with IRQ_TYPE_LEVEL_LOW and check if the unmodified
mcp2515 driver with disable_irq() does work then.

> >
> > | 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";
> > | };

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 --]

  parent reply	other threads:[~2021-03-04  0:24 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
     [not found]               ` <CACGOs=SOxiN1PKhZvhTizH92vneKUOfjxL+9fg4-=JmHHgYtNw@mail.gmail.com>
2021-03-03  8:08                 ` Marc Kleine-Budde [this message]
     [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=20210303080825.lcpphr2ihvuugfl7@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