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