From: Segher Boessenkool <segher@kernel.crashing.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, Chen Gong <g.chen@freescale.com>,
paulus@samba.org
Subject: Re: [PATCH 1/3] Add a new member name to structure irq_host
Date: Wed, 1 Aug 2007 00:13:19 +0200 [thread overview]
Message-ID: <91856a9e02132d2deb4368eee954c931@kernel.crashing.org> (raw)
In-Reply-To: <1185918267.5495.505.camel@localhost.localdomain>
>>> Which makes me think (again) that we should have an optional
>>> device_node
>>> pointer in irq_host. I know you said you wanted the irq stuff to be
>>> OF
>>> agnostic, but the reality is most of the implementations do have an
>>> OF
>>> node. And all of the newer irq_host implementations do, with the
>>> exception of PS3 and celleb - which are special.
>>
>> How do you suggest to get a reasonable display name out of
>> the device tree? The recommended human-readable name for
>> interrupt controller nodes is "interrupt-controller"...
>> You cannot use "device_type" either, and using "compatible"
>> requires selecting one of its string entries, and likely
>> using a lookup table after that, too.
>
> In that case, I would display the node full path.
Those tend to be quite long, in the cases where there are
multiple interrupt controllers in the system; and really
useless otherwise. I think the interrupt controllers should
still just fill in the names "manually".
It's a good thing to have an of_node in the irq_host struct
anyway, though :-)
Segher
next prev parent reply other threads:[~2007-07-31 22:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-23 11:13 [PATCH 0/3] Add virq mapping debugfs for PowerPC Chen Gong
2007-07-23 11:13 ` [PATCH 1/3] Add a new member name to structure irq_host Chen Gong
2007-07-23 11:13 ` [PATCH 2/3] Add irq host name for all powerpc interrupt controllors Chen Gong
2007-07-23 11:13 ` [PATCH 3/3] Add irq debugfs and virq_mapping for getting the virq Chen Gong
2007-07-23 22:04 ` [PATCH 1/3] Add a new member name to structure irq_host Benjamin Herrenschmidt
2007-07-23 23:22 ` Michael Ellerman
2007-07-23 23:36 ` Benjamin Herrenschmidt
2007-07-24 4:06 ` Chen Gong-B11801
2007-07-24 4:33 ` Benjamin Herrenschmidt
2007-07-24 9:25 ` Zhang Wei-r63237
2007-07-24 9:36 ` Benjamin Herrenschmidt
2007-07-25 7:03 ` Zhang Wei-r63237
2007-07-31 19:42 ` Segher Boessenkool
2007-07-31 21:44 ` Benjamin Herrenschmidt
2007-07-31 22:13 ` Segher Boessenkool [this message]
2007-07-31 23:06 ` Michael Ellerman
2007-07-31 23:42 ` Segher Boessenkool
2007-07-23 11:55 ` [PATCH 0/3] Add virq mapping debugfs for PowerPC Stephen Rothwell
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=91856a9e02132d2deb4368eee954c931@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=benh@kernel.crashing.org \
--cc=g.chen@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
/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).