[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191112140109.GK5090@lunn.ch>
Date: Tue, 12 Nov 2019 15:01:09 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Vladimir Oltean <olteanv@...il.com>
Cc: Marc Zyngier <maz@...nel.org>,
Rasmus Villemoes <linux@...musvillemoes.dk>,
Shawn Guo <shawnguo@...nel.org>, Li Yang <leoyang.li@....com>,
Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
linux-arm-kernel@...ts.infradead.org, devicetree@...r.kernel.org,
lkml <linux-kernel@...r.kernel.org>,
netdev <netdev@...r.kernel.org>
Subject: Re: [PATCH 2/2] ARM: dts: ls1021a-tsn: Use interrupts for the SGMII
PHYs
> > >> + /* SGMII2_PHY_INT_B: connected to IRQ2, active low
> > >> */
> > >> + interrupts-extended = <&extirq 2
> > >> IRQ_TYPE_EDGE_FALLING>;
> The interrupt specifier certainly works. So that points to an issue
> with the description. What do you mean, exactly? Does "active low"
> mean "level-triggered"? How would you have described this?
I would expect IRQ_TYPE_ACTIVE_LOW, or whatever it is called. Since
this is a shared interrupt, going on the edge i think opens up a race
condition and interrupts can be missed.
Andrew
Powered by blists - more mailing lists