netdev - Re: GPY215 PHY interrupt issue

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] [day] [month] [year] [list]

Message-ID: <Y4lBT6FMCuUH1b6p@lunn.ch>
Date:   Fri, 2 Dec 2022 01:05:35 +0100
From:   Andrew Lunn <andrew@...n.ch>
To:     Michael Walle <michael@...le.cc>
Cc:     Heiner Kallweit <hkallweit1@...il.com>,
        Russell King <linux@...linux.org.uk>,
        Horatiu Vultur <horatiu.vultur@...rochip.com>,
        netdev@...r.kernel.org, Xu Liang <lxu@...linear.com>
Subject: Re: GPY215 PHY interrupt issue

> I don't even dare to ask, but wouldn't a device tree property
> maxlinear,use-broken-interrupts make more sense than a compile time
> option? I'm fine with both.

Maybe. But it limits it to DT based systems. It gets messy making it
work for PCI devices, USB devices, ACPI etc.

But i guess we can have it disabled by default, and leave it to
whoever wants it enabled to figure out how to enable i for whatever
configuration system they use.

So yes, maxlinear,use-broken-interrupts.

   Andrew