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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 8 Oct 2012 09:42:58 +0000
From:	Dong Aisheng-B29396 <B29396@...escale.com>
To:	Marc Kleine-Budde <mkl@...gutronix.de>
CC:	Wolfgang Grandegger <wg@...ndegger.com>,
	Shawn Guo <shawn.guo@...aro.org>,
	Linux Netdev List <netdev@...r.kernel.org>,
	Linux-CAN <linux-can@...r.kernel.org>,
	Hui Wang <jason77.wang@...il.com>
Subject: RE: [PATCH] flexcan: disable bus error interrupts for the i.MX28

>-----Original Message-----
>From: Marc Kleine-Budde [mailto:mkl@...gutronix.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:
>>>> 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?
>
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.

>> 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?
>
For mx25 and mx28, he could not access it now.
Will check tomorrow.

Regards
Dong Aisheng

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html