1comment "Interrupt controller options"
 2
 3config INTC_USERIMASK
 4	bool "Userspace interrupt masking support"
 5	depends on ARCH_SHMOBILE || (SUPERH && CPU_SH4A)
 6	help
 7	  This enables support for hardware-assisted userspace hardirq
 8	  masking.
 9
10	  SH-4A and newer interrupt blocks all support a special shadowed
11	  page with all non-masking registers obscured when mapped in to
12	  userspace. This is primarily for use by userspace device
13	  drivers that are using special priority levels.
14
15	  If in doubt, say N.
16
17config INTC_BALANCING
18	bool "Hardware IRQ balancing support"
19	depends on SMP && SUPERH && CPU_SHX3
20	help
21	  This enables support for IRQ auto-distribution mode on SH-X3
22	  SMP parts. All of the balancing and CPU wakeup decisions are
23	  taken care of automatically by hardware for distributed
24	  vectors.
25
26	  If in doubt, say N.
27
28config INTC_MAPPING_DEBUG
29	bool "Expose IRQ to per-controller id mapping via debugfs"
30	depends on DEBUG_FS
31	help
32	  This will create a debugfs entry for showing the relationship
33	  between system IRQs and the per-controller id tables.
34
35	  If in doubt, say N.

 1config SH_INTC
 2	bool
 3	select IRQ_DOMAIN
 4
 5if SH_INTC
 6
 7comment "Interrupt controller options"
 8
 9config INTC_USERIMASK
10	bool "Userspace interrupt masking support"
11	depends on (SUPERH && CPU_SH4A) || COMPILE_TEST
12	help
13	  This enables support for hardware-assisted userspace hardirq
14	  masking.
15
16	  SH-4A and newer interrupt blocks all support a special shadowed
17	  page with all non-masking registers obscured when mapped in to
18	  userspace. This is primarily for use by userspace device
19	  drivers that are using special priority levels.
20
21	  If in doubt, say N.
22
23config INTC_BALANCING
24	bool "Hardware IRQ balancing support"
25	depends on SMP && SUPERH && CPU_SHX3
26	help
27	  This enables support for IRQ auto-distribution mode on SH-X3
28	  SMP parts. All of the balancing and CPU wakeup decisions are
29	  taken care of automatically by hardware for distributed
30	  vectors.
31
32	  If in doubt, say N.
33
34config INTC_MAPPING_DEBUG
35	bool "Expose IRQ to per-controller id mapping via debugfs"
36	depends on DEBUG_FS
37	help
38	  This will create a debugfs entry for showing the relationship
39	  between system IRQs and the per-controller id tables.
40
41	  If in doubt, say N.
42
43endif