linux-kernel - Re: [PATCH] phy: request shared IRQ

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:   Wed, 24 Aug 2016 16:15:19 -0500
From:   Xander Huff <xander.huff@...com>
To:     Sergei Shtylyov <sergei.shtylyov@...entembedded.com>,
        f.fainelli@...il.com
CC:     netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
        brad.mouring@...com, Nathan Sullivan <nathan.sullivan@...com>
Subject: Re: [PATCH] phy: request shared IRQ

On 8/24/2016 1:41 PM, Sergei Shtylyov wrote:
> Hello.
>
> On 08/24/2016 08:53 PM, Xander Huff wrote:
>
>> From: Nathan Sullivan <nathan.sullivan@...com>
>>
>> On hardware with multiple PHY devices hooked up to the same IRQ line, allow
>> them to share it.
>
>     Note that it had been allowed until my (erroneous?) commit
> 33c133cc7598e60976a069344910d63e56cc4401 ("phy: IRQ cannot be shared"), so I'd
> like this commit just reverted instead...
>     I'm not sure now what was the reason I concluded that the IRQ sharing was
> impossible... most probably I thought that the kernel IRQ handling code exited
> the loop over the IRQ actions once IRQ_HANDLED was returned -- which is
> obviously not so in reality...
>
> MBR, Sergei
>
Thanks for the suggestion, Sergei. I'll do just that.

-- 
Xander Huff
Staff Software Engineer
National Instruments