From: Jiang Liu <jiang....@linux.intel.com>

Introduce callback irq_chip.irq_write_msi_msg, so we can share common
code among MSI alike interrupt controllers, such as HPET and DMAR.

Signed-off-by: Jiang Liu <jiang....@linux.intel.com>
Cc: Bjorn Helgaas <bhelg...@google.com>
Cc: Grant Likely <grant.lik...@linaro.org>
Cc: Marc Zyngier <marc.zyng...@arm.com>
Cc: Yingjoe Chen <yingjoe.c...@mediatek.com>
Cc: Yijing Wang <wangyij...@huawei.com>
Signed-off-by: Thomas Gleixner <t...@linutronix.de>
---
 include/linux/irq.h |    8 ++++++++
 1 file changed, 8 insertions(+)

Index: tip/include/linux/irq.h
===================================================================
--- tip.orig/include/linux/irq.h
+++ tip/include/linux/irq.h
@@ -322,6 +322,7 @@ static inline irq_hw_number_t irqd_to_hw
  * @irq_release_resources:     optional to release resources acquired with
  *                             irq_request_resources
  * @irq_compose_msi_msg:       optional to compose message content for MSI
+ * @irq_write_msi_msg: optional to write message content for MSI
  * @flags:             chip specific flags
  */
 struct irq_chip {
@@ -359,6 +360,7 @@ struct irq_chip {
        void            (*irq_release_resources)(struct irq_data *data);
 
        void            (*irq_compose_msi_msg)(struct irq_data *data, struct 
msi_msg *msg);
+       void            (*irq_write_msi_msg)(struct irq_data *data, struct 
msi_msg *msg);
 
        unsigned long   flags;
 };
@@ -453,6 +455,12 @@ extern void irq_chip_ack_parent(struct i
 extern int irq_chip_retrigger_hierarchy(struct irq_data *data);
 #endif
 
+static inline void irq_chip_write_msi_msg(struct irq_data *data,
+                                         struct msi_msg *msg)
+{
+       data->chip->irq_write_msi_msg(data, msg);
+}
+
 /* Handling of unhandled and spurious interrupts: */
 extern void note_interrupt(unsigned int irq, struct irq_desc *desc,
                           irqreturn_t action_ret);


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to