All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthias Klein <matthias.klein@optimeas.de>
To: wg@grandegger.com, mkl@pengutronix.de, linux-can@vger.kernel.org,
	support@karo-electronics.de
Cc: Sebastian Siewior <bigeasy@linutronix.de>
Subject: can: flexcan: problems with bus error reporting om i.MX53
Date: Fri, 25 Jul 2014 20:16:34 +0200	[thread overview]
Message-ID: <53D29F02.8010708@optimeas.de> (raw)

Hi all,

we had the following problems when we enabled bus error reporting on an 
i.MX537 (Ka-Ro TX53-8130):
- interrupt flooding when sending a packet on an open bus
- bus state change notifications did not work properly
- second bus state change after bus recovery was not properly notified

The patches in the next mails fix all these problems and are tested 
against mainline linux 3.12.24-rt38 with PREEMPT_RT patch.

Best regards,
Matthias Klein


             reply	other threads:[~2014-07-25 18:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-25 18:16 Matthias Klein [this message]
2014-07-25 19:04 ` can: flexcan: problems with bus error reporting om i.MX53 Sebastian Andrzej Siewior
2014-07-28  6:34 ` Matthias Klein

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=53D29F02.8010708@optimeas.de \
    --to=matthias.klein@optimeas.de \
    --cc=bigeasy@linutronix.de \
    --cc=linux-can@vger.kernel.org \
    --cc=mkl@pengutronix.de \
    --cc=support@karo-electronics.de \
    --cc=wg@grandegger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.