Home
last modified time | relevance | path

Searched +full:on +full:- +full:device (Results 1 – 25 of 1143) sorted by relevance

12345678910>>...46

/openbmc/qemu/tests/qemu-iotests/
H A D026.out6 Event: l1_update; errno: 5; imm: off; once: on; write
8 No errors were found on the image.
11 Event: l1_update; errno: 5; imm: off; once: on; write -b
13 No errors were found on the image.
17 qemu-io: Failed to flush the L2 table cache: Input/output error
18 qemu-io: Failed to flush the refcount block cache: Input/output error
20 No errors were found on the image.
23 Event: l1_update; errno: 5; imm: off; once: off; write -b
24 qemu-io: Failed to flush the L2 table cache: Input/output error
25 qemu-io: Failed to flush the refcount block cache: Input/output error
[all …]
H A D026.out.nocache6 Event: l1_update; errno: 5; imm: off; once: on; write
8 No errors were found on the image.
11 Event: l1_update; errno: 5; imm: off; once: on; write -b
13 No errors were found on the image.
17 qemu-io: Failed to flush the L2 table cache: Input/output error
18 qemu-io: Failed to flush the refcount block cache: Input/output error
20 No errors were found on the image.
23 Event: l1_update; errno: 5; imm: off; once: off; write -b
24 qemu-io: Failed to flush the L2 table cache: Input/output error
25 qemu-io: Failed to flush the refcount block cache: Input/output error
[all …]
H A D186.out6 Testing: -device floppy
7 QEMU X.Y.Z monitor - type 'help' for more information
9 /machine/peripheral-anon/device[1]: [not inserted]
10 Attached to: /machine/peripheral-anon/device[N]
11 Removable device: not locked, tray closed
14 Testing: -device floppy,id=qdev_id
15 QEMU X.Y.Z monitor - type 'help' for more information
19 Removable device: not locked, tray closed
22 Testing: -device ide-cd
23 QEMU X.Y.Z monitor - type 'help' for more information
[all …]
/openbmc/u-boot/include/dm/
H A Duclass-internal.h1 /* SPDX-License-Identifier: GPL-2.0+ */
15 * uclass_find_next_free_req_seq() - Get the next free req_seq number
28 * uclass_get_device_tail() - handle the end of a get_device call
30 * This handles returning an error or probing a device as needed.
32 * @dev: Device that needs to be probed
33 * @ret: Error to return. If non-zero then the device is not probed
35 * @return ret, if non-zero, else the result of the device_probe() call
40 * dev_get_uclass_index() - Get uclass and index of device
41 * @dev: - in - Device that we want the uclass/index of
42 * @ucp: - out - A pointer to the uclass the device belongs to
[all …]
H A Duclass.h1 /* SPDX-License-Identifier: GPL-2.0+ */
13 #include <dm/uclass-id.h>
18 * struct uclass - a U-Boot drive class, collecting together similar drivers
24 * There may be drivers for on-chip SoC GPIO banks, I2C GPIO expanders and
51 * struct uclass_driver - Driver for the uclass
58 * @post_bind: Called after a new device is bound to this uclass
59 * @pre_unbind: Called before a device is unbound from this uclass
60 * @pre_probe: Called before a new device is probed
61 * @post_probe: Called after a new device is probed
62 * @pre_remove: Called before a device is removed
[all …]
H A Ddevice-internal.h1 /* SPDX-License-Identifier: GPL-2.0+ */
19 * device_bind() - Create a device and bind it to a driver
21 * Called to set up a new device attached to a driver. The device will either
22 * have platdata, or a device tree node which can be used to create the
25 * Once bound a device exists but is not yet active until device_probe() is
28 * @parent: Pointer to device's parent, under which this driver will exist
29 * @drv: Device's driver
30 * @name: Name of device (e.g. device tree node name)
31 * @platdata: Pointer to data for this device - the structure is device-
32 * specific but may include the device's I/O address, etc.. This is NULL for
[all …]
/openbmc/linux/drivers/mfd/
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
7 menu "Multifunction device drivers"
17 depends on PCI && (X86_32 || (X86 && COMPILE_TEST))
18 depends on !UML
25 depends on ARCH_INTEL_SOCFPGA && SPI_MASTER=y && OF
36 depends on ARCH_INTEL_SOCFPGA && OF
45 tristate "Active-semi ACT8945A"
48 depends on I2C && OF
50 Support for the ACT8945A PMIC from Active-semi. This device
51 features three step-down DC/DC converters and four low-dropout
[all …]
/openbmc/u-boot/env/
H A DKconfig5 depends on !ENV_IS_IN_EEPROM
6 depends on !ENV_IS_IN_EXT4
7 depends on !ENV_IS_IN_FAT
8 depends on !ENV_IS_IN_FLASH
9 depends on !ENV_IS_IN_MMC
10 depends on !ENV_IS_IN_NAND
11 depends on !ENV_IS_IN_NVRAM
12 depends on !ENV_IS_IN_ONENAND
13 depends on !ENV_IS_IN_REMOTE
14 depends on !ENV_IS_IN_SPI_FLASH
[all …]
/openbmc/linux/include/linux/usb/
H A Dotg-fsm.h1 // SPDX-License-Identifier: GPL-2.0+
18 * Table:6-4
23 * Table:6-5
49 * struct otg_fsm - OTG state machine according to the OTG spec
53 * Common inputs for A and B device
54 * @id: TRUE for B-device, FALSE for A-device.
56 * ADP measurement taken at n-2, differs by more than CADP_THR
57 * @power_up: TRUE when the OTG device first powers up its USB system and
60 * A-Device state inputs
61 * @a_srp_det: TRUE if the A-device detects SRP
[all …]
/openbmc/qemu/subprojects/libvduse/
H A Dlibvduse.h2 * VDUSE (vDPA Device in Userspace) library
10 * later. See the COPYING file in the top-level directory.
21 /* VDUSE device structure */
39 /* Number of physically-contiguous device-readable descriptors */
41 /* Number of physically-contiguous device-writable descriptors */
43 /* Array to store physically-contiguous device-writable descriptors */
45 /* Array to store physically-contiguous device-readable descriptors */
63 * Get corresponding VDUSE device from the virtqueue.
65 * Returns: a pointer to VDUSE device on success, NULL on failure.
75 * Returns: file descriptor on success, -1 on failure.
[all …]
/openbmc/u-boot/dts/
H A DKconfig2 # Device Tree Control
22 menu "Device Tree Control"
23 depends on SUPPORT_OF_CONTROL
26 bool "Run-time configuration via Device Tree"
29 This feature provides for run-time configuration of U-Boot
30 via a flattened device tree.
33 bool "Board-specific manipulation of Device Tree"
36 U-Boot's device tree (e.g. to delete device from it). This option
37 make the Device Tree writeable and provides a board-specific
38 "board_fix_fdt" callback (called during pre-relocation time), which
[all …]
/openbmc/linux/drivers/md/
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
3 # Block device driver configuration
8 depends on BLOCK
10 Support multiple physical spindles through a single logical device.
20 # after relevant mdadm enhancements - to make "names=yes"
21 # the default - are widely available.
25 logical block device. This can be used to simply append one
27 into a RAID1/4/5 device so as to provide protection against hard
33 More information about Software RAID on Linux is contained in the
34 Software RAID mini-HOWTO, available from
[all …]
/openbmc/linux/sound/soc/intel/boards/
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
4 depends on SND_SOC_INTEL_SST_TOPLEVEL || SND_SOC_SOF_INTEL_TOPLEVEL
45 depends on I2C
46 depends on I2C_DESIGNWARE_PLATFORM || COMPILE_TEST
47 depends on X86_INTEL_LPSS || COMPILE_TEST
50 This adds support for the Lynxpoint Audio DSP on Intel(R) Haswell
52 Say Y or m if you have such a device.
61 depends on I2C
62 depends on I2C_DESIGNWARE_PLATFORM || COMPILE_TEST
63 depends on X86_INTEL_LPSS || COMPILE_TEST
[all …]
/openbmc/linux/drivers/pci/msi/
H A Dapi.c1 // SPDX-License-Identifier: GPL-2.0
3 * PCI MSI/MSI-X — Exported APIs for device drivers
5 * Copyright (C) 2003-2004 Intel
17 * pci_enable_msi() - Enable MSI interrupt mode on device
18 * @dev: the PCI device to operate on
20 * Legacy device driver API to enable MSI interrupts mode on device and
21 * allocate a single interrupt vector. On success, the allocated vector
22 * Linux IRQ will be saved at @dev->irq. The driver must invoke
23 * pci_disable_msi() on cleanup.
28 * Return: 0 on success, errno otherwise
[all …]
/openbmc/linux/drivers/platform/surface/
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
3 # Microsoft Surface Platform-Specific Drivers
7 bool "Microsoft Surface Platform-Specific Device Drivers"
8 depends on ARM64 || X86 || COMPILE_TEST
11 Say Y here to get to see options for platform-specific device drivers
21 depends on ACPI_WMI
22 depends on DMI
23 depends on INPUT
24 depends on SPI
29 be called surface3-wmi.
[all …]
/openbmc/u-boot/include/power/
H A Dregulator.h1 /* SPDX-License-Identifier: GPL-2.0+ */
3 * Copyright (C) 2014-2015 Samsung Electronics
11 * U-Boot Voltage/Current Regulator
14 * The regulator API is based on a driver model, with the device tree support.
18 * The regulator uclass - is based on uclass platform data which is allocated,
19 * automatically for each regulator device on bind and 'dev->uclass_platdata'
21 * The uclass file: 'drivers/power/regulator/regulator-uclass.c'
23 * The regulator device - is based on driver's model 'struct udevice'.
25 * - devname - the regulator device's name: 'dev->name'
26 * - platname - the device's platdata's name. So in the code it looks like:
[all …]
/openbmc/linux/drivers/mtd/maps/
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
3 depends on MTD!=n
4 depends on HAS_IOMEM
7 bool "Support non-linear mappings of flash chips"
13 tristate "Flash device in physical memory map"
14 depends on MTD_CFI || MTD_JEDECPROBE || MTD_ROM || MTD_RAM || MTD_LPDDR
19 the physical address and size of the flash chips on your
21 with config options or at run-time.
28 depends on MTD_PHYSMAP
39 depends on MTD_PHYSMAP_COMPAT
[all …]
/openbmc/phosphor-power/phosphor-power-sequencer/docs/
H A DREADME.md1 # phosphor-power-sequencer
5 The phosphor-power-sequencer application powers the chassis on/off and monitors
6 the power sequencer device.
9 application uses information from the power sequencer device to determine the
14 The application is a single-threaded C++ executable. It is a 'daemon' process
16 reaches the Ready state and before the chassis is powered on.
18 The application is driven by an optional, system-specific JSON configuration
21 device, voltage rails, GPIOs, and fault checks to perform.
23 ## Power sequencer device
25 A power sequencer device enables (turns on) the voltage rails in the correct
[all …]
/openbmc/linux/sound/soc/mediatek/
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
8 depends on ARCH_MEDIATEK
13 Select Y if you have such device.
18 depends on SND_SOC_MT2701 && I2C
24 Select Y if you have such device.
29 depends on SND_SOC_MT2701 && I2C
34 Select Y if you have such device.
39 depends on ARCH_MEDIATEK
44 Select Y if you have such device.
49 depends on SND_SOC_MT6797 && MTK_PMIC_WRAP
[all …]
/openbmc/linux/Documentation/driver-api/
H A Ddevice_link.rst4 Device links
8 that are borne out of a parent/child relationship within the device
10 are ordered based on this relationship, i.e. children are always suspended
13 Sometimes there is a need to represent device dependencies beyond the
18 dependencies, i.e. that one device must be bound to a driver before
21 Often these two dependency types come together, so a device depends on
25 Device links allow representation of such dependencies in the driver core.
27 In its standard or *managed* form, a device link combines *both* dependency
29 "supplier" device and its "consumer" devices, and it guarantees driver
30 presence on the supplier. The consumer devices are not probed before the
[all …]
/openbmc/linux/drivers/usb/gadget/udc/
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0
3 # USB Gadget support on a system involves
7 # NOTE: Gadget support ** DOES NOT ** depend on host-side CONFIG_USB !!
9 # - Host systems (like PCs) need CONFIG_USB (with "A" jacks).
10 # - Peripherals (like PDAs) need CONFIG_USB_GADGET (with "B" jacks).
11 # - Some systems have both kinds of controllers.
13 # With help from a special transceiver and a "Mini-AB" jack, systems with
14 # both kinds of controller can also support "USB On-the-Go" (CONFIG_USB_OTG).
22 # - integrated/SOC controllers first
23 # - licensed IP used in both SOC and discrete versions
[all …]
/openbmc/linux/drivers/mtd/devices/
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
2 menu "Self-contained MTD device drivers"
3 depends on MTD!=n
4 depends on HAS_IOMEM
8 depends on PCI
10 This provides a MTD device driver for the Ramix PMC551 RAM PCI card
12 These devices come in memory configurations from 32M - 1G. If you
18 will use a 1G memory map as its view of the device. As a module,
21 particularly useful on the 2.2 kernels on PPC architectures as there
26 depends on MTD_PMC551
[all …]
/openbmc/linux/Documentation/hid/
H A Dhid-transport.rst8 Bluetooth, I2C and user-space I/O drivers.
14 devices and register them with the HID bus. HID core then loads generic device
15 drivers on top of it. The transport drivers are responsible for raw data
16 transport and device setup/management. HID core is responsible for
17 report-parsing, report interpretation and the user-space API. Device specifics
18 and quirks are handled by all layers depending on the quirk.
22 +-----------+ +-----------+ +-----------+ +-----------+
23 | Device #1 | | Device #i | | Device #j | | Device #k |
24 +-----------+ +-----------+ +-----------+ +-----------+
26 +------------+ +------------+
[all …]
/openbmc/u-boot/include/
H A Dadc.h1 /* SPDX-License-Identifier: GPL-2.0+ */
10 /* ADC_CHANNEL() - ADC channel bit mask, to select only required channels */
13 /* The last possible selected channel with 32-bit mask */
18 * the device's input Voltage range is bipolar.
19 * - ADC_DATA_FORMAT_BIN - binary offset
20 * - ADC_DATA_FORMAT_2S - two's complement
22 * Note: Device's driver should fill the 'data_format' field of its uclass's
31 * struct adc_channel - structure to hold channel conversion data.
32 * Useful to keep the result of a multi-channel conversion output.
34 * @id - channel id
[all …]
/openbmc/linux/drivers/mtd/
H A DKconfig2 tristate "Memory Technology Device (MTD) support"
6 used for solid state file systems on embedded devices. This option
9 to enumerate the devices which are present and obtain a handle on
17 depends on m
23 WARNING: some of the tests will ERASE entire MTD device which they
33 # MTD block device support is select'ed if needed
39 tristate "Caching block device access to MTD devices"
40 depends on BLOCK
45 on RAM chips in this manner. This block device is a user of MTD
49 It's possible to mount a rootfs using the MTD device on the "root="
[all …]

12345678910>>...46