blob: 2a37b3fedb8e619d203c1a277c5a9e831da389cc [file] [log] [blame]
Linus Torvalds1da177e2005-04-16 15:20:36 -07001#
2# Plug and Play configuration
3#
4
Jan Engelhardt5c493f52007-07-15 23:39:38 -07005menuconfig PNP
Linus Torvalds1da177e2005-04-16 15:20:36 -07006 bool "Plug and Play support"
Jan Engelhardt5c493f52007-07-15 23:39:38 -07007 depends on HAS_IOMEM
Len Brown76f58582005-08-24 12:10:49 -04008 depends on ISA || ACPI
Linus Torvalds1da177e2005-04-16 15:20:36 -07009 ---help---
10 Plug and Play (PnP) is a standard for peripherals which allows those
11 peripherals to be configured by software, e.g. assign IRQ's or other
12 parameters. No jumpers on the cards are needed, instead the values
13 are provided to the cards from the BIOS, from the operating system,
14 or using a user-space utility.
15
16 Say Y here if you would like Linux to configure your Plug and Play
17 devices. You should then also say Y to all of the protocols below.
18 Alternatively, you can say N here and configure your PnP devices
19 using user space utilities such as the isapnptools package.
20
21 If unsure, say Y.
22
Bjorn Helgaas97ef0622008-08-19 16:53:41 -060023config PNP_DEBUG_MESSAGES
24 default y
25 bool "PNP debugging messages"
26 depends on PNP
27 help
28 Say Y here if you want the PNP layer to be able to produce debugging
29 messages if needed. The messages can be enabled at boot-time with
30 the pnp.debug kernel parameter.
31
32 This option allows you to save a bit of space if you do not want
33 the messages to even be built into the kernel.
34
35 If you have any doubts about this, say Y here.
36
Jan Engelhardt5c493f52007-07-15 23:39:38 -070037if PNP
38
Linus Torvalds1da177e2005-04-16 15:20:36 -070039comment "Protocols"
Linus Torvalds1da177e2005-04-16 15:20:36 -070040
41source "drivers/pnp/isapnp/Kconfig"
42
43source "drivers/pnp/pnpbios/Kconfig"
44
45source "drivers/pnp/pnpacpi/Kconfig"
46
Jan Engelhardt5c493f52007-07-15 23:39:38 -070047endif # PNP