[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110121222451.GA29468@merkur.ravnborg.org>
Date: Fri, 21 Jan 2011 23:24:51 +0100
From: Sam Ravnborg <sam@...nborg.org>
To: sparclinux <sparclinux@...r.kernel.org>,
David Miller <davem@...emloft.net>,
Thomas Gleixner <tglx@...utronix.de>
Cc: lkml <linux-kernel@...r.kernel.org>
Subject: [RFC PATCH 0/5] sparc64: drop deprecated irq features
This set of patches update sparc64 so no deprecated genirq
features are used.
I did this mainly to understand the genirq stuff better.
Originally I looked into sparc64 code and was confused
because it used deprecated stuff. So the logical step
was to update sparc64 to avoid the deprecated stuff.
So I did so and the result follows.
This is an RFC because:
- This is not yet tested
- I expect a (trivial) conflict when we get Thomas'
__DO_irq stuff merged
- I expect to get some feedback that needs to be addressed
I made one conceptual change.
irq_handler_data was previously assinged to irq_data.chip_data.
This is changed so it uses irq_data.handler_data
Looking into kernel/irq/* this looked OK.
I plan to do some testing within the next week.
I looked at integrating struct virt_irq_table[] as
chip_data in irq_data.
But the way the virt_irq_alloc() function is used did not
make this bovious how to do so. So I played safe and did
not try to do so.
Any comments aprreciated.
If there are more features from genirq we could use let me
know and I may look at it.
And if something just looks wrong please say so too.
Sam
Sam Ravnborg (5):
sparc64: fix direct access to irq_desc
sparc: in handler_irq() rename irq parameter to pil
sparc64: all pointers to irq_handler_data renamed to handler_data
sparc64: use {get,set}_irq_data for handler_data
sparc64: use up-to-data genirq functions
arch/sparc/Kconfig | 2 -
arch/sparc/kernel/irq_32.c | 20 ++--
arch/sparc/kernel/irq_64.c | 197 ++++++++++++++++++++---------------------
arch/sparc/kernel/sun4d_irq.c | 18 ++--
4 files changed, 117 insertions(+), 120 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists