From: Michael Ellerman <michael@ellerman.id.au>
To: Zhang Wei-r63237 <Wei.Zhang@freescale.com>
Cc: Wang Haiying-r54964 <Haiying.Wang@freescale.com>,
paulus@samba.org, linuxppc-dev@ozlabs.org
Subject: RE: [PATCH 4/4] Add irq debugfs and virq_mapping for getting thevirq to irq host's hwirq mapping list.
Date: Tue, 27 Mar 2007 13:21:05 +1000 [thread overview]
Message-ID: <1174965665.5348.17.camel@concordia.ozlabs.ibm.com> (raw)
In-Reply-To: <46B96294322F7D458F9648B60E15112C132437@zch01exm26.fsl.freescale.net>
[-- Attachment #1: Type: text/plain, Size: 1246 bytes --]
On Tue, 2007-03-20 at 17:51 +0800, Zhang Wei-r63237 wrote:
> >
> > Minor nit. Should we be creating a 'powerpc' directory first, and
> > putting the 'irq' file under that? Otherwise we risk clashing
> > with some
> > generic code that creates a file called 'irq' in debugfs.
> >
> > cheers
> >
> Hi, Michael,
>
> I've seen some codes in arch/powerpc/kernel/prom.c to create debugfs
> dir "powerpc". But those codes were enabled by a local macro 'DEBUG'.
> There is a little problem. Maybe I should change '#ifdef DEBUG' to
> '#ifdef CONFIG_DEBUG_FS' before the export_flat_device_tree() function
> in arch/powerpc/kernel/prom.c. How about it?
No, we don't want to always export the flat device tree.
Instead I think you should add a function in
arch/powerpc/kernel/setup-common.c which creates the powerpc directory
if CONFIG_DEBUG_FS is enabled, make it an arch_initcall. Then the flat
device tree code can use that directory, and so can your irq stuff.
cheers
--
Michael Ellerman
OzLabs, IBM Australia Development Lab
wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)
We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-03-27 3:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-16 4:38 [PATCH 1/4] Add a new member 'name' to structure irq_host Zhang Wei
2007-03-16 4:38 ` [PATCH 2/4] Add i8259 host name Zhang Wei
2007-03-16 4:38 ` [PATCH 3/4] Add mpic " Zhang Wei
2007-03-16 4:38 ` [PATCH 4/4] Add irq debugfs and virq_mapping for getting the virq to irq host's hwirq mapping list Zhang Wei
2007-03-20 3:03 ` Michael Ellerman
2007-03-20 9:51 ` [PATCH 4/4] Add irq debugfs and virq_mapping for getting thevirq " Zhang Wei-r63237
2007-03-27 3:21 ` Michael Ellerman [this message]
2007-03-21 14:17 ` [PATCH 4/4] Add irq debugfs and virq_mapping for getting the virq " Segher Boessenkool
2007-03-21 20:24 ` Benjamin Herrenschmidt
2007-03-21 21:45 ` Segher Boessenkool
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=1174965665.5348.17.camel@concordia.ozlabs.ibm.com \
--to=michael@ellerman.id.au \
--cc=Haiying.Wang@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).