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

Searched full:subsystem (Results 1 – 25 of 3093) 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/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/bmcweb/redfish-core/schema/dmtf/json-schema/
H A D	PowerSubsystem.v1_1_3.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 when it represents a subset of the power infra… 138 …ntain the set of properties describing the allocation of power for this subsystem as part of the p… [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_19_0.json	143 …. This value is used for status reporting to indicate that the storage subsystem is partially loc… 162 "Disabled": "Encryption is disabled on the storage subsystem.", 163 … "PasswordOnly": "The storage subsystem uses a password, but no keys for encryption.", 164 …"PasswordWithExternalKey": "The storage subsystem uses a password and one or more external keys fo… 165 … "PasswordWithLocalKey": "The storage subsystem uses a password and a local key for encryption.", 166 … "UseExternalKey": "The storage subsystem uses one or more external keys for encryption.", 167 "UseLocalKey": "The storage subsystem uses a local key for encryption." 259 …"description": "The set of drives in this storage subsystem that do not support blocking of TCG-de… 263 … to resources of type `Drive` that represent the drives in this storage subsystem that do not supp… 272 …"description": "The set of drives in this storage subsystem for which the most recent attempt to b… [all …]
/openbmc/bmcweb/redfish-core/schema/dmtf/json-schema-installed/
H A D	PowerSubsystem.v1_1_3.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 when it represents a subset of the power infra… 138 …ntain the set of properties describing the allocation of power for this subsystem as part of the p… [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_19_0.json	143 …. This value is used for status reporting to indicate that the storage subsystem is partially loc… 162 "Disabled": "Encryption is disabled on the storage subsystem.", 163 … "PasswordOnly": "The storage subsystem uses a password, but no keys for encryption.", 164 …"PasswordWithExternalKey": "The storage subsystem uses a password and one or more external keys fo… 165 … "PasswordWithLocalKey": "The storage subsystem uses a password and a local key for encryption.", 166 … "UseExternalKey": "The storage subsystem uses one or more external keys for encryption.", 167 "UseLocalKey": "The storage subsystem uses a local key for encryption." 259 …"description": "The set of drives in this storage subsystem that do not support blocking of TCG-de… 263 … to resources of type `Drive` that represent the drives in this storage subsystem that do not supp… 272 …"description": "The set of drives in this storage subsystem for which the most recent attempt to b… [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" string 230 "Subsystem": "bmc_firmware", global() string 257 "Subsystem": "user_error", global() string 284 "Subsystem": "bmc_firmware", global() string 308 "Subsystem": "bmc_firmware", global() string 332 "Subsystem": "bmc_firmware", global() string 356 "Subsystem": "bmc_firmware", global() string 391 "Subsystem": "platform_firmware", global() string 446 "Subsystem": "platform_firmware", global() string 471 "Subsystem": "other_na", global() string 509 "Subsystem": "bmc_firmware", global() string 536 "Subsystem": "bmc_firmware", global() string 556 "Subsystem": "bmc_firmware", global() string 590 "Subsystem": "cec_hardware", global() string 609 "Subsystem": "cec_hardware", global() string 630 "Subsystem": "cec_hardware", global() string 648 "Subsystem": "cec_hardware", global() string 666 "Subsystem": "cec_sp_hyp_iface", global() string 689 "Subsystem": "cec_hardware", global() string 707 "Subsystem": "cec_hardware", global() string 729 "Subsystem": "cec_hardware", global() string 756 "Subsystem": "cec_hardware", global() string 806 "Subsystem": "cec_clocks", global() string 827 "Subsystem": "bmc_firmware", global() string 855 "Subsystem": "cec_chip_iface", global() string 880 "Subsystem": "bmc_firmware", global() string 912 "Subsystem": "processor_chip", global() string 941 "Subsystem": "cec_chip_iface", global() string 965 "Subsystem": "cec_chip_iface", global() string 987 "Subsystem": "bmc_firmware", global() string 1018 "Subsystem": "cec_hardware", global() string 1038 "Subsystem": "bmc_firmware", global() string 1058 "Subsystem": "bmc_firmware", global() string 1078 "Subsystem": "cec_hardware", global() string 1118 "Subsystem": "cec_sp_hostboot_iface", global() string 1143 "Subsystem": "input_power_source", global() string 1176 "Subsystem": "cec_op_panel", global() string 1195 "Subsystem": "bmc_firmware", global() string 1230 "Subsystem": "bmc_firmware", global() string 1260 "Subsystem": "bmc_firmware", global() string 1294 "Subsystem": "bmc_firmware", global() string 1328 "Subsystem": "bmc_firmware", global() string 1362 "Subsystem": "bmc_firmware", global() string 1396 "Subsystem": "bmc_firmware", global() string 1430 "Subsystem": "bmc_firmware", global() string 1464 "Subsystem": "bmc_firmware", global() string 1498 "Subsystem": "bmc_firmware", global() string 1532 "Subsystem": "bmc_firmware", global() string 1565 "Subsystem": "bmc_firmware", global() string 1596 "Subsystem": "bmc_firmware", global() string 1616 "Subsystem": "processor_chip", global() string 1643 "Subsystem": "processor_chip", global() string 1679 "Subsystem": "processor_chip", global() string 1705 "Subsystem": "processor_chip", global() string 1733 "Subsystem": "processor_chip", global() string 1794 "Subsystem": "processor_chip", global() string 1820 "Subsystem": "cec_hardware", global() string 1849 "Subsystem": "bmc_firmware", global() string 1871 "Subsystem": "processor_chip", global() string 2020 "Subsystem": "power_supply", global() string 2078 "Subsystem": "power_supply", global() string 2132 "Subsystem": "power_supply", global() string 2185 "Subsystem": "power_supply", global() string 2243 "Subsystem": "power_supply", global() string 2296 "Subsystem": "power_supply", global() string 2334 "Subsystem": "power_supply", global() string 2392 "Subsystem": "power_supply", global() string 2439 "Subsystem": "power_supply", global() string 2493 "Subsystem": "power_supply", global() string 2540 "Subsystem": "power", global() string 2591 "Subsystem": "power_supply", global() string 2639 "Subsystem": "power_sequencer", global() string 2690 "Subsystem": "power_control_hw", global() string 2772 "Subsystem": "power_sequencer", global() string 2815 "Subsystem": "power_sequencer", global() string 3791 "Subsystem": "power", global() string 3815 "Subsystem": "power", global() string 3841 "Subsystem": "power", global() string 3869 "Subsystem": "power", global() string 3889 "Subsystem": "power", global() string 3909 "Subsystem": "power", global() string 3938 "Subsystem": "power", global() string 3970 "Subsystem": "power_sequencer", global() string 4019 "Subsystem": "power_sequencer", global() string 4069 "Subsystem": "power_sequencer", global() string 4119 "Subsystem": "power", global() string 4148 "Subsystem": "cec_i2c", global() string 4173 "Subsystem": "power", global() string 4198 "Subsystem": "power", global() string 4223 "Subsystem": "power_fans", global() string 4249 "Subsystem": "power_fans", global() string 4323 "Subsystem": "power_fans", global() string 4367 "Subsystem": "power_fans", global() string 4423 "Subsystem": "power_fans", global() string 4477 "Subsystem": "power", global() string 4530 "Subsystem": "power", global() string 4572 "Subsystem": "power", global() string 4625 "Subsystem": "power", global() string 4667 "Subsystem": "power", global() string 4720 "Subsystem": "power", global() string 4762 "Subsystem": "power", global() string 4795 "Subsystem": "power", global() string 4825 "Subsystem": "power", global() string 4857 "Subsystem": "ext_env", global() string 4898 "Subsystem": "ext_env", global() string 4921 "Subsystem": "cec_tod", global() string 4939 "Subsystem": "cec_tod", global() string 4957 "Subsystem": "power", global() string 4979 "Subsystem": "power", global() string 5001 "Subsystem": "power", global() string 5023 "Subsystem": "power", global() string 5045 "Subsystem": "cec_vpd", global() string 5071 "Subsystem": "cec_vpd", global() string 5093 "Subsystem": "cec_vpd", global() string 5114 "Subsystem": "cec_vpd", global() string 5144 "Subsystem": "cec_vpd", global() string 5175 "Subsystem": "cec_vpd", global() string 5204 "Subsystem": "cec_vpd", global() string 5231 "Subsystem": "cec_vpd", global() string 5260 "Subsystem": "cec_vpd", global() string 5292 "Subsystem": "cec_vpd", global() string 5314 "Subsystem": "cec_vpd", global() string 5347 "Subsystem": "cec_vpd", global() string 5382 "Subsystem": "cec_vpd", global() string 5412 "Subsystem": "cec_op_panel", global() string 5429 "Subsystem": "cec_op_panel", global() string 5449 "Subsystem": "cec_op_panel", global() string 5477 "Subsystem": "cec_op_panel", global() string 5509 "Subsystem": "cec_op_panel", global() string 5531 "Subsystem": "cec_sp_hostboot_iface", global() string 5551 "Subsystem": "bmc_firmware", global() string 5578 "Subsystem": "bmc_firmware", global() string 5601 "Subsystem": "bmc_firmware", global() string 5624 "Subsystem": "bmc_firmware", global() string 5648 "Subsystem": "bmc_firmware", global() string 5671 "Subsystem": "bmc_firmware", global() string 5694 "Subsystem": "bmc_firmware", global() string 5717 "Subsystem": "bmc_firmware", global() string 5740 "Subsystem": "bmc_firmware", global() string 5763 "Subsystem": "bmc_firmware", global() string 5786 "Subsystem": "bmc_firmware", global() string 5822 "Subsystem": "bmc_firmware", global() string 5844 "Subsystem": "bmc_firmware", global() string 5865 "Subsystem": "bmc_firmware", global() string 5886 "Subsystem": "bmc_firmware", global() string 5907 "Subsystem": "bmc_firmware", global() string 5928 "Subsystem": "bmc_firmware", global() string 5949 "Subsystem": "bmc_firmware", global() string 5970 "Subsystem": "bmc_firmware", global() string 5991 "Subsystem": "bmc_firmware", global() string 6012 "Subsystem": "bmc_firmware", global() string 6033 "Subsystem": "bmc_firmware", global() string 6054 "Subsystem": "bmc_firmware", global() string 6075 "Subsystem": "bmc_firmware", global() string 6096 "Subsystem": "bmc_firmware", global() string 6117 "Subsystem": "bmc_firmware", global() string 6138 "Subsystem": "bmc_firmware", global() string 6159 "Subsystem": "bmc_firmware", global() string 6181 "Subsystem": "bmc_firmware", global() string 6202 "Subsystem": "bmc_firmware", global() string 6223 "Subsystem": "bmc_firmware", global() string 6244 "Subsystem": "bmc_firmware", global() string 6265 "Subsystem": "bmc_firmware", global() string 6286 "Subsystem": "bmc_firmware", global() string 6307 "Subsystem": "bmc_firmware", global() string 6328 "Subsystem": "bmc_firmware", global() string 6341 "Subsystem": "bmc_firmware", global() string 6362 "Subsystem": "bmc_firmware", global() string 6383 "Subsystem": "bmc_firmware", global() string 6404 "Subsystem": "bmc_firmware", global() string 6418 "Subsystem": "cec_hardware", global() string 6464 "Subsystem": "cec_hardware", global() string 6480 "Subsystem": "cec_hardware", global() string 6527 "Subsystem": "memory", global() string 6558 "Subsystem": "memory", global() string 6597 "Subsystem": "memory", global() string [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/openbmc/meta-facebook/meta-harma/recipes-phosphor/console/obmc-console/
H A D	plat-80-obmc-console-uart.rules	1 SUBSYSTEM=="tty", ATTRS{iomem_base}=="0x1E78F000", ENV{SYSTEMD_WANTS}="obmc-console@ttyS2", TAG+="s… 2 SUBSYSTEM=="tty", KERNEL=="ttyUSB0", ENV{SYSTEMD_WANTS}="obmc-console@ttyUSB0", TAG+="systemd" 3 SUBSYSTEM=="tty", KERNEL=="ttyUSB1", ENV{SYSTEMD_WANTS}="obmc-console@ttyUSB1", TAG+="systemd" 4 SUBSYSTEM=="tty", KERNEL=="ttyUSB2", ENV{SYSTEMD_WANTS}="obmc-console@ttyUSB2", TAG+="systemd" 5 SUBSYSTEM=="tty", KERNEL=="ttyUSB3", ENV{SYSTEMD_WANTS}="obmc-console@ttyUSB3", TAG+="systemd" 6 SUBSYSTEM=="tty", KERNEL=="ttyUSB4", ENV{SYSTEMD_WANTS}="obmc-console@ttyUSB4", TAG+="systemd" 7 SUBSYSTEM=="tty", KERNEL=="ttyUSB5", ENV{SYSTEMD_WANTS}="obmc-console@ttyUSB5", TAG+="systemd" 8 SUBSYSTEM=="tty", KERNEL=="ttyUSB6", ENV{SYSTEMD_WANTS}="obmc-console@ttyUSB6", TAG+="systemd"
/openbmc/openbmc/meta-facebook/meta-yosemite4/recipes-phosphor/console/obmc-console/
H A D	plat-80-obmc-console-uart.rules	1 SUBSYSTEM=="tty", ATTRS{iomem_base}=="0x1E783000", ENV{SYSTEMD_WANTS}="obmc-console@ttyS0", TAG+="s… 2 SUBSYSTEM=="tty", ATTRS{iomem_base}=="0x1E78D000", ENV{SYSTEMD_WANTS}="obmc-console@ttyS1", TAG+="s… 3 SUBSYSTEM=="tty", ATTRS{iomem_base}=="0x1E78E000", ENV{SYSTEMD_WANTS}="obmc-console@ttyS2", TAG+="s… 4 SUBSYSTEM=="tty", ATTRS{iomem_base}=="0x1E78F000", ENV{SYSTEMD_WANTS}="obmc-console@ttyS3", TAG+="s… 5 SUBSYSTEM=="tty", ATTRS{iomem_base}=="0x1E790000", ENV{SYSTEMD_WANTS}="obmc-console@ttyS5", TAG+="s… 6 SUBSYSTEM=="tty", ATTRS{iomem_base}=="0x1E790100", ENV{SYSTEMD_WANTS}="obmc-console@ttyS6", TAG+="s… 7 SUBSYSTEM=="tty", ATTRS{iomem_base}=="0x1E790200", ENV{SYSTEMD_WANTS}="obmc-console@ttyS7", TAG+="s… 8 SUBSYSTEM=="tty", ATTRS{iomem_base}=="0x1E790300", ENV{SYSTEMD_WANTS}="obmc-console@ttyS8", TAG+="s…
/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/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 …]

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

Project(s)

Full Search
Definition
Symbol
File Path
History
Type