Home
last modified time | relevance | path

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

12345678910>>...35

/openbmc/openbmc/poky/meta/recipes-core/systemd/systemd/
H A Dinit81 …subsystem-nomatch=tty --subsystem-nomatch=mem --subsystem-nomatch=vc --subsystem-nomatch=vtconsole…
/openbmc/openbmc/poky/meta/recipes-core/udev/eudev/
H A Dinit102 …subsystem-nomatch=tty --subsystem-nomatch=mem --subsystem-nomatch=vc --subsystem-nomatch=vtconsole…
/openbmc/linux/sound/pci/emu10k1/
H A Demu10k1_main.c1004 {.vendor = 0x1102, .device = 0x0008, .subsystem = 0x10241102,
1050 {.vendor = 0x1102, .device = 0x0008, .subsystem = 0x10211102,
1077 {.vendor = 0x1102, .device = 0x0008, .subsystem = 0x10011102,
1116 {.vendor = 0x1102, .device = 0x0008, .subsystem = 0x20011102,
1129 {.vendor = 0x1102, .device = 0x0008, .subsystem = 0x42011102,
1142 {.vendor = 0x1102, .device = 0x0008, .subsystem = 0x40041102,
1156 {.vendor = 0x1102, .device = 0x0008, .subsystem = 0x40071102,
1168 {.vendor = 0x1102, .device = 0x0004, .subsystem = 0x40011102,
1178 {.vendor = 0x1102, .device = 0x0008, .subsystem = 0x40021102,
1189 {.vendor = 0x1102, .device = 0x0004, .subsystem = 0x40021102,
[all …]
/openbmc/linux/Documentation/dev-tools/kunit/
H A Dstyle.rst24 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. ``power_qos`` would be a better name.
67 The corresponding module name is ``parport_pc``, so this subsystem should also
[all …]
/openbmc/phosphor-logging/test/openpower-pels/
H A Duser_header_test.cpp47 EXPECT_EQ(uh.subsystem(), 0x10); in TEST()
108 regEntry.subsystem = 5; in TEST()
128 EXPECT_EQ(uh.subsystem(), 5); in TEST()
153 regEntry.subsystem = 5; in TEST()
199 regEntry.subsystem = 5; in TEST()
221 regEntry.subsystem = 5; in TEST()
243 regEntry.subsystem = 5; in TEST()
266 regEntry.subsystem = 5; in TEST()
288 regEntry.subsystem = 5; in TEST()
322 regEntry.subsystem = 5; in TEST()
[all …]
/openbmc/linux/Documentation/filesystems/
H A Dconfigfs.rst50 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 allocates a new
305 If the subsystem wants the child to be a group itself, the subsystem
[all …]
/openbmc/qemu/scripts/
H A Dget_maintainer.pl47 my $subsystem = 0;
193 'subsystem!' => \$subsystem,
232 $subsystem = 0;
237 my $selections = $email + $scm + $status + $subsystem + $web;
461 my @subsystem = ();
483 if ($subsystem) {
484 @subsystem = uniq(@subsystem);
485 output(@subsystem);
539 @subsystem = ();
906 my $subsystem = $typevalue[$start];
[all …]
/openbmc/linux/Documentation/admin-guide/
H A Dvideo-output.rst17 | |-- subsystem -> ../../../class/video_output
22 | |-- subsystem -> ../../../class/video_output
27 | |-- subsystem -> ../../../class/video_output
32 |-- subsystem -> ../../../class/video_output
H A Dsysfs-rules.rst68 - 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 name.
[all …]
/openbmc/linux/Documentation/doc-guide/
H A Dmaintainer-profile.rst3 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.
41 I am the sole maintainer for the documentation subsystem, and I am doing
/openbmc/linux/Documentation/driver-api/rapidio/
H A Drapidio.rst10 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 operations, rio_mport structure
[all …]
/openbmc/linux/drivers/remoteproc/
H A Dqcom_common.c104 static int qcom_add_minidump_segments(struct rproc *rproc, struct minidump_subsystem *subsystem, in qcom_add_minidump_segments() argument
120 seg_cnt = le32_to_cpu(subsystem->region_count); in qcom_add_minidump_segments()
121 ptr = ioremap((unsigned long)le64_to_cpu(subsystem->regions_baseptr), in qcom_add_minidump_segments()
150 struct minidump_subsystem *subsystem; in qcom_minidump() local
163 subsystem = &toc->subsystems[minidump_id]; in qcom_minidump()
169 if (subsystem->regions_baseptr == 0 || in qcom_minidump()
170 le32_to_cpu(subsystem->status) != 1 || in qcom_minidump()
171 le32_to_cpu(subsystem->enabled) != MINIDUMP_SS_ENABLED) { in qcom_minidump()
175 if (le32_to_cpu(subsystem->encryption_status) != MINIDUMP_SS_ENCR_DONE) { in qcom_minidump()
186 ret = qcom_add_minidump_segments(rproc, subsystem, rproc_dumpfn_t); in qcom_minidump()
/openbmc/openpower-hw-diags/attn/
H A Dattn_logging.cpp116 uint8_t subsystem; in createPelCustom() local
121 subsystem = std::stoi(it->second); in createPelCustom()
122 tiPel->setSubsystem(subsystem); in createPelCustom()
148 if (static_cast<uint8_t>(pel::SubsystemID::hypervisor) == subsystem) in createPelCustom()
394 uint8_t subsystem; in event() local
399 subsystem = std::stoi(it->second); in event()
414 if (static_cast<uint8_t>(pel::SubsystemID::hypervisor) != subsystem) in event()
447 uint8_t subsystem; in eventTerminate() local
452 subsystem = std::stoi(it->second); in eventTerminate()
465 if (static_cast<uint8_t>(pel::SubsystemID::hypervisor) == subsystem) in eventTerminate()
/openbmc/linux/drivers/target/
H A DKconfig14 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
/openbmc/qemu/scripts/kvm/
H A Dkvm_flightrecorder46 def enable_event(subsystem, event, enable): argument
47 write_file(trace_path('events', subsystem, event, 'enable'), '1' if enable else '0')
49 def enable_subsystem(subsystem, enable): argument
50 write_file(trace_path('events', subsystem, 'enable'), '1' if enable else '0')
/openbmc/linux/Documentation/driver-api/fpga/
H A 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
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
/openbmc/qemu/docs/system/s390x/
H A Dcss.rst1 The virtual channel subsystem
4 QEMU implements a virtual channel subsystem with subchannels, (mostly
12 The default channel subsystem image id (``<cssid>``) is ``0xfe``. Devices in
13 there will show up in channel subsystem image ``0`` to guests that do not
69 * a virtio-mouse device in a non-standard channel subsystem image::
78 * a virtio-keyboard device in another non-standard channel subsystem image::
83 the standard channel subsystem image id.
/openbmc/linux/Documentation/driver-api/media/
H A Dmaintainer-entry-profile.rst7 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 are:
[all …]
/openbmc/linux/Documentation/admin-guide/cgroup-v1/
H A Dcgroups.rst53 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 names and the cgroup name
[all …]
/openbmc/linux/scripts/
H A Dget_maintainer.pl56 my $subsystem = 0;
267 'subsystem!' => \$subsystem,
318 $subsystem = 0;
323 my $selections = $email + $scm + $status + $subsystem + $web;
632 my @subsystem = ();
653 if ($subsystem) {
654 @subsystem = uniq(@subsystem);
655 output(@subsystem);
848 @subsystem = ();
1254 my $subsystem = $typevalue[$start];
[all …]
/openbmc/u-boot/scripts/
H A Dget_maintainer.pl52 my $subsystem = 0;
253 'subsystem!' => \$subsystem,
302 $subsystem = 0;
307 my $selections = $email + $scm + $status + $subsystem + $web;
581 my @subsystem = ();
603 if ($subsystem) {
604 @subsystem = uniq(@subsystem);
605 output(@subsystem);
798 @subsystem = ();
1194 my $subsystem = $typevalue[$start];
[all …]
/openbmc/u-boot/drivers/ram/
H A DKconfig15 The RAM subsystem adds a small amount of overhead to the image.
24 The RAM subsystem adds a small amount of overhead to the image.
50 K3 based AM654 devices has DDR memory subsystem that comprises
52 intergrate these blocks into the device. This DDR subsystem
55 SDRAM devices connected to DDR subsystem.
/openbmc/linux/Documentation/leds/
H A Dleds-class-flash.rst5 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
/openbmc/linux/sound/pci/ctxfi/
H A Dxfi.c32 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()
/openbmc/linux/Documentation/mm/damon/
H A Dmaintainer-profile.rst6 The DAMON subsystem covers the files that are listed in 'DATA ACCESS MONITOR'
9 The mailing lists for the subsystem are damon@lists.linux.dev and
19 management subsystem maintainer. After more sufficient tests, the patches will
21 memory management subsystem maintainer.
45 mm-stable[3] trees depend on the memory management subsystem maintainer.

12345678910>>...35