Documentation/admin-guide/pnp.rst
Source file repositories/reference/linux-study-clean/Documentation/admin-guide/pnp.rst
File Facts
- System
- Linux kernel
- Corpus path
Documentation/admin-guide/pnp.rst- Extension
.rst- Size
- 6970 bytes
- Lines
- 286
- Domain
- Support Tooling And Documentation
- Bucket
- Documentation
- Inferred role
- Support Tooling And Documentation: documentation
- Status
- atlas-only
Why This File Exists
Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
- Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
- No C-style include directives detected by the generator.
Detected Declarations
function serial_pnp_probefunction serial8250_pnp_init
Annotated Snippet
=================================
Linux Plug and Play Documentation
=================================
:Author: Adam Belay <ambx1@neo.rr.com>
:Last updated: Oct. 16, 2002
Overview
--------
Plug and Play provides a means of detecting and setting resources for legacy or
otherwise unconfigurable devices. The Linux Plug and Play Layer provides these
services to compatible drivers.
The User Interface
------------------
The Linux Plug and Play user interface provides a means to activate PnP devices
for legacy and user level drivers that do not support Linux Plug and Play. The
user interface is integrated into sysfs.
In addition to the standard sysfs file the following are created in each
device's directory:
- id - displays a list of support EISA IDs
- options - displays possible resource configurations
- resources - displays currently allocated resources and allows resource changes
activating a device
^^^^^^^^^^^^^^^^^^^
::
# echo "auto" > resources
this will invoke the automatic resource config system to activate the device
manually activating a device
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
::
# echo "manual <depnum> <mode>" > resources
<depnum> - the configuration number
<mode> - static or dynamic
static = for next boot
dynamic = now
disabling a device
^^^^^^^^^^^^^^^^^^
::
# echo "disable" > resources
EXAMPLE:
Suppose you need to activate the floppy disk controller.
1. change to the proper directory, in my case it is
/driver/bus/pnp/devices/00:0f::
# cd /driver/bus/pnp/devices/00:0f
# cat name
PC standard floppy disk controller
2. check if the device is already active::
Annotation
- Detected declarations: `function serial_pnp_probe`, `function serial8250_pnp_init`.
- Atlas domain: Support Tooling And Documentation / Documentation.
- Implementation status: atlas-only.
Implementation Notes
- This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
- Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
- Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.