SubSystem (full) in projects: openbmc - OpenGrok search results

Searched full:subsystem (Results 1 – 25 of 3029) sorted by relevance

/openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/linuxconsole/linuxconsole/
H A D	51-these-are-not-joysticks-rm.rules	6 SUBSYSTEM=="input", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c30a", ENV{ID_INPUT_JOYSTICK}=="?"… 7 SUBSYSTEM=="input", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c30a", KERNEL=="js[0-9]", RUN+="/b… 8 SUBSYSTEM=="input", ATTRS{idVendor}=="04d9", ATTRS{idProduct}=="a0df", ENV{ID_INPUT_JOYSTICK}=="?"… 9 SUBSYSTEM=="input", ATTRS{idVendor}=="04d9", ATTRS{idProduct}=="a0df", KERNEL=="js[0-9]", RUN+="/b… 10 SUBSYSTEM=="input", ATTRS{idVendor}=="056a", ATTRS{idProduct}=="0010", ENV{ID_INPUT_JOYSTICK}=="?"… 11 SUBSYSTEM=="input", ATTRS{idVendor}=="056a", ATTRS{idProduct}=="0010", KERNEL=="js[0-9]", RUN+="/b… 12 SUBSYSTEM=="input", ATTRS{idVendor}=="056a", ATTRS{idProduct}=="0011", ENV{ID_INPUT_JOYSTICK}=="?"… 13 SUBSYSTEM=="input", ATTRS{idVendor}=="056a", ATTRS{idProduct}=="0011", KERNEL=="js[0-9]", RUN+="/b… 14 SUBSYSTEM=="input", ATTRS{idVendor}=="056a", ATTRS{idProduct}=="0012", ENV{ID_INPUT_JOYSTICK}=="?"… 15 SUBSYSTEM=="input", ATTRS{idVendor}=="056a", ATTRS{idProduct}=="0012", KERNEL=="js[0-9]", RUN+="/b… [all …]
/openbmc/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. ``power_qos`` would be a better name. 67 The corresponding module name is ``parport_pc``, so this subsystem should also [all …]
/openbmc/linux/arch/arm/mach-pxa/
H A D	pxa3xx-regs.h	40 #define ASCR __REG(0x40f40000) /* Application Subsystem Power Status/Configuration / 41 #define ARSR __REG(0x40f40004) / Application Subsystem Reset Status / 42 #define AD3ER __REG(0x40f40008) / Application Subsystem Wake-Up from D3 Enable / 43 #define AD3SR __REG(0x40f4000c) / Application Subsystem Wake-Up from D3 Status / 44 #define AD2D0ER __REG(0x40f40010) / Application Subsystem Wake-Up from D2 to D0 Enable / 45 #define AD2D0SR __REG(0x40f40014) / Application Subsystem Wake-Up from D2 to D0 Status / 46 #define AD2D1ER __REG(0x40f40018) / Application Subsystem Wake-Up from D2 to D1 Enable / 47 #define AD2D1SR __REG(0x40f4001c) / Application Subsystem Wake-Up from D2 to D1 Status / 48 #define AD1D0ER __REG(0x40f40020) / Application Subsystem Wake-Up from D1 to D0 Enable / 49 #define AD1D0SR __REG(0x40f40024) / Application Subsystem Wake-Up from D1 to D0 Status */ [all …]
/openbmc/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 allocates a new 305 If the subsystem wants the child to be a group itself, the subsystem [all …]
/openbmc/linux/drivers/target/
H A D	Kconfig	14 subsystem logic for virtual LUN 0 access 19 tristate "TCM/IBLOCK Subsystem Plugin for Linux/BLOCK" 22 Say Y here to enable the TCM/IBLOCK subsystem plugin for non-buffered 26 tristate "TCM/FILEIO Subsystem Plugin for Linux/VFS" 28 Say Y here to enable the TCM/FILEIO subsystem plugin for buffered 32 tristate "TCM/pSCSI Subsystem Plugin for Linux/SCSI" 35 Say Y here to enable the TCM/pSCSI subsystem plugin for non-buffered 39 tristate "TCM/USER Subsystem Plugin for Linux" 42 Say Y here to enable the TCM/USER subsystem plugin for a userspace
/openbmc/linux/Documentation/admin-guide/cgroup-v1/
H A D	cgroups.rst	34 3.3 Subsystem API 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 [all …]
/openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/
H A D	PowerSubsystem.v1_1_2.json	57 "description": "Power allocation for a subsystem.", 58 …This type shall contain the set of properties describing the allocation of power for a subsystem.", 75 … "description": "The total amount of power that has been allocated or budgeted to this subsystem.", 76 …"This property shall represent the total power currently allocated or budgeted to this subsystem.", 86 …the subsystem requests, which might be higher than the current level being consumed because the re… 87 …s property shall represent the amount of power, in watt units, that the subsystem currently reques… 101 …ion": "This `PowerSubsystem schema` contains the definition for the power subsystem of a chassis.", 102 …"longDescription": "This resource shall represent a power subsystem for a Redfish implementation.", 137 "description": "Power allocation for this subsystem.", 138 …roperty shall contain the set of properties describing the allocation of power for this subsystem." [all …]
H A D	ThermalMetrics.v1_3_2.json	39 "description": "The heater metrics summary for the subsystem.", 40 …: "This type shall contain properties that describe the heater metrics summary for the subsystem.", 57 …scription": "The total number of seconds all the heaters in the thermal subsystem were active whil… 58 …hall contain the total number of seconds all the heaters in the thermal subsystem were active whil… 67 …scription": "The total number of seconds all the heaters in the thermal subsystem were active whil… 68 …hall contain the total number of seconds all the heaters in the thermal subsystem were active whil… 134 "description": "The temperature readings for a subsystem.", 135 …scription": "This type shall contain properties that describe temperature sensor for a subsystem.", 160 … "description": "The ambient temperature (in degree Celsius units) of this subsystem.", 162 …mperature, in degree Celsius units, for the ambient temperature of this subsystem. The value of t… [all …]
H A D	Storage.v1_17_1.json	140 …. This value is used for status reporting to indicate that the storage subsystem is partially loc… 159 "Disabled": "Encryption is disabled on the storage subsystem.", 160 … "PasswordOnly": "The storage subsystem uses a password, but no keys for encryption.", 161 …"PasswordWithExternalKey": "The storage subsystem uses a password and one or more external keys fo… 162 … "PasswordWithLocalKey": "The storage subsystem uses a password and a local key for encryption.", 163 … "UseExternalKey": "The storage subsystem uses one or more external keys for encryption.", 164 "UseLocalKey": "The storage subsystem uses a local key for encryption." 206 … "description": "An array of links to the chassis to which this storage subsystem is attached.", 218 "description": "The storage systems that host this storage subsystem.", 222 …mputerSystem` that represent the storage systems that host this storage subsystem. The members of… [all …]
/openbmc/bmcweb/redfish-core/schema/dmtf/json-schema-installed/
H A D	PowerSubsystem.v1_1_2.json	57 "description": "Power allocation for a subsystem.", 58 …This type shall contain the set of properties describing the allocation of power for a subsystem.", 75 … "description": "The total amount of power that has been allocated or budgeted to this subsystem.", 76 …"This property shall represent the total power currently allocated or budgeted to this subsystem.", 86 …the subsystem requests, which might be higher than the current level being consumed because the re… 87 …s property shall represent the amount of power, in watt units, that the subsystem currently reques… 101 …ion": "This `PowerSubsystem schema` contains the definition for the power subsystem of a chassis.", 102 …"longDescription": "This resource shall represent a power subsystem for a Redfish implementation.", 137 "description": "Power allocation for this subsystem.", 138 …roperty shall contain the set of properties describing the allocation of power for this subsystem." [all …]
H A D	ThermalMetrics.v1_3_2.json	39 "description": "The heater metrics summary for the subsystem.", 40 …: "This type shall contain properties that describe the heater metrics summary for the subsystem.", 57 …scription": "The total number of seconds all the heaters in the thermal subsystem were active whil… 58 …hall contain the total number of seconds all the heaters in the thermal subsystem were active whil… 67 …scription": "The total number of seconds all the heaters in the thermal subsystem were active whil… 68 …hall contain the total number of seconds all the heaters in the thermal subsystem were active whil… 134 "description": "The temperature readings for a subsystem.", 135 …scription": "This type shall contain properties that describe temperature sensor for a subsystem.", 160 … "description": "The ambient temperature (in degree Celsius units) of this subsystem.", 162 …mperature, in degree Celsius units, for the ambient temperature of this subsystem. The value of t… [all …]
H A D	Storage.v1_17_1.json	140 …. This value is used for status reporting to indicate that the storage subsystem is partially loc… 159 "Disabled": "Encryption is disabled on the storage subsystem.", 160 … "PasswordOnly": "The storage subsystem uses a password, but no keys for encryption.", 161 …"PasswordWithExternalKey": "The storage subsystem uses a password and one or more external keys fo… 162 … "PasswordWithLocalKey": "The storage subsystem uses a password and a local key for encryption.", 163 … "UseExternalKey": "The storage subsystem uses one or more external keys for encryption.", 164 "UseLocalKey": "The storage subsystem uses a local key for encryption." 206 … "description": "An array of links to the chassis to which this storage subsystem is attached.", 218 "description": "The storage systems that host this storage subsystem.", 222 …mputerSystem` that represent the storage systems that host this storage subsystem. The members of… [all …]
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Inventory/Item/
H A D	PCIeDevice.interface.yaml	`45 The Subsystem ID for this function. 49 The Subsystem Vendor ID for this function. 78 The Subsystem ID for this function. 82 The Subsystem Vendor ID for this function. 111 The Subsystem ID for this function. 115 The Subsystem Vendor ID for this function. 144 The Subsystem ID for this function. 148 The Subsystem Vendor ID for this function. 177 The Subsystem ID for this function. 181 The Subsystem Vendor ID for this function. [all …]`
/openbmc/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 operations, rio_mport structure [all …]
/openbmc/phosphor-logging/extensions/openpower-pels/registry/
H A D	message_registry.json	`5 "Subsystem": "bmc_firmware", string 27 "Subsystem": "bmc_firmware", string 48 "Subsystem": "user_error", string 64 "Subsystem": "user_error", string 81 "Subsystem": "user_error", string 98 "Subsystem": "user_error", string 114 "Subsystem": "cec_i2c", string 143 "Subsystem": "cec_i2c", string 172 "Subsystem": "cec_i2c", string 201 "Subsystem": "cec_i2c", string [all …]`
/openbmc/openbmc/poky/meta/recipes-core/systemd/systemd/
H A D	init	`81 …subsystem-nomatch=tty --subsystem-nomatch=mem --subsystem-nomatch=vc --subsystem-nomatch=vtconsole…`
/openbmc/linux/Documentation/admin-guide/
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 name. [all …]
/openbmc/openbmc/poky/meta/recipes-core/udev/eudev/
H A D	init	`98 PLATFORM_BUS_NOMATCH="--subsystem-nomatch=platform" 102 …subsystem-nomatch=tty --subsystem-nomatch=mem --subsystem-nomatch=vc --subsystem-nomatch=vtconsole…`
/openbmc/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 143 Subsystem maintainers may remove inactive maintainers from the MAINTAINERS 149 to remember to include the maintainers in discussions and subsystem [all …]
/openbmc/linux/Documentation/admin-guide/aoe/
H A D	udev.txt	3 # 8 udev manpage to see whether your udev supports SUBSYSTEM, and 4 # whether it uses one or two equal signs for SUBSYSTEM and KERNEL. 19 SUBSYSTEM=="aoe", KERNEL=="discover", NAME="etherd/%k", GROUP="disk", MODE="0220" 20 SUBSYSTEM=="aoe", KERNEL=="err", NAME="etherd/%k", GROUP="disk", MODE="0440" 21 SUBSYSTEM=="aoe", KERNEL=="interfaces", NAME="etherd/%k", GROUP="disk", MODE="0220" 22 SUBSYSTEM=="aoe", KERNEL=="revalidate", NAME="etherd/%k", GROUP="disk", MODE="0220" 23 SUBSYSTEM=="aoe", KERNEL=="flush", NAME="etherd/%k", GROUP="disk", MODE="0220"
/openbmc/obmc-console/conf/
H A D	80-obmc-console-uart.rules.in	1 SUBSYSTEM=="tty", ATTRS{iomem_base}=="0x1E787000", ENV{SYSTEMD_WANTS}="obmc-console@ttyVUART0", SYM… 2 SUBSYSTEM=="tty", ATTRS{iomem_base}=="0x1E788000", ENV{SYSTEMD_WANTS}="obmc-console@ttyVUART1", SYM… 3 SUBSYSTEM=="tty", ATTRS{iomem_base}=="0x1E783000", ENV{SYSTEMD_WANTS}="obmc-console@ttyS0", TAG+="s… 4 SUBSYSTEM=="tty", ATTRS{iomem_base}=="0x1E78D000", ENV{SYSTEMD_WANTS}="obmc-console@ttyS1", TAG+="s… 5 SUBSYSTEM=="tty", ATTRS{iomem_base}=="0x1E78E000", ENV{SYSTEMD_WANTS}="obmc-console@ttyS2", TAG+="s… 6 SUBSYSTEM=="tty", ATTRS{iomem_base}=="0x1E78F000", ENV{SYSTEMD_WANTS}="obmc-console@ttyS3", TAG+="s…
/openbmc/linux/samples/configfs/
H A D	configfs_sample.c	22 * This first example is a childless subsystem. It cannot create 26 * This is not necessary if a subsystem has no attributes directly 27 * on the subsystem. See the next example, 02-simple-children, for 28 * such a subsystem. 77 "The childless subsystem is the simplest possible subsystem in\n" in childless_description_show() 118 * subsystem, as it has no attributes of its own. 202 "This subsystem allows the creation of child config_items. These\n" in simple_children_description_show() 252 * the simple_children group is not the subsystem itself, it is a 253 * child of the subsystem. Creation of a group in the subsystem creates 280 "This subsystem allows the creation of child config_groups. These\n" in group_children_description_show() [all …]
/openbmc/linux/drivers/remoteproc/
H A D	qcom_common.c	53 * struct minidump_subsystem - Subsystem's SMEM Table of content 54 * @status : Subsystem toc init status 56 * @encryption_status: Encryption status for this subsystem 57 * @encryption_required : Decides to encrypt the subsystem regions or not 58 * @region_count : Number of regions added in this subsystem toc 59 * @regions_baseptr : regions base pointer of the subsystem 104 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 [all …]
/openbmc/linux/Documentation/driver-api/media/
H A D	maintainer-entry-profile.rst	1 Media Subsystem Profile 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 [all …]
/openbmc/linux/drivers/pinctrl/qcom/
H A D	Kconfig	59 Qualcomm Technologies Inc LPASS (Low Power Audio SubSystem) LPI 68 Qualcomm Technologies Inc LPASS (Low Power Audio SubSystem) LPI 77 Qualcomm Technologies Inc LPASS (Low Power Audio SubSystem) LPI 86 Qualcomm Technologies Inc LPASS (Low Power Audio SubSystem) LPI 95 Qualcomm Technologies Inc LPASS (Low Power Audio SubSystem) LPI 105 Qualcomm Technologies Inc LPASS (Low Power Audio SubSystem) LPI 114 Qualcomm Technologies Inc LPASS (Low Power Audio SubSystem) LPI 123 Qualcomm Technologies Inc LPASS (Low Power Audio SubSystem) LPI

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

Project(s)

Full Search
Definition
Symbol
File Path
History
Type