subsystem (reference) in projects: linux-6.12

Searched refs:subsystem (Results 1 – 25 of 672) sorted by relevance

/linux/sound/pci/emu10k1/
H A D	emu10k1_main.c	945 {.vendor = 0x1102, .device = 0x0008, .subsystem = 0x10241102, 991 {.vendor = 0x1102, .device = 0x0008, .subsystem = 0x10211102, 1018 {.vendor = 0x1102, .device = 0x0008, .subsystem = 0x10011102, 1057 {.vendor = 0x1102, .device = 0x0008, .subsystem = 0x20011102, 1070 {.vendor = 0x1102, .device = 0x0008, .subsystem = 0x42011102, 1083 {.vendor = 0x1102, .device = 0x0008, .subsystem = 0x40041102, 1097 {.vendor = 0x1102, .device = 0x0008, .subsystem = 0x40071102, 1109 {.vendor = 0x1102, .device = 0x0004, .subsystem = 0x40011102, 1119 {.vendor = 0x1102, .device = 0x0008, .subsystem = 0x40021102, 1130 {.vendor = 0x1102, .device = 0x0004, .subsystem 1469 snd_emu10k1_create(struct snd_card * card,struct pci_dev * pci,unsigned short extin_mask,unsigned short extout_mask,long max_cache_bytes,int enable_ir,uint subsystem) snd_emu10k1_create() argument [all...]
/linux/Documentation/dev-tools/kunit/
H A D	style.rst	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 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 64 suffix. ``qos`` is also ambiguous as a subsystem name, because several parts 65 of the kernel have a ``qos`` subsystem [all...]
/linux/Documentation/filesystems/
H A D	configfs.rst	50 subsystems. Once a client subsystem is loaded, it will appear as a 122 object in the subsystem. It has attributes that match values on that 124 and its attributes, allowing the subsystem to ignore all but the 132 A subsystem is the top level of a client module. During initialization, 133 the client module registers the subsystem with configfs, the subsystem 135 subsystem is also a config_group, and can do everything a config_group 162 structure that actually represents what the subsystem is doing. The 176 Usually a subsystem wants the item to display and/or store attributes, 300 mkdir(2) in the group's directory. The subsystem allocate [all...]
/linux/Documentation/admin-guide/
H A D	video-output.rst	`17 \| \|-- subsystem -> ../../../class/video_output 22 \| \|-- subsystem -> ../../../class/video_output 27 \| \|-- subsystem -> ../../../class/video_output 32 \|-- subsystem -> ../../../class/video_output`
H A D	sysfs-rules.rst	68 - subsystem (``block``, ``tty``, ``pci``, ...) 71 - retrieved by reading the "subsystem"-link and using only the 108 - Classification by subsystem 115 classification directories into one place at ``/sys/subsystem``, 117 classes, including the converted block subsystem, will show up 119 The devices belonging to a subsystem will create a symlink in the 120 "devices" directory at ``/sys/subsystem/<name>/devices``, 122 If ``/sys/subsystem`` exists, ``/sys/bus``, ``/sys/class`` and ``/sys/block`` 124 places, as the kernel is free to move a subsystem from one place to 126 subsystem nam [all...]
H A D	rapidio.rst	`18 subsystem internals. 39 subsystem to gather info on devices, request/map memory region 58 subsystem. 96 The following people have contributed to the RapidIO subsystem directly`
/linux/Documentation/driver-api/rapidio/
H A D	rapidio.rst	10 This document describes the basics of the Linux RapidIO subsystem and provides 16 Because the RapidIO subsystem follows the Linux device model it is integrated 20 The Linux RapidIO subsystem is architecture independent and therefore defines 22 subsystem operations. 28 Each of these components is represented in the subsystem by an associated data 29 structure. The core logical components of the RapidIO subsystem are defined 37 packets (transactions). In the RapidIO subsystem each master port is represented 43 RapidIO master ports are serviced by subsystem specific mport device drivers 44 that provide functionality defined for this subsystem. To provide a hardware 45 independent interface for RapidIO subsystem operation [all...]
H A D	mport_cdev.rst	`2 RapidIO subsystem mport character device driver (rio_mport_cdev.c) 16 This driver (MPORT_CDEV) provides access to basic RapidIO subsystem operations 25 following RapidIO bus and subsystem operations: 56 - Manage device objects supported by RapidIO subsystem (RIO_DEV_ADD/RIO_DEV_DEL). 59 kernel RapidIO subsystem. 64 This device driver uses standard interfaces defined by kernel RapidIO subsystem 66 subsystem with limitations set by available mport implementation.`
/linux/drivers/target/
H A D	Kconfig	`14 subsystem logic for virtual LUN 0 access 22 Say Y here to enable the TCM/IBLOCK subsystem plugin for non-buffered 28 Say Y here to enable the TCM/FILEIO subsystem plugin for buffered 35 Say Y here to enable the TCM/pSCSI subsystem plugin for non-buffered 42 Say Y here to enable the TCM/USER subsystem plugin for a userspace`
/linux/Documentation/driver-api/fpga/
H A 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 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 40 of an FPGA. This subsystem includes fpga-bridge.c and the low level`
/linux/Documentation/doc-guide/
H A D	maintainer-profile.rst	`3 Documentation subsystem maintainer entry profile 6 The documentation "subsystem" is the central coordinating point for the 12 It's worth noting, though, that the boundaries of this subsystem are rather 13 fuzzier than normal. Many other subsystem maintainers like to keep control 17 always) maintained by the relevant subsystem maintainer. 48 I am the sole maintainer for the documentation subsystem, and I am doing`
/linux/Documentation/driver-api/media/
H A D	maintainer-entry-profile.rst	7 The media subsystem covers support for a variety of devices: stream 24 by them before being merged via the media subsystem's development 29 add new features to the subsystem must also bring changes to the 32 Due to the size and wide scope of the media subsystem, media's 34 knowledge of a specific aspect of the subsystem. It is the sub-maintainers' 36 following the subsystem rules and are properly using the media kernel and 39 Patches for the media subsystem must be sent to the media mailing list 66 At the media subsystem, we have a group of senior developers that 69 subsystem as a whole. For core changes, whenever possible, multiple 72 The media maintainers that work on specific areas of the subsystem ar [all...]
/linux/Documentation/admin-guide/cgroup-v1/
H A D	cgroups.rst	53 A subsystem is a module that makes use of the task grouping 55 particular ways. A subsystem is typically a "resource controller" that 58 virtualization subsystem. 62 hierarchy, and a set of subsystems; each subsystem has system-specific 109 At one extreme, each resource controller or subsystem could be in a 181 cgroup_subsys_state objects, one for each cgroup subsystem 186 subsystem state is something that's expected to happen frequently 219 It's not currently possible to bind a new subsystem to an active 220 cgroup hierarchy, or to unbind a subsystem from an active cgroup 233 for each active hierarchy, the subsystem name [all...]
/linux/drivers/remoteproc/
H A D	qcom_common.c	58 * @encryption_status: Encryption status for this subsystem 59 * @encryption_required : Decides to encrypt the subsystem regions or not 60 * @region_count : Number of regions added in this subsystem toc 61 * @regions_baseptr : regions base pointer of the subsystem 106 static int qcom_add_minidump_segments(struct rproc rproc, struct minidump_subsystem subsystem, in qcom_add_minidump_segments() argument 122 seg_cnt = le32_to_cpu(subsystem->region_count); in qcom_add_minidump_segments() 123 ptr = ioremap((unsigned long)le64_to_cpu(subsystem->regions_baseptr), in qcom_add_minidump_segments() 152 struct minidump_subsystem subsystem; in qcom_minidump() local 164 / Get subsystem table of contents using the minidump id */ in qcom_minidump() 165 subsystem in qcom_minidump() [all...]
/linux/scripts/
H A D	get_maintainer.pl	`59 my $subsystem = 0; 271 'subsystem!' => \$subsystem, 329 $subsystem = 0; 336 my $selections = $email + $scm + $status + $subsystem + $web + $bug; 338 die "$P: Missing required option: email, scm, status, subsystem, web or bug\n"; 644 my @subsystem = (); 671 if ($subsystem) { 672 @subsystem = uniq(@subsystem); [all...]`
/linux/sound/pci/ctxfi/
H A D	xfi.c	`32 static unsigned int subsystem[SNDRV_CARDS]; variable 40 module_param_array(subsystem, int, NULL, 0444); 41 MODULE_PARM_DESC(subsystem, "Override subsystem ID for Creative X-Fi driver"); 90 pci_id->driver_data, subsystem[dev], &atc); in ct_card_probe()`
/linux/Documentation/leds/
H A D	leds-class-flash.rst	`5 Some LED devices provide two modes - torch and flash. In the LED subsystem 13 registered in the LED subsystem with led_classdev_flash_register function. 29 A LED subsystem driver can be controlled also from the level of VideoForLinux2 30 subsystem. In order to enable this CONFIG_V4L2_FLASH_LED_CLASS symbol has to 34 V4L2 subsystem. The function takes six arguments: 88 Opening the V4L2 flash sub-device makes the LED subsystem sysfs interface`
/linux/net/bluetooth/
H A D	Kconfig	`3 # Bluetooth subsystem configuration 7 tristate "Bluetooth subsystem support" 26 Linux Bluetooth subsystem consist of several layers: 42 To use Linux Bluetooth subsystem, you will need several user-space 125 Run self tests when initializing the Bluetooth subsystem. This 129 When the Bluetooth subsystem is built as module, then the test 131 subsystem is compiled into the kernel image, then the test cases`
/linux/Documentation/nvme/
H A D	nvme-pci-endpoint-target.rst	19 subsystem using a port. The port transfer type must be configured to be 20 "pci". The subsystem can be configured to have namespaces backed by regular 154 as a subsystem namespace can be used. 181 subsystem and port must be defined. Second, the NVMe PCI endpoint device must 182 be setup and bound to the subsystem and port created. 187 Details about how to configure an NVMe target subsystem and port are outside the 189 and subsystem with a single namespace backed by a null_blk device. 210 Now, create a subsystem and a port that we will use to create a PCI target 222 Next, create and enable the subsystem namespace using the null_blk block 229 Finally, create the target port and link it to the subsystem [all...]
/linux/Documentation/driver-api/usb/
H A D	hotplug.rst	45 The /sbin/hotplug program can be invoked by any subsystem as part of its 46 reaction to a configuration change, from a thread in that subsystem. 47 Only one parameter is required: the name of a subsystem being notified of 50 the subsystem making that invocation. 62 The USB subsystem currently invokes ``/sbin/hotplug`` when USB devices 122 Most USB device drivers should pass these tables to the USB subsystem as 123 well as to the module management subsystem. Not all, though: some driver 127 Drivers that connect directly to the USB subsystem should be declared 145 When the USB subsystem knows about a driver's device ID table, it's used when
H A D	writing_usb_driver.rst	12 The Linux USB subsystem has grown from supporting only two different 44 excellent introduction to the Linux USB subsystem can be found at the 46 subsystem is structured and introduces the reader to the concept of USB 50 the Linux USB subsystem, giving it some information about which devices 53 information is passed to the USB subsystem in the :c:type:`usb_driver` 76 another kernel subsystem, such as the SCSI, network or TTY subsystem. 78 subsystem, and any user-space interactions are provided through that 79 interface. But for drivers that do not have a matching kernel subsystem, 81 is needed. The USB subsystem provide [all...]
/linux/Documentation/devicetree/bindings/display/
H A D	st,stih4xx.txt	`21 - sti-display-subsystem: Master device for DRM sub-components 25 - compatible: "st,sti-display-subsystem" 29 must be a child of sti-display-subsystem 45 must be a child of sti-display-subsystem 57 must be a child of sti-display-subsystem 74 must be a child of sti-display-subsystem 87 must be a child of sti-display-subsystem 102 must be a child of sti-display-subsystem 175 sti-display-subsystem { 176 compatible = "st,sti-display-subsystem"; [all...]`
/linux/Documentation/maintainer/
H A D	feature-and-driver-maintainers.rst	17 subsystem. 28 a subsystem could well have a hundred such drivers. Subsystem 31 The exact expectations on the response time will vary by subsystem. 32 The patch review SLA the subsystem had set for itself can sometimes 33 be found in the subsystem documentation. Failing that as a rule of thumb 35 review delay of the subsystem maintainer. The resulting expectations 43 Maintainers must be subscribed and follow the appropriate subsystem-wide 63 than the expected review timeline for the subsystem, maintainer should 90 should be conducted in a manner typical for the larger subsystem. 160 to remember to include the maintainers in discussions and subsystem [all...]
/linux/drivers/gpu/drm/
H A D	Kconfig.debug	`15 bool "Compile the drm subsystem with warnings as errors" 21 enables the '-Werror' flag to enforce that rule in the drm subsystem. 23 The drm subsystem enables more warnings than the kernel default, so 33 Ensure the DRM subsystem headers both under drivers/gpu/drm and 97 Enables unit tests for TTM, a GPU memory manager subsystem used`
/linux/Documentation/admin-guide/media/
H A D	index.rst	`6 Media subsystem admin and user guide 9 This section contains usage information about media subsystem and 26 subsystem`

12 3 4 5 6 7 8 9 10 >>...27

Project(s)

Full Search
Definition
Symbol
File Path
History
Type