From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Michael Ellerman <mpe@ellerman.id.au>,
linuxppc dev list <linuxppc-dev@lists.ozlabs.org>,
"stewart@linux.vnet.ibm.com" <stewart@linux.vnet.ibm.com>
Subject: Re: [PATCH] powerpc/opal-irqchip: Use interrupt names if present
Date: Wed, 30 Nov 2016 19:21:24 +1100 [thread overview]
Message-ID: <1480494084.3459.7.camel@kernel.crashing.org> (raw)
In-Reply-To: <87d1hdpf0r.fsf@concordia.ellerman.id.au>
On Wed, 2016-11-30 at 19:07 +1100, Michael Ellerman wrote:
> Benjamin Herrenschmidt <benh@kernel.crashing.org> 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 there's a generic device tree
> spec for this sort of thing, and if so whether we should use it?
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 interrupts either.
So for this specific case, just adding a new prop with a string-list
matching 1:1 the entries in "opal-interrupts" is the most logical
choice.
Cheers,
Ben.
next prev parent reply other threads:[~2016-11-30 8:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-29 23:56 [PATCH] powerpc/opal-irqchip: Use interrupt names if present Benjamin Herrenschmidt
2016-11-30 8:07 ` Michael Ellerman
2016-11-30 8:21 ` Benjamin Herrenschmidt [this message]
2016-11-30 8:25 ` Benjamin Herrenschmidt
-- strict thread matches above, loose matches on Subject: below --
2017-02-06 5:07 Benjamin Herrenschmidt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1480494084.3459.7.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=stewart@linux.vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).