/openbmc/linux/drivers/staging/board/ |
H A D | Kconfig | 7 in-tree development and integration of platform devices. 9 Helps developers integrate devices as platform devices for
|
/openbmc/linux/drivers/vfio/cdx/ |
H A D | Kconfig | 9 tristate "VFIO support for CDX bus devices" 13 Driver to enable VFIO support for the devices on CDX bus. 14 This is required to make use of CDX devices present in
|
/openbmc/linux/drivers/bcma/ |
H A D | README | 10 2) AMBA standard devices called ports or wrappers. They have CIDs (AMBA_CID) 12 devices is used for managing Broadcom specific core. 14 Addresses of AMBA devices are not hardcoded in driver and have to be read from 18 16 devices identified by Broadcom specific fields: manufacturer, id, revision
|
/openbmc/linux/Documentation/ABI/testing/ |
H A D | sysfs-devices-real_power_state | 1 What: /sys/devices/.../real_power_state 5 The /sys/devices/.../real_power_state attribute is only present 18 from the value of the /sys/devices/.../power_state attribute for 21 other devices using them at the moment.
|
H A D | sysfs-bus-iio-impedance-analyzer-ad5933 | 1 What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_frequency_start 8 What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_frequency_increment 16 What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_frequency_points 27 What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_settling_cycles
|
H A D | usb-charger-uevent | 25 UDEV change /devices/soc0/usbphynop1 (platform) 27 DEVPATH=/devices/soc0/usbphynop1 42 KERNEL change /devices/soc0/usbphynop1 (platform) 44 DEVPATH=/devices/soc0/usbphynop1
|
H A D | sysfs-bus-iio-chemical-sunrise-co2 | 1 What: /sys/bus/iio/devices/iio:deviceX/in_concentration_co2_calibration_factory 8 What: /sys/bus/iio/devices/iio:deviceX/in_concentration_co2_calibration_background 15 What: /sys/bus/iio/devices/iio:deviceX/error_status_available 33 What: /sys/bus/iio/devices/iio:deviceX/error_status
|
H A D | sysfs-driver-w1_therm | 1 What: /sys/bus/w1/devices/.../alarms 17 What: /sys/bus/w1/devices/.../eeprom_cmd 23 embedded in device EEPROM. Be aware that devices support 33 What: /sys/bus/w1/devices/.../ext_power 47 What: /sys/bus/w1/devices/.../resolution 69 What: /sys/bus/w1/devices/.../temperature 90 What: /sys/bus/w1/devices/.../w1_slave 111 What: /sys/bus/w1/devices/w1_bus_masterXX/therm_bulk_read 129 devices on the bus 139 What: /sys/bus/w1/devices/.../conv_time [all …]
|
H A D | sysfs-devices-xenbus | 1 What: /sys/devices/*/xenbus/event_channels 8 What: /sys/devices/*/xenbus/events 15 What: /sys/devices/*/xenbus/jiffies_eoi_delayed 24 What: /sys/devices/*/xenbus/spurious_events 32 What: /sys/devices/*/xenbus/spurious_threshold
|
H A D | sysfs-class-iommu | 1 What: /sys/class/iommu/<iommu>/devices/ 6 IOMMU drivers are able to link devices managed by a 10 What: /sys/devices/.../iommu
|
/openbmc/linux/Documentation/ABI/stable/ |
H A D | sysfs-devices | 5 What: /sys/devices/*/of_node 13 What: /sys/devices/*/devspec 20 What: /sys/devices/*/obppath 27 What: /sys/devices/*/dev
|
/openbmc/linux/drivers/media/cec/platform/ |
H A D | Kconfig | 15 between compatible devices. 41 between compatible devices. 53 between compatible devices. 64 between compatible devices. 75 between compatible devices. 87 between compatible devices. 98 between compatible devices. 110 between compatible devices.
|
/openbmc/linux/Documentation/devicetree/bindings/ |
H A D | xilinx.txt | 3 The Xilinx EDK toolchain ships with a set of IP cores (devices) for use 4 in Xilinx Spartan and Virtex FPGAs. The devices cover the whole range 6 devices (gpio, LCD, spi, etc). Also, since these devices are 25 [, (list of compatible devices), ...]; 90 device tree. The following are bindings for specific devices: 116 Xilinx Ethernet devices. In addition to general xilinx properties 117 listed above, nodes for these devices should include a phy-handle 123 Xilinx uartlite devices are simple fixed speed serial ports. 130 Xilinx hwicap devices provide access to the configuration logic 146 Xilinx UART 16550 devices are very similar to the NS16550 but with [all …]
|
/openbmc/u-boot/doc/ |
H A D | README.power-framework | 20 devices are now available on the board - namely power managers (PMIC), fuel 22 devices (MFD). 30 Power devices use not only I2C for communication, but SPI as well. Additionally 35 The "flat" hierarchy for power devices works well when each device performs only 39 the master and uses methods exported by other devices. We need to control MUIC 58 The framework classifies devices by their function - separate directories should 59 be maintained for different classes of devices. 66 devices. 92 To charge a battery, information from several "abstract" power devices is 140 Define devices as listed at 1. [all …]
|
/openbmc/u-boot/doc/driver-model/ |
H A D | pci-info.txt | 23 If there is no alias the devices will be numbered sequentially in the device 27 This does a scan of the bus to locate available devices. These devices are 31 After probing a bus, the available devices will appear in the device tree 37 PCI devices can appear in the flattened device tree. If they do, their node 45 Note we must describe PCI devices with the same bus hierarchy as the 47 relationship during PCI bus enumeration thus PCI devices won't be bound to 98 PCIe-to-PCI bridge and all the chipset integrated devices like the PCI UART 99 device are on the PCI bus. Like other devices in the device tree, if we want 100 to bind PCI devices before relocation, "u-boot,dm-pre-reloc" must be declared 103 If PCI devices are not listed in the device tree, U_BOOT_PCI_DEVICE can be used [all …]
|
/openbmc/linux/Documentation/PCI/ |
H A D | pci-iov-howto.rst | 20 devices. The physical device is referred to as Physical Function (PF) 21 while the virtual devices are referred to as Virtual Functions (VF). 51 The second method is the recommended method for new/future VF devices. 56 The VF is treated as hot-plugged PCI devices in the kernel, so they 57 should be able to work in the same way as real PCI devices. The VF 77 /sys/bus/pci/devices/<DOMAIN:BUS:DEVICE.FUNCTION>/sriov_numvfs 88 /sys/bus/pci/devices/<DOMAIN:BUS:DEVICE.FUNCTION>/sriov_numvfs 96 /sys/bus/pci/devices/<DOMAIN:BUS:DEVICE.FUNCTION>/sriov_drivers_autoprobe 104 /sys/bus/pci/devices/<DOMAIN:BUS:DEVICE.FUNCTION>/sriov_drivers_autoprobe
|
/openbmc/linux/drivers/hid/ |
H A D | hid-lgff.c | 47 static const struct dev_type devices[] = { variable 135 for (i = 0; i < ARRAY_SIZE(devices); i++) { in lgff_init() 136 if (dev->id.vendor == devices[i].idVendor && in lgff_init() 137 dev->id.product == devices[i].idProduct) { in lgff_init() 138 ff_bits = devices[i].ff; in lgff_init()
|
/openbmc/linux/Documentation/admin-guide/laptops/ |
H A D | lg-laptop.rst | 26 Writing 0/1 to /sys/devices/platform/lg-laptop/reader_mode disables/enables 34 Writing 0/1 to /sys/devices/platform/lg-laptop/fn_lock disables/enables 51 Writing 1/0 to /sys/devices/platform/lg-laptop/fan_mode disables/enables 58 Writing 0/1 to /sys/devices/platform/lg-laptop/usb_charge disables/enables 67 The are two LED devices supported by the driver:
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/utouch/ |
H A D | utouch-evemu_git.bb | 2 …brary and tools are used to describe devices, record data, create devices and replay data from ker…
|
/openbmc/linux/Documentation/driver-api/ |
H A D | isa.rst | 8 During the recent "isa drivers using platform devices" discussion it was 21 As another difference: these devices only exist in the driver model due 47 parameter, indicating how many devices to create and call our methods 63 changeover to platform devices, it could just not provide a .match() and 78 loops over the passed in ndev creating devices and registering them. 95 driver's devices by seeing if the device's platform_data pointer is set 96 to this driver. Platform devices compare strings, but we don't need to 109 If during all this, there's any error, or no devices matched at all 112 isa_unregister_driver() just unregisters the matched devices and the 121 ISA devices which may be registered in the I/O port address space given [all …]
|
/openbmc/qemu/docs/system/s390x/ |
H A D | vfio-ccw.rst | 5 make certain I/O subchannels and their devices available to a guest. The 6 host will not interact with those subchannels/devices any more. 8 Note that while vfio-ccw should work with most non-QDIO devices, only ECKD 45 [root@host ~]# echo 0.0.0313 > /sys/bus/css/devices/0.0.0313/driver/unbind 51 /sys/bus/css/devices/0.0.0313/mdev_supported_types/vfio_ccw-io/create 61 /sys/bus/mdev/devices/7e270a25-e163-4922-af60-757fc8ed48c6
|
/openbmc/linux/drivers/net/wireless/intersil/p54/ |
H A D | Kconfig | 10 also need to be enabled in order to support any devices. 12 These devices require softmac firmware which can be found at 24 These devices require softmac firmware which can be found at 34 This driver supports most devices that are supported by the 35 fullmac prism54 driver plus many devices which are not 57 Unlike the PCI or USB devices, the SPI variants don't have
|
/openbmc/linux/Documentation/trace/coresight/ |
H A D | ultrasoc-smb.rst | 15 corresponding trace generators (ETM) are attached as source devices. 20 The SMB devices appear on the existing coresight bus alongside other 21 devices:: 23 $# ls /sys/bus/coresight/devices/ 28 $# ls /sys/bus/coresight/devices/ultra_smb0 30 $# ls /sys/bus/coresight/devices/ultra_smb0/mgmt
|
/openbmc/linux/drivers/media/platform/ |
H A D | Kconfig | 7 bool "Media platform devices" 15 bool "V4L platform devices" 20 bool "SDR platform devices" 26 bool "DVB platform devices" 32 bool "Memory-to-memory multimedia devices" 35 Say Y here to enable selecting drivers for V4L devices that
|
/openbmc/u-boot/Documentation/devicetree/bindings/misc/ |
H A D | gdsys,io-endpoint.txt | 1 gdsys IO endpoint of IHS FPGA devices 3 The IO endpoint of IHS FPGA devices is a packet-based transmission interface 4 that allows interconnected gdsys devices to send and receive data over the
|