Home
last modified time | relevance | path

Searched +full:subsystem +full:- +full:level (Results 1 – 25 of 210) sorted by relevance

123456789

/Documentation/driver-api/fpga/
Dintro.rst4 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 …]
/Documentation/scsi/
Dscsi.rst1 .. 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 …]
Dscsi_mid_low_api.rst1 .. 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 …]
/Documentation/networking/
Dnfc.rst2 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 …]
/Documentation/power/
Druntime_pm.rst5 (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 …]
/Documentation/core-api/
Dprintk-index.rst1 .. 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 …]
Dgenericirq.rst7 :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 …]
/Documentation/maintainer/
Dmaintainer-entry-profile.rst6 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 …]
Drebasing-and-merging.rst1 .. 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 …]
/Documentation/w1/
Dw1-generic.rst2 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 …]
/Documentation/netlabel/
Dlsm_interface.rst25 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.
/Documentation/power/powercap/
Dpowercap.rst13 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 …]
/Documentation/devicetree/bindings/soc/qcom/
Dqcom,smd.yaml1 # 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 …]
/Documentation/userspace-api/media/dvb/
Dfe-set-voltage.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
13 FE_SET_VOLTAGE - Allow setting the DC level sent to the antenna subsystem.
34 This ioctl allows to set the DC voltage level sent through the antenna
40 LNBf can controlled by the voltage level. Other devices (for example,
42 control the voltage level, provided that either 13V or 18V is sent to
46 setting a voltage level may interfere on other devices, as they may lose
56 On error -1 is returned, and the ``errno`` variable is set
60 :ref:`Generic Error Codes <gen-errors>` chapter.
/Documentation/admin-guide/
Dsysfs-rules.rst4 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 …]
Dthunderbolt.rst1 .. 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 …]
/Documentation/leds/
Dleds-class-flash.rst5 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 …]
/Documentation/mm/
Dindex.rst5 This is a guide to understanding the memory management subsystem
8 see the :doc:`admin guide <../admin-guide/mm/index>`.
31 (MM) subsystem internals with different level of details ranging from notes and
40 allocation-profiling
49 memory-model
53 overcommit-accounting
62 unevictable-lru
63 vmalloced-kernel-stacks
/Documentation/devicetree/bindings/media/
Dimx.txt5 ---------------------------
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 …]
/Documentation/driver-api/surface_aggregator/
Doverview.rst1 .. 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 …]
/Documentation/process/
Dmaintainer-soc.rst1 .. 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 …]
/Documentation/dev-tools/kunit/
Dstyle.rst1 .. SPDX-License-Identifier: GPL-2.0
17 example, non-deterministically producing false positives or negatives, or
24 suite is a group of tests which test a related area of the kernel. A subsystem
25 is a set of test suites which test different parts of a kernel subsystem
29 ----------
31 Every test suite must belong to a subsystem. A subsystem is a collection of one
33 test subsystem should match a single kernel module. If the code being tested
34 cannot be compiled as a module, in many cases the subsystem should correspond to
42 If a test subsystem name has multiple components, they should be separated by
43 underscores. *Do not* include "test" or "kunit" directly in the subsystem name
[all …]
/Documentation/driver-api/rapidio/
Dmport_cdev.rst2 RapidIO subsystem mport character device driver (rio_mport_cdev.c)
16 This driver (MPORT_CDEV) provides access to basic RapidIO subsystem operations
17 for user-space applications. Most of RapidIO operations are supported through
24 Using available set of ioctl commands user-space applications can perform
25 following RapidIO bus and subsystem operations:
27 - Reads and writes from/to configuration registers of mport devices
29 - Reads and writes from/to configuration registers of remote RapidIO devices.
32 - Set RapidIO Destination ID for mport devices (RIO_MPORT_MAINT_HDID_SET)
33 - Set RapidIO Component Tag for mport devices (RIO_MPORT_MAINT_COMPTAG_SET)
34 - Query logical index of mport devices (RIO_MPORT_MAINT_PORT_IDX_GET)
[all …]
/Documentation/driver-api/hte/
Dhte.rst1 .. SPDX-License-Identifier: GPL-2.0+
10 ------------
25 ----------------------------------------
27 .. kernel-doc:: drivers/hte/hte.c
31 ----------------------------------------
33 .. kernel-doc:: drivers/hte/hte.c
37 -----------------------------------
38 .. kernel-doc:: include/linux/hte.h
41 ------------------------------
47 - Monitors GPIO line change.
[all …]
/Documentation/devicetree/bindings/display/ti/
Dti,k2g-dss.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
4 ---
5 $id: http://devicetree.org/schemas/display/ti/ti,k2g-dss.yaml#
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
8 title: Texas Instruments K2G Display Subsystem
11 - Jyri Sarha <jsarha@ti.com>
12 - Tomi Valkeinen <tomi.valkeinen@ti.com>
15 The K2G DSS is an ultra-light version of TI Keystone Display
16 SubSystem. It has only one output port and video plane. The
21 const: ti,k2g-dss
[all …]

123456789