Searched full:devices (Results 1 – 25 of 4837) sorted by relevance
12345678910>>...194
| /openbmc/linux/Documentation/ABI/testing/ |
| D | sysfs-bus-soundwire-slave | |
| D | sysfs-bus-coresight-devices-cti | |
| D | sysfs-bus-coresight-devices-etm4x | |
| D | sysfs-devices-platform-ipmi | |
| D | sysfs-driver-chromeos-acpi | |
| D | sysfs-bus-counter | |
| D | sysfs-driver-ccp | |
| D | sysfs-devices-power | |
| D | sysfs-devices-mapping | |
| D | sysfs-platform-hidma-mgmt | |
| D | sysfs-bus-most | |
| /openbmc/qemu/docs/system/ |
| H A D | device-emulation.rst | 6 QEMU supports the emulation of a large number of devices from
7 peripherals such network cards and USB devices to integrated systems
10 used to describes devices within QEMU.
20 system is expecting to see. All devices can be specified with the
22 options ``--device help`` will list all devices it is aware of. Using
32 Most devices will exist on a BUS of some sort. Depending on the
35 can be inferred, for example PCI devices are generally automatically
41 Some devices, for example a PCI SCSI host controller, will add an
42 additional buses to the system that other devices can be attached to.
43 A hypothetical chain of devices might look like:
[all …]
|
| /openbmc/entity-manager/src/entity_manager/ |
| H A D | devices.hpp | 7 namespace devices namespace
19 // driver creates a /sys/bus/i2c/devices/<busnum>-<i2caddr>/hwmon
22 // not reliable. I2C devices flagged with hasHWMonDir are tested for correct
27 // Devices such as I2C EEPROMs do not generate this file structure. These
28 // kinds of devices are flagged using the noHWMonDir enumeration. The
56 ExportTemplate("24c01 $Address", "/sys/bus/i2c/devices/i2c-$Bus",
60 ExportTemplate("24c02 $Address", "/sys/bus/i2c/devices/i2c-$Bus",
64 ExportTemplate("24c04 $Address", "/sys/bus/i2c/devices/i2c-$Bus",
68 ExportTemplate("24c08 $Address", "/sys/bus/i2c/devices/i2c-$Bus",
72 ExportTemplate("24c16 $Address", "/sys/bus/i2c/devices/i2c-$Bus",
[all …]
|
| /openbmc/linux/Documentation/ABI/stable/ |
| D | sysfs-driver-mlxreg-io | |
| D | sysfs-driver-firmware-zynqmp | |
| D | sysfs-devices-node | |
| D | sysfs-driver-dma-idxd | |
| D | sysfs-devices-system-cpu | |
| /openbmc/linux/drivers/platform/surface/ |
| D | Kconfig | |
| /openbmc/openbmc/meta-facebook/meta-harma/recipes-phosphor/configuration/entity-manager/ |
| H A D | device-driver-probe | 29 echo pca9546 0x71 > /sys/bus/i2c/devices/i2c-9/new_device
32 echo pca9546 0x71 > /sys/bus/i2c/devices/i2c-11/new_device
43 echo adc128d818 0x1d > /sys/bus/i2c/devices/i2c-36/new_device
44 echo ina238 0x44 > /sys/bus/i2c/devices/i2c-36/new_device
45 echo ina238 0x45 > /sys/bus/i2c/devices/i2c-36/new_device
46 echo MCP9600 0x60 > /sys/bus/i2c/devices/i2c-34/new_device
47 echo MCP9600 0x62 > /sys/bus/i2c/devices/i2c-34/new_device
48 echo MCP9600 0x63 > /sys/bus/i2c/devices/i2c-34/new_device
49 echo MCP9600 0x64 > /sys/bus/i2c/devices/i2c-34/new_device
50 echo MCP9600 0x65 > /sys/bus/i2c/devices/i2c-34/new_device
[all …]
|
| /openbmc/linux/Documentation/admin-guide/ |
| D | sysfs-rules.rst | |
| /openbmc/linux/Documentation/arch/s390/ |
| D | common_io.rst | |
| /openbmc/linux/drivers/staging/most/Documentation/ABI/ |
| D | sysfs-class-most.txt | |
| /openbmc/linux/drivers/staging/greybus/Documentation/ |
| D | sysfs-bus-greybus | |
| /openbmc/qemu/docs/ |
| H A D | qdev-device-use.txt | 5 In qdev, each device has a parent bus. Some devices provide one or
10 where this address can be configured, devices provide a bus-specific
28 === Block Devices ===
34 of which can have up to two devices, and each device is a guest part,
41 The old ways to define block devices define host and guest part
70 * serial goes into DEV-OPTS, for devices supporting serial numbers.
71 For other devices, it goes nowhere.
95 As for all PCI devices, you can add bus=PCI-BUS,addr=DEVFN to
111 "Default Devices".
122 As for all PCI devices, you can add bus=PCI-BUS,addr=DEVFN to
[all …]
|
12345678910>>...194