Searched +full:subsystem +full:- +full:level (Results 1 – 25 of 850) sorted by relevance
12345678910>>...34
/linux-6.12.1/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 …]
|
/linux-6.12.1/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 …]
|
/linux-6.12.1/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 …]
|
D | cgroup.h | 1 /* SPDX-License-Identifier: GPL-2.0 */ 8 * Copyright (C) 2004-2006 Silicon Graphics, Inc. 28 #include <linux/cgroup-defs.h> 66 struct list_head iters_node; /* css_set->task_iters */ 85 * cgroup_subsys_enabled - fast test on whether a subsys is enabled 86 * @ss: subsystem in question 92 * cgroup_subsys_on_dfl - fast test on whether a subsys is on default hierarchy 93 * @ss: subsystem in question 163 * css_for_each_child - iterate through children of a css 169 * If a subsystem synchronizes ->css_online() and the start of iteration, a [all …]
|
/linux-6.12.1/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 …]
|
D | scsi_mid_low_api.rst | 1 .. SPDX-License-Identifier: GPL-2.0 4 SCSI mid_level - lower_level driver interface 9 This document outlines the interface between the Linux SCSI mid level and 10 SCSI lower level drivers. Lower level drivers (LLDs) are variously called 14 (SCSI terminology, see SAM-3 at http://www.t10.org) sends SCSI commands 20 its own subsystem in Linux (e.g. USB and ieee1394). In such cases the 21 SCSI subsystem LLD is a software bridge to the other driver subsystem. 22 Examples are the usb-storage driver (found in the drivers/usb/storage 30 HBAs. These HBAs might be either on PCI daughter-boards or built into 33 has its own PCI device address. [The one-to-one correspondence between [all …]
|
/linux-6.12.1/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 …]
|
/linux-6.12.1/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 …]
|
/linux-6.12.1/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 …]
|
D | genericirq.rst | 7 :Copyright: |copy| 2005-2010: Thomas Gleixner 8 :Copyright: |copy| 2005-2006: Ingo Molnar 22 interrupt subsystem based for their architecture, with the help of the 29 __do_IRQ() super-handler, which is able to deal with every type of 36 - Level type 38 - Edge type 40 - Simple type 44 - Fast EOI type 46 In the SMP world of the __do_IRQ() super-handler another type was 49 - Per CPU type [all …]
|
/linux-6.12.1/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 …]
|
/linux-6.12.1/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 …]
|
/linux-6.12.1/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 …]
|
/linux-6.12.1/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 …]
|
/linux-6.12.1/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.
|
/linux-6.12.1/drivers/soc/qcom/ |
D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only 15 the low-power state for resources related to the remoteproc 17 Subsystem (AOSS) using Qualcomm Messaging Protocol (QMP). 26 resource on a RPM-hardened platform must use this database to get 53 Last Level Cache Controller(LLCC) driver for platforms such as, 84 and instances handled by the remote DSPs. This is a kernel-space 124 Say yes here to support USB-C and battery status on modern Qualcomm 147 purpose of exchanging sector-data between the remote filesystem 156 The RPM Master sleep stats driver provides detailed per-subsystem 158 assess whether all the low-power modes available are entered as [all …]
|
/linux-6.12.1/Documentation/leds/ |
D | leds-class-flash.rst | 5 Some LED devices provide two modes - torch and flash. In the LED subsystem 6 those modes are supported by LED class (see Documentation/leds/leds-class.rst) 13 registered in the LED subsystem with led_classdev_flash_register function. 16 (see Documentation/ABI/testing/sysfs-class-led-flash) 18 - flash_brightness 19 - max_flash_brightness 20 - flash_timeout 21 - max_flash_timeout 22 - flash_strobe 23 - flash_fault [all …]
|
/linux-6.12.1/Documentation/devicetree/bindings/soc/qcom/ |
D | qcom,smd.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Andy Gross <agross@kernel.org> 11 - Bjorn Andersson <bjorn.andersson@linaro.org> 12 - Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> 18 Using the top-level SMD node is deprecated. Instead, the SMD edges are defined 19 directly below the device node representing the respective remote subsystem 29 "^smd-edge|rpm$": 30 $ref: /schemas/remoteproc/qcom,smd-edge.yaml# [all …]
|
/linux-6.12.1/Documentation/driver-api/surface_aggregator/ |
D | overview.rst | 1 .. SPDX-License-Identifier: GPL-2.0+ 10 its responsibilities and feature-set have since been expanded significantly 23 sensors (e.g. skin temperature) and cooling/performance-mode setting to the 27 and 2 it is required for keyboard HID input. This HID subsystem has been 32 While features have not changed much on a coarse level since the 5th 36 SAN), translating ACPI generic serial bus write-/read-accesses to SAM 40 harder to discover and requiring us to hard-code a sort of device registry. 41 Due to this, a SSAM bus and subsystem with client devices 50 communicate via HID, specifically using a HID-over-I2C device, whereas on 55 SAM-over-SSH and SAM-over-HID. [all …]
|
/linux-6.12.1/Documentation/devicetree/bindings/media/ |
D | imx.txt | 5 --------------------------- 12 - compatible : "fsl,imx-capture-subsystem"; 13 - ports : Should contain a list of phandles pointing to camera 18 capture-subsystem { 19 compatible = "fsl,imx-capture-subsystem"; 25 -------------- 27 This is the device node for the MIPI CSI-2 Receiver core in the i.MX 28 SoC. This is a Synopsys Designware MIPI CSI-2 host controller core 29 combined with a D-PHY core mixed into the same register block. In 30 addition this device consists of an i.MX-specific "CSI2IPU gasket" [all …]
|
/linux-6.12.1/drivers/staging/media/atomisp/pci/isp/kernels/ynr/ynr_2/ |
D | ia_css_ynr2.host.h | 1 /* SPDX-License-Identifier: GPL-2.0 */ 3 * Support for Intel Camera Imaging ISP subsystem. 40 unsigned int level); 45 unsigned int level); 50 unsigned int level); 55 unsigned int level);
|
/linux-6.12.1/Documentation/trace/ |
D | events.rst | 24 --------------------------------- 50 etc., and a full event name looks like this: <subsystem>:<event>. The 51 subsystem name is optional, but it is displayed in the available_events 52 file. All of the events in a subsystem can be specified via the syntax 53 ``<subsystem>:*``; for example, to enable all irq events, you can use the 59 --------------------------- 72 To enable all events in sched subsystem:: 82 - 0 - all events this file affects are disabled 83 - 1 - all events this file affects are enabled 84 - X - there is a mixture of events enabled and disabled [all …]
|
/linux-6.12.1/drivers/staging/media/atomisp/pci/isp/kernels/bnr/bnr_1.0/ |
D | ia_css_bnr.host.c | 1 // SPDX-License-Identifier: GPL-2.0 3 * Support for Intel Camera Imaging ISP subsystem. 31 to->threshold_low = in ia_css_bnr_encode() 32 uDIGIT_FITTING(from->direction, 16, SH_CSS_BAYER_BITS); in ia_css_bnr_encode() 33 to->threshold_width_log2 = uFRACTION_BITS_FITTING(8); in ia_css_bnr_encode() 34 to->threshold_width = in ia_css_bnr_encode() 35 1 << to->threshold_width_log2; in ia_css_bnr_encode() 36 to->gain_all = in ia_css_bnr_encode() 37 uDIGIT_FITTING(from->bnr_gain, 16, SH_CSS_BNR_GAIN_SHIFT); in ia_css_bnr_encode() 38 to->gain_dir = in ia_css_bnr_encode() [all …]
|
12345678910>>...34