| /openbmc/qemu/hw/usb/ |
| H A D | bus.c | 59 dev->attached = false; in usb_device_post_load()
61 dev->attached = true; in usb_device_post_load()
289 if (dev->attached) { in usb_qdev_unrealize()
489 assert(!dev->attached); in usb_check_attach()
516 dev->attached = true; in usb_device_attach()
526 assert(dev->attached); in usb_device_detach()
530 dev->attached = false; in usb_device_detach()
556 dev->attached ? ", attached" : ""); in usb_bus_dev_print()
684 return dev->attached; in usb_get_attached()
691 if (dev->attached == value) { in usb_set_attached()
|
| H A D | dev-serial.c | 520 if (!s->dev.attached) { in usb_serial_can_read()
568 if (!s->always_plugged && !s->dev.attached) { in usb_serial_event()
573 if (!s->always_plugged && s->dev.attached) { in usb_serial_event()
609 !dev->attached) { in usb_serial_realize()
|
| H A D | xen-usb.c | 74 bool attached; member
468 if (!stub->dev || !stub->attached) { in usbback_check_and_submit()
548 if (!usbback_req->stub || !usbback_req->stub->attached) { in usbback_dispatch()
711 if (!usbif->ports[port - 1].attached) { in usbback_portid_detach()
716 usbif->ports[port - 1].attached = false; in usbback_portid_detach()
803 usbif->ports[port - 1].attached = true; in usbback_portid_add()
969 usbif->ports[port->index].attached = true; in xen_bus_attach()
|
| /openbmc/qemu/docs/system/ |
| H A D | device-emulation.rst | 34 automatically created. In most cases the BUS a device is attached to
38 (``bus=ID``) a device is attached to along with its address
42 additional buses to the system that other devices can be attached to.
48 which would be a bar device (with the ID of baz) which is attached to
50 that bus is itself is attached to the first PCI bus (pci.0).
|
| /openbmc/qemu/docs/ |
| H A D | pci_expander_bridge.txt | 32 - a pxb host bridge attached to NUMA 1 with an e1000 behind it
33 - a pxb host bridge attached to NUMA 0 with an e1000 behind it
34 - a pxb host bridge not attached to any NUMA with a hard drive behind it.
54 When adding a device to PXB it is attached to the bridge for two reasons:
|
| H A D | bypass-iommu.txt | 14 determine whether the devices attached on the PCI host bridge will bypass
18 the attached devices will go through vIOMMU by default.
|
| /openbmc/u-boot/doc/ |
| H A D | README.nokia_rx51 | 30 * 0. if keyboard is closed boot automatically attached kernel image
33 * 3. try boot from attached kernel image
53 * run attachboot - Boot attached kernel image (attached to U-Boot binary)
100 flashed with attached zImage to RX-51 kernel nand area. For enabling UBIFS
|
| H A D | README.nvme | 11 for enterprise and client solid state drives, typically attached to the PCI
30 it is able to scan all available namespaces attached to it. Scanning namespace
46 be executed for all NVMe hard disks attached to the NVMe controller to be
|
| H A D | README.ubi | 31 when such a UBI device is attached (via "ubi part"). Here an example:
59 UBI: attached mtd1 to ubi0
74 Now that the UBI device is attached, this device can be modified
152 UBI partition which has been attached with the ubi part command:
|
| /openbmc/qemu/qapi/ |
| H A D | common.json | 168 # Indicates whether a netfilter is attached to a netdev's transmit
171 # @all: the filter is attached both to the receive and the transmit
174 # @rx: the filter is attached to the receive queue of the netdev,
177 # @tx: the filter is attached to the transmit queue of the netdev,
|
| /openbmc/openbmc/meta-openembedded/meta-networking/recipes-support/mdio-tools/ |
| H A D | mdio-tools.inc | 1 DESCRIPTION = "A low-level debug tool for communicating with devices attached to an MDIO bus"
|
| /openbmc/phosphor-bmc-code-mgmt/cpld/ |
| H A D | README.md | 3 This daemon implements the update process for CPLD attached via I2C bus.
|
| /openbmc/phosphor-bmc-code-mgmt/i2c-vr/ |
| H A D | README.md | 3 This daemon implements the update process for voltage regulators attached via
|
| /openbmc/u-boot/doc/device-tree-bindings/gpio/ |
| H A D | altera_pio.txt | 12 - gpio-bank-name: bank name attached to this device.
|
| /openbmc/phosphor-bmc-code-mgmt/eeprom-device/ |
| H A D | README.md | 3 This daemon implements the update process for EEPROM device attached via I2C.
|
| /openbmc/qemu/docs/system/devices/ |
| H A D | usb.rst | 42 the EHCI controller. Devices must be attached to the correct
56 bus they should be attached to. Here is a complete example:
128 USB attached SCSI device. This does not create a SCSI disk, so
253 case they are added with ``attached = false`` so the guest will not see
254 the device until the ``attached`` property is explicitly set to true.
261 #. ``scripts/qmp/qom-set foo.attached = true``
327 Specifies the bus number the device must be attached to
331 Specifies the physical port the device is attached to
|
| H A D | nvme.rst | 128 Specifies that the namespace will be attached to all controllers in the
130 and may only be attached to a single controller at a time. Shared namespaces
131 are always automatically attached to all controllers (also when controllers
136 not attached to any controllers initially. A shared namespace with this set
137 to ``on`` will never be automatically attached to controllers.
148 will cause NSID 1 will be a shared namespace that is initially attached to both
151 attached to any controller initially (due to ``detached=on``) or to hotplugged
|
| H A D | cxl.rst | 4 targets accelerators and memory devices attached to a CXL host.
15 attached to CXL or PCI End Points. Alternatively there may be CXL Switches
16 with CXL and PCI Endpoints attached below them. In many cases additional
38 CXL attached memory devices.
233 attached Type3 devices. Note this is a representative subset
238 directly attached to these ports.
303 A very simple setup with just one directly attached CXL Type 3 Persistent Memory device::
314 A very simple setup with just one directly attached CXL Type 3 Volatile Memory device::
337 the CXL Type3 device directly attached (no switches).::
|
| /openbmc/u-boot/doc/device-tree-bindings/i2c/ |
| H A D | i2c-mux.txt | 26 with two NXP pca8574 GPIO expanders attached, one each to
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-graphics/panel-mipi-dbi/ |
| H A D | panel-mipi-dbi-native_git.bb | 4 This means many displays attached via SPI, even if the \
|
| /openbmc/qemu/docs/specs/ |
| H A D | fsi.rst | 30 which it is attached.
49 The configuration block presents engines in the order they are attached to the
55 so complete; it's assumed that each CFAM is attached to a single FSI slave (as
|
| /openbmc/openbmc/meta-raspberrypi/recipes-connectivity/pi-bluetooth/pi-bluetooth/ |
| H A D | 0001-bthelper-correct-path-for-hciconfig-under-Yocto.patch | 26 echo Not a UART-attached BT Modem
|
| /openbmc/qemu/gdbstub/ |
| H A D | gdbstub.c | 288 if (gdb_get_cpu_process(cpu)->attached) { in gdb_next_attached_cpu()
304 if (!process->attached) { in gdb_first_attached_cpu()
327 if (!process->attached) { in gdb_get_cpu()
346 if (!process->attached) { in gdb_get_cpu()
814 if (!process->attached) { in gdb_handle_vcont()
1032 process->attached = false; in handle_detach()
1434 process->attached = true; in handle_v_attach()
2314 if (!p->attached) { in gdb_set_stop_cpu()
2516 process->attached = false; in gdb_create_default_process()
|
| /openbmc/u-boot/doc/driver-model/ |
| H A D | usb-info.txt | 115 Given a controller, you know the bus - it is the one attached to the
117 root hub attached to it. This hub, which is itself a USB device, can provide
118 one or more 'ports' to which additional devices can be attached. It is
120 attached.
151 U-Boot simply finds the controller to which the device is attached, and sends
173 are attached to a parent hub (or controller in the case of the root hub) and
174 so have parent data attached to them (this is struct usb_device).
200 (only) device that is attached to the controller - a root hub
|
| /openbmc/openbmc/meta-openembedded/meta-networking/recipes-protocols/zeroconf/ |
| H A D | zeroconf_0.9.bb | 7 are normally attached to each Ethernet device in your computer. \
|