Yan, Like a8cd6925fc hv: pirq: clean up irq handlers ... There are several similar irq handlers with confusing function names and it's not friendly to call update_irq_handler() to update a proper handler after request_irq(). With this commit, a single generic irq handler is being used, in which, no lock need to be acquired because our design could guarantee there is no concurrent irq handling and irq handler request/free. A flags field is added to irq_desc struct to select the proper processing flow for an irq. Irqflags is defined as follows: IRQF_NONE (0U) IRQF_LEVEL (1U << 1U) /* 1: level trigger; 0: edge trigger */ IRQF_PT (1U << 2U) /* 1: for passthrough dev */ Because we have only one irq handler, update_irq_handler() should be replace by set_irq_trigger_mode(), whichs set trigger mode flag of a certian irq. Accordingly, the code where called update_irq_handler() need to be updated. Signed-off-by: Yan, Like <like.yan@intel.com> Acked-by: Anthony Xu <anthony.xu@intel.com>		2018-08-17 14:25:52 +08:00
..
hypercall.h	HV: trusty: new hypercall to save/restore context of secure world	2018-08-09 15:09:15 +08:00
irq.h	hv: pirq: clean up irq handlers	2018-08-17 14:25:52 +08:00
ptdev.h	hv: pirq: remove unnecessary dev_handler_node struct	2018-08-14 16:48:45 +08:00
schedule.h	HV:treewide:Cleanup the type for parameters of bitmap	2018-07-02 10:46:11 +08:00
softirq.h	hv: softirq: refine softirq	2018-08-01 11:36:27 +08:00