From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Dong Aisheng-B29396 <B29396@freescale.com>
Cc: Wolfgang Grandegger <wg@grandegger.com>,
Shawn Guo <shawn.guo@linaro.org>,
Linux Netdev List <netdev@vger.kernel.org>,
Linux-CAN <linux-can@vger.kernel.org>,
Hui Wang <jason77.wang@gmail.com>
Subject: Re: [PATCH] flexcan: disable bus error interrupts for the i.MX28
Date: Mon, 08 Oct 2012 11:31:31 +0200 [thread overview]
Message-ID: <50729D73.3050409@pengutronix.de> (raw)
In-Reply-To: <7FE21149F4667147B645348EC60578850B2A8D51@039-SN2MPN1-011.039d.mgd.msft.net>
[-- Attachment #1: Type: text/plain, Size: 1535 bytes --]
On 10/08/2012 11:13 AM, Dong Aisheng-B29396 wrote:
>>> I just checked our ic guy of flexcan, it seems he also had no sense of
>> this issue.
>>>
>>> Below is some version info what I got:
>>> Mx6s use FlexCAN3, with IP version 10.00.12.00
>>> Mx53 use FlexCAN2 (with glitch filter), with IP version 03.00.00.00
>>> Mx28 use FlexCAN2 (with glitch filter), with IP version 03.00.04.00
>>> Mx35 use FlexCAN2 (without glitch filter) , with IP version
>>> 03.00.00.00
>>> Mx25 use FlexCAN2 (without glitch filter), with IP version 03.00.00.00
>>> I'm not sure if mx6q has such issue.
>>
>> OK, we need to find that out experimentally.
>>
> Our IC owner double checked the MX35 and MX53 IP and found the RX_WARN & TX_WARN
> Interrupt source actually are not connected to ARM.
Does this mean it's a SoC problem, not a problem of the ip core?
> That means flexcan will not trigger interrupt to ARM core even RX_WARN or TX_WARN
> Happens.
> This may be the root cause that why you cannot see RX_WARN interrupt if not enable
> bus error interrupt on mx35.
> He also checked that mx6q has the rx/tx warning interrupt connected to arm.
> So we guess mx6q does not have this issue.
> Anyway, we can test to confirm.
What about mx25?
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Industrial Linux Solutions | Phone: +49-231-2826-924 |
Vertretung West/Dortmund | Fax: +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 259 bytes --]
next prev parent reply other threads:[~2012-10-08 9:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-28 13:17 [PATCH] flexcan: disable bus error interrupts for the i.MX28 Wolfgang Grandegger
2012-09-29 6:00 ` Hui Wang
2012-10-07 3:09 ` Shawn Guo
2012-10-07 14:48 ` Wolfgang Grandegger
2012-10-08 7:59 ` Dong Aisheng-B29396
2012-10-08 9:03 ` Wolfgang Grandegger
2012-10-08 9:13 ` Dong Aisheng-B29396
2012-10-08 9:31 ` Marc Kleine-Budde [this message]
2012-10-08 9:42 ` Dong Aisheng-B29396
2012-10-09 11:52 ` Dong Aisheng-B29396
2012-10-09 12:32 ` Wolfgang Grandegger
2012-10-10 20:04 ` Marc Kleine-Budde
2012-10-11 1:41 ` Dong Aisheng
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=50729D73.3050409@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=B29396@freescale.com \
--cc=jason77.wang@gmail.com \
--cc=linux-can@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shawn.guo@linaro.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).