Searched +full:subsystem +full:- +full:level (Results 1 – 25 of 1029) sorted by relevance
12345678910>>...42
| /kernel/linux/linux-5.10/Documentation/ABI/testing/ |
| D | sysfs-bus-iio-counter-104-quad-8 | 7 Contact: linux-iio@vger.kernel.org
9 This interface is deprecated; please use the Counter subsystem.
16 Contact: linux-iio@vger.kernel.org
18 This interface is deprecated; please use the Counter subsystem.
21 normal, range limit, non-recycle, and modulo-n. The preset value
36 Non-recycle:
37 Counter is disabled whenever a 24-bit count overflow or
38 underflow takes place. The counter is re-enabled when a
42 Modulo-N:
52 Contact: linux-iio@vger.kernel.org
[all …]
|
| /kernel/linux/linux-5.10/Documentation/power/ |
| D | runtime_pm.rst | 5 (C) 2009-2011 Rafael J. Wysocki <rjw@sisk.pl>, Novell Inc.
15 at the power management core (PM core) level by means of:
18 put their PM-related work items. It is strongly recommended that pm_wq be
20 them to be synchronized with system-wide power transitions (suspend to RAM,
53 The ->runtime_suspend(), ->runtime_resume() and ->runtime_idle() callbacks
54 are executed by the PM core for the device's subsystem that may be either of
57 1. PM domain of the device, if the device's PM domain object, dev->pm_domain,
60 2. Device type of the device, if both dev->type and dev->type->pm are present.
62 3. Device class of the device, if both dev->class and dev->class->pm are
65 4. Bus type of the device, if both dev->bus and dev->bus->pm are present.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/driver-api/fpga/ |
| D | intro.rst | 4 The FPGA subsystem supports reprogramming FPGAs dynamically under
7 * The FPGA subsystem is vendor agnostic.
9 * The FPGA subsystem separates upper layers (userspace interfaces and
16 other users. Write the linux-fpga mailing list and maintainers and
24 ------------
27 this is the subsystem for you. Low level FPGA manager drivers contain
28 the knowledge of how to program a specific device. This subsystem
29 includes the framework in fpga-mgr.c and the low level drivers that
33 -----------
37 programming begins and re-enabled afterwards. An FPGA bridge may be
[all …]
|
| /kernel/linux/linux-6.6/Documentation/driver-api/fpga/ |
| D | intro.rst | 4 The FPGA subsystem supports reprogramming FPGAs dynamically under
7 * The FPGA subsystem is vendor agnostic.
9 * The FPGA subsystem separates upper layers (userspace interfaces and
16 other users. Write the linux-fpga mailing list and maintainers and
24 ------------
27 this is the subsystem for you. Low level FPGA manager drivers contain
28 the knowledge of how to program a specific device. This subsystem
29 includes the framework in fpga-mgr.c and the low level drivers that
33 -----------
37 programming begins and re-enabled afterwards. An FPGA bridge may be
[all …]
|
| /kernel/linux/linux-5.10/include/linux/ |
| D | pm.h | 1 /* SPDX-License-Identifier: GPL-2.0-or-later */
3 * pm.h - Power management interface
55 * struct dev_pm_ops - device PM callbacks.
59 * subsystem and generally the rest of the kernel is supposed to prevent
62 * registration of a child already in progress), it may return -EAGAIN, so
72 * runtime-suspended and it may be left in that state during the entire
77 * The PM core executes subsystem-level @prepare() for all devices before
95 * The PM core executes subsystem-level @complete() after it has executed
109 * depends on the device's subsystem (PM domain, device type, class or bus
110 * type), but generally the device must be quiescent after subsystem-level
[all …]
|
| /kernel/linux/linux-6.6/Documentation/power/ |
| D | runtime_pm.rst | 5 (C) 2009-2011 Rafael J. Wysocki <rjw@sisk.pl>, Novell Inc.
15 at the power management core (PM core) level by means of:
18 put their PM-related work items. It is strongly recommended that pm_wq be
20 them to be synchronized with system-wide power transitions (suspend to RAM,
53 The ->runtime_suspend(), ->runtime_resume() and ->runtime_idle() callbacks
54 are executed by the PM core for the device's subsystem that may be either of
57 1. PM domain of the device, if the device's PM domain object, dev->pm_domain,
60 2. Device type of the device, if both dev->type and dev->type->pm are present.
62 3. Device class of the device, if both dev->class and dev->class->pm are
65 4. Bus type of the device, if both dev->bus and dev->bus->pm are present.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/scsi/ |
| D | scsi.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 SCSI subsystem documentation
8 the SCSI subsystem in the Linux kernel (lk) 2.4 series. See:
9 http://www.tldp.org/HOWTO/SCSI-2.4-HOWTO . The LDP has single
12 http://web.archive.org/web/%2E/http://www.torque.net/scsi/SCSI-2.4-HOWTO
14 Notes on using modules in the SCSI subsystem
20 The scsi-core (also known as the "mid level") contains the core of scsi
27 the SCSI subsystem.
29 The individual upper and lower level drivers can be loaded in any order
33 level drivers to support the various assorted devices which can be
[all …]
|
| /kernel/linux/linux-6.6/Documentation/scsi/ |
| D | scsi.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 SCSI subsystem documentation
8 the SCSI subsystem in the Linux kernel (lk) 2.4 series. See:
9 https://www.tldp.org/HOWTO/SCSI-2.4-HOWTO . The LDP has single
12 Notes on using modules in the SCSI subsystem
18 The scsi-core (also known as the "mid level") contains the core of SCSI
25 the SCSI subsystem.
27 The individual upper and lower level drivers can be loaded in any order
29 as a module). The disk driver (sd_mod.o), CD-ROM driver (sr_mod.o),
31 level drivers to support the various assorted devices which can be
[all …]
|
| /kernel/linux/linux-6.6/include/linux/ |
| D | pm.h | 1 /* SPDX-License-Identifier: GPL-2.0-or-later */
3 * pm.h - Power management interface
63 * struct dev_pm_ops - device PM callbacks.
67 * subsystem and generally the rest of the kernel is supposed to prevent
70 * registration of a child already in progress), it may return -EAGAIN, so
80 * runtime-suspended and it may be left in that state during the entire
85 * The PM core executes subsystem-level @prepare() for all devices before
103 * The PM core executes subsystem-level @complete() after it has executed
117 * depends on the device's subsystem (PM domain, device type, class or bus
118 * type), but generally the device must be quiescent after subsystem-level
[all …]
|
| /kernel/linux/linux-5.10/Documentation/networking/ |
| D | nfc.rst | 2 Linux NFC subsystem
5 The Near Field Communication (NFC) subsystem is required to standardize the
14 The NFC subsystem is responsible for:
15 - NFC adapters management;
16 - Polling for targets;
17 - Low-level data exchange;
19 The subsystem is divided in some parts. The 'core' is responsible for
21 responsible for providing an interface to control operations and low-level
26 The low-level data exchange interface is provided by the new socket family
29 .. code-block:: none
[all …]
|
| /kernel/linux/linux-6.6/Documentation/networking/ |
| D | nfc.rst | 2 Linux NFC subsystem
5 The Near Field Communication (NFC) subsystem is required to standardize the
14 The NFC subsystem is responsible for:
15 - NFC adapters management;
16 - Polling for targets;
17 - Low-level data exchange;
19 The subsystem is divided in some parts. The 'core' is responsible for
21 responsible for providing an interface to control operations and low-level
26 The low-level data exchange interface is provided by the new socket family
29 .. code-block:: none
[all …]
|
| /kernel/linux/linux-6.6/Documentation/maintainer/ |
| D | rebasing-and-merging.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 Maintaining a subsystem, as a general rule, requires a familiarity with the
8 Git source-code management system. Git is a powerful tool with a lot of
30 - Changing the parent (starting) commit upon which a series of patches is
36 - Changing the history of a set of patches by fixing (or deleting) broken
48 - History that has been exposed to the world beyond your private system
54 That said, there are always exceptions. Some trees (linux-next being
61 - Do not rebase a branch that contains history created by others. If you
67 - Do not reparent a tree without a good reason to do so. Just being on a
71 - If you must reparent a repository, do not pick some random kernel commit
[all …]
|
| D | maintainer-entry-profile.rst | 6 The Maintainer Entry Profile supplements the top-level process documents
7 (submitting-patches, submitting drivers...) with
8 subsystem/device-driver-local customs as well as details about the patch
9 submission life-cycle. A contributor uses this document to level set
16 --------
17 Provide an introduction to how the subsystem operates. While MAINTAINERS
19 convey other subsystem-local infrastructure and mechanisms that aid
24 - Are there notifications when patches are applied to the local tree, or
26 - Does the subsystem have a patchwork instance? Are patchwork state
28 - Any bots or CI infrastructure that watches the list, or automated
[all …]
|
| /kernel/linux/linux-6.6/Documentation/core-api/ |
| D | printk-index.rst | 1 .. SPDX-License-Identifier: GPL-2.0
19 Finding these changes in the sources would require non-trivial parsers.
36 named according to the binaries where the printk formats are built-in. There
44 might appear in "vmlinux" when the module is built-in.
48 $> head -1 /sys/kernel/debug/printk/index/vmlinux; shuf -n 5 vmlinux
49 # <level[,flags]> filename:line function "format"
50 <5> block/blk-settings.c:661 disk_stack_limits "%s: Warning: Device %s is misaligned\n"
54 <6> drivers/acpi/osl.c:1410 acpi_no_auto_serialize_setup "ACPI: auto-serialization disabled\n"
58 - :level: log level value: 0-7 for particular severity, -1 as default,
59 'c' as continuous line without an explicit log level
[all …]
|
| /kernel/linux/linux-6.6/Documentation/w1/ |
| D | w1-generic.rst | 2 Introduction to the 1-wire (w1) subsystem
5 The 1-wire bus is a simple master-slave bus that communicates via a single
9 drain output and by sampling the logic level of the signal line.
11 The w1 subsystem provides the framework for managing w1 masters and
18 - DS9490 usb device
19 - W1-over-GPIO
20 - DS2482 (i2c to w1 bridge)
21 - Emulated devices, such as a RS232 converter, parallel port adapter, etc
24 What does the w1 subsystem do?
25 ------------------------------
[all …]
|
| /kernel/linux/linux-5.10/Documentation/w1/ |
| D | w1-generic.rst | 2 Introduction to the 1-wire (w1) subsystem
5 The 1-wire bus is a simple master-slave bus that communicates via a single
9 drain output and by sampling the logic level of the signal line.
11 The w1 subsystem provides the framework for managing w1 masters and
18 - DS9490 usb device
19 - W1-over-GPIO
20 - DS2482 (i2c to w1 bridge)
21 - Emulated devices, such as a RS232 converter, parallel port adapter, etc
24 What does the w1 subsystem do?
25 ------------------------------
[all …]
|
| /kernel/linux/linux-5.10/Documentation/maintainer/ |
| D | rebasing-and-merging.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 Maintaining a subsystem, as a general rule, requires a familiarity with the
8 Git source-code management system. Git is a powerful tool with a lot of
30 - Changing the parent (starting) commit upon which a series of patches is
36 - Changing the history of a set of patches by fixing (or deleting) broken
48 - History that has been exposed to the world beyond your private system
54 That said, there are always exceptions. Some trees (linux-next being
61 - Do not rebase a branch that contains history created by others. If you
67 - Do not reparent a tree without a good reason to do so. Just being on a
71 - If you must reparent a repository, do not pick some random kernel commit
[all …]
|
| D | maintainer-entry-profile.rst | 6 The Maintainer Entry Profile supplements the top-level process documents
7 (submitting-patches, submitting drivers...) with
8 subsystem/device-driver-local customs as well as details about the patch
9 submission life-cycle. A contributor uses this document to level set
16 --------
17 Provide an introduction to how the subsystem operates. While MAINTAINERS
19 convey other subsystem-local infrastructure and mechanisms that aid
24 - Are there notifications when patches are applied to the local tree, or
26 - Does the subsystem have a patchwork instance? Are patchwork state
28 - Any bots or CI infrastructure that watches the list, or automated
[all …]
|
| /kernel/linux/linux-6.6/Documentation/power/powercap/ |
| D | powercap.rst | 13 form of a tree of objects. The objects at the root level of the tree represent
15 example, the intel-rapl control type represents the Intel "Running Average
16 Power Limit" (RAPL) technology, whereas the 'idle-injection' control type
35 └──intel-rapl
36 ├──intel-rapl:0
43 │ ├──device -> ../../intel-rapl
45 │ ├──intel-rapl:0:0
52 │ │ ├──device -> ../../intel-rapl:0
60 │ │ ├──subsystem -> ../../../../../../class/power_cap
62 │ ├──intel-rapl:0:1
[all …]
|
| /kernel/linux/linux-5.10/Documentation/power/powercap/ |
| D | powercap.rst | 13 form of a tree of objects. The objects at the root level of the tree represent
15 example, the intel-rapl control type represents the Intel "Running Average
16 Power Limit" (RAPL) technology, whereas the 'idle-injection' control type
35 └──intel-rapl
36 ├──intel-rapl:0
43 │ ├──device -> ../../intel-rapl
45 │ ├──intel-rapl:0:0
52 │ │ ├──device -> ../../intel-rapl:0
60 │ │ ├──subsystem -> ../../../../../../class/power_cap
62 │ ├──intel-rapl:0:1
[all …]
|
| /kernel/linux/linux-6.6/Documentation/admin-guide/ |
| D | sysfs-rules.rst | 4 The kernel-exported sysfs exports internal kernel implementation details
11 low-level userspace applications, with a new kernel release, the users
12 of sysfs must follow some rules to use an as-abstract-as-possible way to
21 - Do not use libsysfs
23 offer any abstraction, it exposes all the kernel driver-core
31 - sysfs is always at ``/sys``
38 - devices are only "devices"
39 There is no such thing like class-, bus-, physical devices,
41 just simply a "device". Class-, bus-, physical, ... types are just
47 - devpath (``/devices/pci0000:00/0000:00:1d.1/usb2/2-2/2-2:1.0``)
[all …]
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/ |
| D | sysfs-rules.rst | 4 The kernel-exported sysfs exports internal kernel implementation details
11 low-level userspace applications, with a new kernel release, the users
12 of sysfs must follow some rules to use an as-abstract-as-possible way to
21 - Do not use libsysfs
23 offer any abstraction, it exposes all the kernel driver-core
31 - sysfs is always at ``/sys``
38 - devices are only "devices"
39 There is no such thing like class-, bus-, physical devices,
41 just simply a "device". Class-, bus-, physical, ... types are just
47 - devpath (``/devices/pci0000:00/0000:00:1d.1/usb2/2-2/2-2:1.0``)
[all …]
|
| D | thunderbolt.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 some differences at the register level among other things. Connection
18 software connection manager in Linux also advertises security level
21 the software connection manager only supports ``user`` security level and
25 -----------------------------------
27 should be a userspace tool that handles all the low-level details, keeps
31 found in ``Documentation/ABI/testing/sysfs-bus-thunderbolt``.
35 ``/etc/udev/rules.d/99-local.rules``::
37 ACTION=="add", SUBSYSTEM=="thunderbolt", ATTR{authorized}=="0", ATTR{authorized}="1"
44 security levels available. Intel Titan Ridge added one more security level
[all …]
|
| /kernel/linux/linux-6.6/Documentation/process/ |
| D | maintainer-soc.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 SoC Subsystem
8 --------
10 The SoC subsystem is a place of aggregation for SoC-specific code.
11 The main components of the subsystem are:
13 * devicetrees for 32- & 64-bit ARM and RISC-V
14 * 32-bit ARM board files (arch/arm/mach*)
15 * 32- & 64-bit ARM defconfigs
16 * SoC-specific drivers across architectures, in particular for 32- & 64-bit
17 ARM, RISC-V and Loongarch
[all …]
|
| /kernel/linux/linux-6.6/Documentation/netlabel/ |
| D | lsm_interface.rst | 25 NetLabel subsystem converts the security attributes to and from the correct
26 low-level packet label depending on the NetLabel build time and run time
37 level functions are translated into low level protocol operations based on how
38 the administrator has configured the NetLabel subsystem.
|
12345678910>>...42