netdev - RE: [PATCH 2.6.32 3/3] net: Make ks8851 snl work under Beagle Zippy combo board

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]

Message-ID: <14385191E87B904DBD836449AA30269D4F2135@MORGANITE.micrel.com>
Date:	Thu, 3 Dec 2009 17:17:09 -0800
From:	"Ha, Tristram" <Tristram.Ha@...rel.Com>
To:	"David Miller" <davem@...emloft.net>
Cc:	<ben@...tec.co.uk>, <netdev@...r.kernel.org>,
	<linux-kernel@...r.kernel.org>
Subject: RE: [PATCH 2.6.32 3/3] net: Make ks8851 snl work under Beagle Zippy combo board

David Miller wrote:
> From: "Ha, Tristram" <Tristram.Ha@...rel.Com>
> Date: Thu, 3 Dec 2009 13:30:03 -0800
> 
>> From: Tristram Ha <Tristram.Ha@...rel.com>
>> 
>> The Micrel KSZ8851 SNL Ethernet chip is used in the OMAP Beagle Zippy
combo board.  Requesting
>> interrupt using level triggering flag hangs the system because the
interrupt handling routine
>> is called continually.  Using edge triggering avoids this problem.
As a result, disabling
>> interrupt may not be necessary.   
>> 
>> Signed-off-by: Tristram Ha <Tristram.Ha@...rel.com>
> 
> You say "may not be necessary", do you actually know for sure?
> 
> This seems questionable, if the interrupt disabling was there for a
reason what has changed to
> make it such that it is no longer necessary? 

I have tested the KSZ8851 SNL driver using the OMAP Beagle Zippy combo
board, developed by Tin Can Tools.  Ben Dooks, who implemented the
original driver, has his own KSZ8851 SNL evaluation board, but he
probably did not run any performance test on the driver.  I did sent him
the changes before so that he can verify on his board, but I have not
received any response.

So I really do not know if interrupt disabling is necessary or not.  But
from my understanding of the SPI network driver model, it is almost
required the interrupt be edge triggered, as the hardware interrupt
cannot be disabled inside the actual interrupt handling routine.  So if
the interrupt is level triggered, the interrupt routine will be called
continually, and there is no chance for the workqueue to disable the
interrupt.  As the interrupt is edge triggered, I do not think the
interrupt needs to be disabled.
--
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