Thread (13 messages) 13 messages, 5 authors, 2012-10-11

RE: [PATCH] flexcan: disable bus error interrupts for the i.MX28

From: Dong Aisheng-B29396 <hidden>
Date: 2012-10-09 11:52:51
Also in: netdev

Hi Wolfgang,
-----Original Message-----
From: Dong Aisheng-B29396
Sent: Monday, October 08, 2012 5:44 PM
To: 'Marc Kleine-Budde'
Cc: Wolfgang Grandegger; Shawn Guo; Linux Netdev List; Linux-CAN; Hui Wang
Subject: RE: [PATCH] flexcan: disable bus error interrupts for the i.MX28
quoted
-----Original Message-----
From: Marc Kleine-Budde [mailto:mkl@pengutronix.de]
Sent: Monday, October 08, 2012 5:32 PM
To: Dong Aisheng-B29396
Cc: Wolfgang Grandegger; Shawn Guo; Linux Netdev List; Linux-CAN; Hui
Wang
Subject: Re: [PATCH] flexcan: disable bus error interrupts for the
i.MX28
Importance: High

On 10/08/2012 11:13 AM, Dong Aisheng-B29396 wrote:
quoted
quoted
quoted
I just checked our ic guy of flexcan, it seems he also had no sense
of
this issue.
quoted
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?
It's not a problem of ip core, it's about how to use the IP.
I do not know why some i.MX SoCs does not use rx/tx warn interrupts.
quoted
quoted
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.
quoted
So we guess mx6q does not have this issue.
Anyway, we can test to confirm.
What about mx25?
For mx25 and mx28, he could not access it now.
Will check tomorrow.
Just let you know:
The checking result is Mx28 has rx/tx warning interrupt line connected
while mx25 not.
Looks align with what we guess.

Regards
Dong Aisheng
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help