From: Mugunthan V N <mugunthanvnm@ti.com>
To: Pantelis Antoniou <panto@antoniou-consulting.com>
Cc: "Bedia, Vaibhav" <vaibhav.bedia@ti.com>,
Richard Cochran <richardcochran@gmail.com>,
"Porter, Matt" <mporter@ti.com>,
"Maupin, Chase" <chase.maupin@ti.com>,
"Kridner, Jason" <jdk@ti.com>, Tony Lindgren <tony@atomide.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] cpsw: Fix interrupt storm among other things
Date: Thu, 31 Jan 2013 00:57:56 +0530 [thread overview]
Message-ID: <5109743C.7010703@ti.com> (raw)
In-Reply-To: <C6DFFB7E-2A5A-4A4A-ABAB-BF0C2739C44A@antoniou-consulting.com>
Hi Antoniou
On 1/30/2013 7:25 PM, Pantelis Antoniou wrote:
> Hi Mugunthan,
>
> On Jan 30, 2013, at 3:53 PM, Mugunthan V N wrote:
>
>> On 1/30/2013 7:21 PM, Pantelis Antoniou wrote:
>>> Hi Vaibhav,
>>>
>>> On Jan 30, 2013, at 3:47 PM, Bedia, Vaibhav wrote:
>>>
>>>> Hi Antoniou,
>>>>
>>>> On Wed, Jan 30, 2013 at 19:07:19, Pantelis Antoniou wrote:
>>>>> Hi Vaibhav,
>>>>>
>>>>> On Jan 30, 2013, at 3:29 PM, Bedia, Vaibhav wrote:
>>>>>
>>>>>> On Wed, Jan 30, 2013 at 18:14:30, Pantelis Antoniou wrote:
>>>>>>> Hi Vaibhav,
>>>>>>>
>>>>>>> On Jan 30, 2013, at 2:38 PM, Bedia, Vaibhav wrote:
>>>>>>>
>>>>>>>> On Wed, Jan 30, 2013 at 16:38:50, Pantelis Antoniou wrote:
>>>>>>>> [...]
>>>>>>>>> TBH I haven't found a simple way to print out the silicon revision number.
>>>>>>>>> Anyone on the list know a quick and dirty method?
>>>>>>>>>
>>>>>>>> You can dump the DEVICE_ID register @ 0x44e10600.
>>>>>>>> Bits 31:28 should be 0 for PG1.0 and 1 for PG2.0.
>>>>>>>>
>>>>>>> Thanks this works perfectly:
>>>>>>>
>>>>>>> original-bone:
>>>>>>> root@beaglebone:~# devmem2 0x44e10600 w
>>>>>>> Read at address 0x44E10600 (0xb6ff4600): 0x0B94402E
>>>>>>>
>>>>>>> bone-black:
>>>>>>> root@beaglebone:~# devmem2 0x44e10600 w
>>>>>>> Read at address 0x44E10600 (0xb6fcc600): 0x1B94402E
>>>>>>>
>>>>>> I just re-read the mail-chain and I am confused here.
>>>>>> So the patch in question is meant for Bone-A4 which has
>>>>>> PG1.0?
>>>>>>
>>>>> It is a general bug fix. The problem was discovered only on
>>>>> the bone black which has PG2.0 silicon. The driver has been
>>>>> tested and it works on the original bone with PG1.0 as well.
>>>>>
>>>> But Mugunthan mentioned that he doesn't see this on an EVM
>>>> with PG2.0 silicon... is there any board dependency here?
>>>>
>>> I don't know, but I doubt it. How about we wait for Mugunthan to
>>> send us what are the DEVICE_ID contents for his board.
>>>
>>>> Regards,
>>>> Vaibhav
>>> Regards
>>>
>>> -- Pantelis
>>>
>> This is the device ID which i have
>>
>> [root@arago /]# devmem 0x44e10600
>> 0x1B94402E
>>
> No clue what's the difference of the black with the EVM, and why this happens.
> The fix is valid anyway.
I am able to see the issue in EVM also by comparing the number of rx
interrupt received
from CPSW and no of packets actually received. But this can be resolved
by acknowledging
the interrupt in cpdma driver.
Regards
Mugunthan V N
>> Regards
>> Mugunthan V N
> Regards
>
> -- Pantelis
>
prev parent reply other threads:[~2013-01-30 19:28 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-28 13:11 [PATCH] cpsw: Fix interrupt storm among other things Pantelis Antoniou
2013-01-28 18:24 ` Richard Cochran
2013-01-28 18:40 ` Pantelis Antoniou
2013-01-28 19:49 ` Richard Cochran
2013-01-28 19:56 ` Richard Cochran
2013-01-28 18:27 ` Richard Cochran
2013-01-28 21:14 ` Peter Korsgaard
2013-01-30 8:34 ` Pantelis Antoniou
2013-01-29 11:45 ` Mugunthan V N
2013-01-30 8:36 ` Pantelis Antoniou
2013-01-30 9:03 ` Mugunthan V N
2013-01-30 9:36 ` Pantelis Antoniou
2013-01-30 10:55 ` Mugunthan V N
2013-01-30 11:08 ` Pantelis Antoniou
2013-01-30 12:38 ` Bedia, Vaibhav
2013-01-30 12:44 ` Pantelis Antoniou
2013-01-30 13:29 ` Bedia, Vaibhav
2013-01-30 13:37 ` Pantelis Antoniou
2013-01-30 13:47 ` Bedia, Vaibhav
2013-01-30 13:51 ` Pantelis Antoniou
2013-01-30 13:53 ` Mugunthan V N
2013-01-30 13:55 ` Pantelis Antoniou
2013-01-30 14:03 ` Mugunthan V N
2013-01-30 19:27 ` Mugunthan V N [this message]
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=5109743C.7010703@ti.com \
--to=mugunthanvnm@ti.com \
--cc=chase.maupin@ti.com \
--cc=jdk@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mporter@ti.com \
--cc=panto@antoniou-consulting.com \
--cc=richardcochran@gmail.com \
--cc=tony@atomide.com \
--cc=vaibhav.bedia@ti.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).