public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Johannes Weiner <jw@emlix.com>
To: Chris Zankel <chris@zankel.net>
Cc: Oskar Schirmer <os@emlix.com>, Daniel Gloeckner <dg@emlix.com>,
	linux-kernel@vger.kernel.org
Subject: [patch 3/8] xtensa: variant irq set callbacks
Date: Tue, 10 Mar 2009 12:56:46 +0100	[thread overview]
Message-ID: <20090310120631.350359642@emlix.com> (raw)
In-Reply-To: 20090310115643.653120649@emlix.com

[-- Attachment #1: 0003-xtensa-variant-irq-set-callbacks.patch --]
[-- Type: text/plain, Size: 1874 bytes --]

Allow the core variant code to provide irq enable/disable callbacks.

The s6000 has a crossbar that multiplexes peripheral IRQ lines to a
smaller number of core lines.  These callbacks allow the s6000 variant
to program the crossbar when core lines are toggled.

Signed-off-by: Johannes Weiner <jw@emlix.com>
---
 arch/xtensa/Kconfig           |    3 +++
 arch/xtensa/include/asm/irq.h |    7 +++++++
 arch/xtensa/kernel/irq.c      |   14 ++++++++++++++
 3 files changed, 24 insertions(+)

--- a/arch/xtensa/Kconfig
+++ b/arch/xtensa/Kconfig
@@ -51,6 +51,9 @@ source "kernel/Kconfig.freezer"
 config MMU
 	def_bool n
 
+config VARIANT_IRQ_SWITCH
+	def_bool n
+
 menu "Processor type and features"
 
 choice
--- a/arch/xtensa/include/asm/irq.h
+++ b/arch/xtensa/include/asm/irq.h
@@ -14,6 +14,13 @@
 #include <platform/hardware.h>
 #include <variant/core.h>
 
+#ifdef CONFIG_VARIANT_IRQ_SWITCH
+#include <variant/irq.h>
+#else
+static inline void variant_irq_enable(unsigned int irq) { }
+static inline void variant_irq_disable(unsigned int irq) { }
+#endif
+
 #ifndef PLATFORM_NR_IRQS
 # define PLATFORM_NR_IRQS 0
 #endif
--- a/arch/xtensa/kernel/irq.c
+++ b/arch/xtensa/kernel/irq.c
@@ -132,6 +132,18 @@ static void xtensa_irq_unmask(unsigned i
 	set_sr (cached_irq_mask, INTENABLE);
 }
 
+static void xtensa_irq_enable(unsigned int irq)
+{
+	variant_irq_enable(irq);
+	xtensa_irq_unmask(irq);
+}
+
+static void xtensa_irq_disable(unsigned int irq)
+{
+	xtensa_irq_mask(irq);
+	variant_irq_disable(irq);
+}
+
 static void xtensa_irq_ack(unsigned int irq)
 {
 	set_sr(1 << irq, INTCLEAR);
@@ -146,6 +158,8 @@ static int xtensa_irq_retrigger(unsigned
 
 static struct irq_chip xtensa_irq_chip = {
 	.name		= "xtensa",
+	.enable		= xtensa_irq_enable,
+	.disable	= xtensa_irq_disable,
 	.mask		= xtensa_irq_mask,
 	.unmask		= xtensa_irq_unmask,
 	.ack		= xtensa_irq_ack,

-- 


  parent reply	other threads:[~2009-03-10 13:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-10 13:11 [patch 0/8] xtensa: s6000 & s6105 Johannes Weiner
2009-03-10 11:56 ` [patch 1/8] xtensa: nommu support Johannes Weiner
2009-03-10 11:56 ` [patch 2/8] xtensa: variant-specific code Johannes Weiner
2009-03-10 11:56 ` Johannes Weiner [this message]
2009-03-10 11:56 ` [patch 4/8] xtensa: s6000 variant core definitions Johannes Weiner
2009-03-10 11:56 ` [patch 5/8] xtensa: s6000 variant Johannes Weiner
2009-03-10 11:56 ` [patch 6/8] xtensa: s6000 gpio driver Johannes Weiner
2009-03-10 11:56 ` [patch 7/8] xtensa: let platform override KERNELOFFSET Johannes Weiner
2009-03-10 11:56 ` [patch 8/8] xtensa: platform stretch s6105 eval board Johannes Weiner

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=20090310120631.350359642@emlix.com \
    --to=jw@emlix.com \
    --cc=chris@zankel.net \
    --cc=dg@emlix.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=os@emlix.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