summaryrefslogblamecommitdiff
path: root/drivers/pnp/Kconfig
blob: 1959cef8e9debc6e613882ebfd06427ecab929d2 (plain) (tree) 
1da177e4c3f4





e25df1205f37 ^

1da177e4c3f4



76f58584824c ^

1da177e4c3f4
































1
2
3
4
5

6

7
8
9

10

11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42





                             
                            


                                    
                              































                                                                               
#
# Plug and Play configuration
#

menu "Plug and Play support"
	depends on HAS_IOMEM

config PNP
	bool "Plug and Play support"
	depends on ISA || ACPI
	---help---
	  Plug and Play (PnP) is a standard for peripherals which allows those
	  peripherals to be configured by software, e.g. assign IRQ's or other
	  parameters. No jumpers on the cards are needed, instead the values
	  are provided to the cards from the BIOS, from the operating system,
	  or using a user-space utility.

	  Say Y here if you would like Linux to configure your Plug and Play
	  devices. You should then also say Y to all of the protocols below.
	  Alternatively, you can say N here and configure your PnP devices
	  using user space utilities such as the isapnptools package.

	  If unsure, say Y.

config PNP_DEBUG
	bool "PnP Debug Messages"
	depends on PNP
	help
	  Say Y if you want the Plug and Play Layer to print debug messages.
	  This is useful if you are developing a PnP driver or troubleshooting.

comment "Protocols"
	depends on PNP

source "drivers/pnp/isapnp/Kconfig"

source "drivers/pnp/pnpbios/Kconfig"

source "drivers/pnp/pnpacpi/Kconfig"

endmenu