Recent versions of OPAL can provide names for the various OPAL interrupts,
so let's use them. This also modernises the code that fetches the
interrupt array to use the helpers provided by the generic code instead
of hand-parsing the property.
Signed-off-by: Benjamin Herrenschmidt
On Wed, 2016-11-30 at 19:21 +1100, Benjamin Herrenschmidt wrote:
>
> There isn't one. The existing "opal-interrupts" from day one was a
> bit
> weird anyway, it's not a proper "interrupts" property to begin with,
> but it's unfixable now. Also I don't think there's a generic way to
> name
On Wed, 2016-11-30 at 19:07 +1100, Michael Ellerman wrote:
> Benjamin Herrenschmidt writes:
>
> > Recent versions of OPAL will be able to provide names for the
> > various
> > OPAL interrupts via a new "opal-interrupt-names" property. So let's
> > use them to make
Benjamin Herrenschmidt writes:
> Recent versions of OPAL will be able to provide names for the various
> OPAL interrupts via a new "opal-interrupt-names" property. So let's
> use them to make /proc/interrupts more informative.
I guess there's no point asking whether
Recent versions of OPAL will be able to provide names for the various
OPAL interrupts via a new "opal-interrupt-names" property. So let's
use them to make /proc/interrupts more informative.
This also modernises the code that fetches the interrupt array to use
the helpers provided by the generic