From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Zhang Wei-r63237 <Wei.Zhang@freescale.com>
Cc: linuxppc-dev@ozlabs.org, Chen Gong-B11801 <G.Chen@freescale.com>,
paulus@samba.org
Subject: RE: [PATCH 1/3] Add a new member name to structure irq_host
Date: Tue, 24 Jul 2007 19:36:42 +1000 [thread overview]
Message-ID: <1185269802.5439.246.camel@localhost.localdomain> (raw)
In-Reply-To: <46B96294322F7D458F9648B60E15112C74CDC2@zch01exm26.fsl.freescale.net>
On Tue, 2007-07-24 at 17:25 +0800, Zhang Wei-r63237 wrote:
> Hi, Ben,
>
> Thanks! Please see my inline comments.
>
> >
> > Well, you would have to look at a cell blade or pSeries machine
> > device-tree, I don't have one at hand in DTS form... but basically,
> > those don't have a 1:1 relationship between hosts and nodes.
>
> Is there any problem when the relationship between hosts and nodes is
> not 1:1?
>
> The mapping method is defined in irq_alloc_host(). If there is only one
> host for many nodes,
> then these nodes will use the same mapping. Such as iic_host, the
> IRQ_HOST_MAP_LINEAR
> is used for its all nodes. We do _not_ care which node, we just care
> which virq is mapped from which host's hw irq.
Sure and it all works fine, I was replying to the suggestion of adding a
device_node pointer in there.
> >
> > Anyway, I discussed with Michael today and it might be a good idea to
> > provide an optional device node field in the host struct that can be
> > used by the majority of the PICs that have one host == one node, that
> > would provide a good default for the name() function.
> >
>
> But we have some irq host which has not OF-node bound.
Sure, hence the word 'optional' which would provide a default name.
Ben.
next prev parent reply other threads:[~2007-07-24 9:36 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 [this message]
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
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=1185269802.5439.246.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=G.Chen@freescale.com \
--cc=Wei.Zhang@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).