From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Markus Mirevik <markus.mirevik@dpsolutions.se>
Cc: "linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Subject: Re: MCP251xFD runs interrupt handler twice per message.
Date: Mon, 17 Jan 2022 16:08:33 +0100 [thread overview]
Message-ID: <20220117150833.d4e4f4dhjvsvmxkt@pengutronix.de> (raw)
In-Reply-To: <HE1PR04MB310040456777CCDE2DF03FEAE6579@HE1PR04MB3100.eurprd04.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1244 bytes --]
On 17.01.2022 14:53:46, Markus Mirevik wrote:
> > That scope picture looks good! Can you include both runs of the IRQ
> > handler in one scope picture? I'm interested if there is activity or
> > a glich on IRQ line.
>
> Both are included. The last (number 7) is the one extra reading of the
> register!?
Doh! Indeed, you'r right, missed that.
> > After you've that picture, you can try to catch glitches on the IRQ
> > line. If your scope allows this, setup a trigger on the INT channel
> > that triggers if the channel is low for considerably less then it
> > takes to clear the IRQ.
> >
> > Currently it takes about 160µs to clear the IRQ, so setup a trigger
> > for less than 50µs.
>
> No glitches. The scope can trigger on glitch but no one is to be
> found.
Good.
It looks like this is not a problem of the mcp251xfd driver. I think now
it's time to ask an am335x expert. Maybe one of my coworker knows this
issue.
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:[~2022-01-17 15:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-14 11:05 MCP251xFD runs interrupt handler twice per message Markus Mirevik
2022-01-14 12:41 ` Marc Kleine-Budde
2022-01-14 13:43 ` Sv: " Markus Mirevik
2022-01-16 11:09 ` Marc Kleine-Budde
2022-01-17 11:55 ` Sv: " Markus Mirevik
2022-01-17 13:27 ` Marc Kleine-Budde
2022-01-17 14:53 ` Sv: " Markus Mirevik
2022-01-17 15:08 ` Marc Kleine-Budde [this message]
2022-01-17 15:56 ` Marc Kleine-Budde
2022-01-18 10:16 ` Marc Kleine-Budde
2022-01-18 10:22 ` Sv: " Markus Mirevik
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=20220117150833.d4e4f4dhjvsvmxkt@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=linux-can@vger.kernel.org \
--cc=markus.mirevik@dpsolutions.se \
/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