/openbmc/linux/drivers/platform/surface/aggregator/ |
H A D | Kconfig | 12 Surface devices (i.e. Surface Pro 5, Surface Book 2, Surface Laptop, 13 and newer, with exception of Surface Go series devices). 18 - battery status information (all devices) 19 - thermal sensor access (all devices) 20 - performance mode / cooling mode control (all devices) 34 Note: While 4th-generation Surface devices also make use of a SAM EC, 37 devices using SAM-over-SSH are supported, whereas devices using 54 for non-platform and non-ACPI SSAM devices, i.e. SSAM devices that are
|
/openbmc/linux/Documentation/ABI/testing/ |
H A D | sysfs-bus-event_source-devices-hv_24x7 | 1 What: /sys/bus/event_source/devices/hv_24x7/format 6 (See ABI/testing/sysfs-bus-event_source-devices-format). 26 What: /sys/bus/event_source/devices/hv_24x7/interface/catalog 36 What: /sys/bus/event_source/devices/hv_24x7/interface/catalog_length 43 What: /sys/bus/event_source/devices/hv_24x7/interface/catalog_version 50 What: /sys/devices/hv_24x7/interface/sockets 57 What: /sys/devices/hv_24x7/interface/chipspersocket 64 What: /sys/devices/hv_24x7/interface/coresperchip 71 What: /sys/devices/hv_24x7/cpumask 78 What: /sys/bus/event_source/devices/hv_24x7/event_descs/<event-name> [all …]
|
H A D | sysfs-driver-ufs | 743 What: /sys/bus/platform/devices/*.ufs/flags/device_init 762 What: /sys/bus/platform/devices/*.ufs/flags/power_on_wpe 773 What: /sys/bus/platform/devices/*.ufs/flags/bkops_enable 803 What: /sys/bus/platform/devices/*.ufs/flags/busy_rtc 995 What: /sys/bus/platform/devices/*.ufs/rpm_lvl 1040 What: /sys/bus/platform/devices/*.ufs/spm_lvl 1311 What: /sys/bus/platform/devices/*.ufs/flags/wb_enable 1324 What: /sys/bus/platform/devices/*.ufs/flags/wb_flush_en 1409 What: /sys/bus/platform/devices/*.ufs/wb_on 1430 What: /sys/bus/platform/devices/*.ufs/wb_flush_threshold [all …]
|
H A D | sysfs-driver-toshiba_acpi | 1 What: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/kbd_backlight_mode 16 Also note that toggling this value on type 1 devices, requires 20 What: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/kbd_backlight_timeout 33 What: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/position 40 What: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/touchpad 68 What: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/kbd_type 79 What: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/usb_sleep_charge 143 What: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/version 150 What: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/fan 178 What: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/panel_power_on [all …]
|
H A D | sysfs-platform-lg-laptop | 1 What: /sys/devices/platform/lg-laptop/reader_mode 8 What: /sys/devices/platform/lg-laptop/fn_lock 15 What: /sys/devices/platform/lg-laptop/battery_care_limit 23 What: /sys/devices/platform/lg-laptop/fan_mode 30 What: /sys/devices/platform/lg-laptop/usb_charge
|
H A D | sysfs-class-rnbd-server | 12 block device is created under /sys/class/rnbd-server/ctl/devices/. 14 What: /sys/class/rnbd-server/ctl/devices/<device_name>/block_dev 23 What: /sys/class/rnbd-server/ctl/devices/<device_name>/sessions/ 30 /sys/class/rnbd-server/ctl/devices/<device_name>/sessions/<session-name>/ 34 What: /sys/class/rnbd-server/ctl/devices/<device_name>/sessions/<session-name>/read_only 40 What: /sys/class/rnbd-server/ctl/devices/<device_name>/sessions/<session-name>/mapping_path 46 What: /sys/class/rnbd-server/ctl/devices/<device_name>/sessions/<session-name>/access_mode 52 What: /sys/class/rnbd-server/ctl/devices/<device_name>/sessions/<session-name>/force_close
|
H A D | sysfs-bus-iio-dac-ad5766 | 1 What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_dither_enable 7 What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_dither_invert 14 What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_dither_scale_available 20 What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_dither_scale 26 What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_dither_source
|
H A D | sysfs-bus-coresight-devices-stm | 1 What: /sys/bus/coresight/devices/<memory_map>.stm/enable_source 11 What: /sys/bus/coresight/devices/<memory_map>.stm/hwevent_enable 18 What: /sys/bus/coresight/devices/<memory_map>.stm/hwevent_select 26 What: /sys/bus/coresight/devices/<memory_map>.stm/port_enable 34 What: /sys/bus/coresight/devices/<memory_map>.stm/port_select 41 What: /sys/bus/coresight/devices/<memory_map>.stm/status 48 What: /sys/bus/coresight/devices/<memory_map>.stm/traceid
|
H A D | sysfs-bus-fsi | 1 What: /sys/bus/platform/devices/../fsi-master/fsi0/rescan 6 Initiates a FSI master scan for all connected slave devices 9 What: /sys/bus/platform/devices/../fsi-master/fsi0/break 19 What: /sys/bus/platform/devices/../fsi-master/fsi0/slave@00:00/term 32 What: /sys/bus/platform/devices/../fsi-master/fsi0/slave@00:00/raw 40 What: /sys/bus/platform/devices/../cfam_reset
|
H A D | sysfs-devices-edac | 1 What: /sys/devices/system/edac/mc/mc*/reset_counters 12 What: /sys/devices/system/edac/mc/mc*/seconds_since_reset 19 What: /sys/devices/system/edac/mc/mc*/mc_name 25 What: /sys/devices/system/edac/mc/mc*/size_mb 31 What: /sys/devices/system/edac/mc/mc*/ue_count 39 What: /sys/devices/system/edac/mc/mc*/ue_noinfo_count 46 What: /sys/devices/system/edac/mc/mc*/ce_count 56 What: /sys/devices/system/edac/mc/mc*/ce_noinfo_count 66 What: /sys/devices/system/edac/mc/mc*/sdram_scrub_rate 78 What: /sys/devices/system/edac/mc/mc*/max_location [all …]
|
/openbmc/linux/arch/x86/kernel/ |
H A D | platform-quirks.c | 15 x86_platform.legacy.devices.pnpbios = 1; in x86_early_init_platform_quirks() 22 x86_platform.legacy.devices.pnpbios = 0; in x86_early_init_platform_quirks() 27 x86_platform.legacy.devices.pnpbios = 0; in x86_early_init_platform_quirks() 39 return x86_platform.legacy.devices.pnpbios == 0; in x86_pnpbios_disabled()
|
/openbmc/linux/drivers/vfio/fsl-mc/ |
H A D | Kconfig | 1 menu "VFIO support for FSL_MC bus devices" 5 tristate "VFIO support for QorIQ DPAA2 fsl-mc bus devices" 9 (Management Complex) devices. This is required to passthrough 10 fsl-mc bus devices using the VFIO framework.
|
/openbmc/qemu/docs/system/devices/ |
H A D | usb.rst | 5 plug virtual USB devices or real host USB devices (only works with 7 connect virtual USB hubs as necessary to connect multiple USB devices. 23 XHCI supports USB 1.1, USB 2.0 and USB 3.0 devices, so this is the 26 need to use the bus= parameter when adding USB devices. 34 devices. The companion controller setup is more convenient to use 36 1.1 devices. See next section for details. 95 .. _Connecting USB devices: 97 Connecting USB devices 260 #. optionally add more devices (luns 1 ... 15) 265 Using host USB devices on a Linux host [all …]
|
/openbmc/qemu/docs/ |
H A D | pcie.txt | 7 devices in PCI Express based machines and explains the reasoning behind 41 not controllers. Place only legacy PCI devices on 48 strangely when PCI Express devices are integrated 81 A PCI Express Root bus supports up to 32 devices. Since each 92 Plug only PCI Express devices into PCI Express Ports. 190 PCI Express devices within PCI Express hierarchy. 207 devices to prevent bus number starvation. 217 that the command line sets for other pxb-pcie devices. 296 7. Virtio devices 302 to transitional virtio devices. [all …]
|
/openbmc/linux/Documentation/usb/ |
H A D | usbip_protocol.rst | 9 USB devices and the clients import them. The device driver for the exported 12 The client may ask for the list of the exported USB devices. To get the list the 16 the OP_REP_DEVLIST packet which lists the exported USB devices. Finally the 23 (imports USB devices) (exports USB devices) 32 Once the client knows the list of exported USB devices it may decide to use one 45 (imports USB devices) (exports USB devices) 96 (imports USB devices) (exports USB devices) 144 Retrieve the list of exported USB devices. 152 | | | | devices. | 158 Reply with the list of exported USB devices. [all …]
|
/openbmc/linux/Documentation/userspace-api/media/mediactl/ |
H A D | media-controller-intro.rst | 8 Media devices increasingly handle multiple related functions. Many USB 14 be modelled as separate devices. A USB camera with a microphone will be 15 presented to userspace applications as V4L2 and ALSA capture devices. 16 The devices' relationships (when using a webcam, end-users shouldn't 21 With more and more advanced SoC devices being introduced, the current 25 between seemingly unrelated devices.
|
/openbmc/linux/drivers/net/wireless/broadcom/b43/ |
H A D | Kconfig | 10 b43 is a driver for the Broadcom 43xx series wireless devices. 17 the old IEEE 802.11B devices. Old devices are supported by 21 IEEE 802.11G devices can talk to IEEE 802.11B AccessPoints. 81 Broadcom 43xx device support for Soft-MAC SDIO devices. 108 bool "Support for G-PHY (802.11g) devices" 117 bool "Support for N-PHY (the main 802.11n series) devices" 128 bool "Support for LP-PHY (low-power 802.11g) devices" 133 and embedded devices. It supports 802.11a/b/g 137 bool "Support for HT-PHY (high throughput 802.11n) devices" 144 bool "Support for LCN-PHY devices (BROKEN)" [all …]
|
/openbmc/linux/Documentation/driver-api/surface_aggregator/ |
H A D | overview.rst | 8 embedded controller (EC) on Microsoft Surface devices. It has been originally 9 introduced on 4th generation devices (Surface Pro 4, Surface Book 1), but 17 Not much is currently known about SAM on 4th generation devices (Surface Pro 20 Book 2, Surface Laptop 1) and later generation devices, SAM is responsible 28 restructured for 7th generation devices and on those, specifically Surface 34 5th and 6th generation devices, both battery and temperature information is 37 requests. On 7th generation devices, this additional layer is gone and these 38 devices require a driver hooking directly into the SAM interface. Equally, 39 on newer generations, less devices are declared in ACPI, making them a bit 41 Due to this, a SSAM bus and subsystem with client devices [all …]
|
/openbmc/linux/drivers/media/usb/dvb-usb/ |
H A D | dvb-usb-init.c | 219 for (j = 0; j < DVB_USB_ID_MAX_NUM && props->devices[i].cold_ids[j] != NULL; j++) { in dvb_usb_find_device() 220 …deb_info("check for cold %x %x\n", props->devices[i].cold_ids[j]->idVendor, props->devices[i].cold… in dvb_usb_find_device() 221 if (props->devices[i].cold_ids[j]->idVendor == le16_to_cpu(udev->descriptor.idVendor) && in dvb_usb_find_device() 222 props->devices[i].cold_ids[j]->idProduct == le16_to_cpu(udev->descriptor.idProduct)) { in dvb_usb_find_device() 224 desc = &props->devices[i]; in dvb_usb_find_device() 232 for (j = 0; j < DVB_USB_ID_MAX_NUM && props->devices[i].warm_ids[j] != NULL; j++) { in dvb_usb_find_device() 233 …deb_info("check for warm %x %x\n", props->devices[i].warm_ids[j]->idVendor, props->devices[i].warm… in dvb_usb_find_device() 234 if (props->devices[i].warm_ids[j]->idVendor == le16_to_cpu(udev->descriptor.idVendor) && in dvb_usb_find_device() 235 props->devices[i].warm_ids[j]->idProduct == le16_to_cpu(udev->descriptor.idProduct)) { in dvb_usb_find_device() 237 desc = &props->devices[i]; in dvb_usb_find_device()
|
/openbmc/linux/Documentation/driver-api/tty/ |
H A D | index.rst | 7 Teletypewriter (TTY) layer takes care of all those serial devices. Including 14 corresponding struct tty_port. These devices are maintained by a TTY driver 21 Every character received by the kernel (both from devices and users) is passed 46 layers first. Drivers for serial devices can often use one of these specific 47 layers to implement a serial driver. Only special devices should be handled 53 #. Create and register TTY devices as they are probed (probe function) 56 #. Remove devices as they are going away (remove function) 60 :doc:`tty_driver`. For the other two (devices handling), look into
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/multipath-tools/files/ |
H A D | multipath.conf.example | 8 ## By default, devices with vendor = "IBM" and product = "S/390.*" are 43 ## of how to blacklist devices by wwid. The 2 devnode lines are the 45 ## of devices, such as all scsi devices, you should use a devnode line. 46 ## However, if you want to blacklist specific devices, you should use 49 ## devnode lines are not recommended for blacklisting specific devices. 72 #devices {
|
/openbmc/linux/Documentation/devicetree/bindings/bus/ |
H A D | xlnx,versal-net-cdx.yaml | 10 CDX bus controller for AMD devices is implemented to dynamically 11 detect CDX bus and devices using the firmware. 12 The CDX bus manages multiple FPGA based hardware devices, which 14 devices. These FPGA based devices can be added/modified dynamically 17 All devices on the CDX bus will have a unique streamid (for IOMMU) 26 The msi-map property is used to associate the devices with the
|
/openbmc/linux/tools/testing/selftests/net/forwarding/ |
H A D | tsn_lib.sh | 113 if ! [ -d /sys/bus/cpu/devices/cpu${cpu}/cpufreq ]; then 122 cat /sys/bus/cpu/devices/cpu${cpu}/cpufreq/scaling_max_freq > \ 123 /sys/bus/cpu/devices/cpu${cpu}/cpufreq/scaling_min_freq 125 /sys/bus/cpu/devices/cpu${cpu}/cpufreq/scaling_governor 134 if ! [ -d /sys/bus/cpu/devices/cpu${cpu}/cpufreq ]; then 138 echo "${!freq}" > /sys/bus/cpu/devices/cpu${cpu}/cpufreq/scaling_min_freq 140 /sys/bus/cpu/devices/cpu${cpu}/cpufreq/scaling_governor
|
/openbmc/linux/Documentation/admin-guide/blockdev/drbd/ |
H A D | data-structure-v9.rst | 12 devices (aka volumes) and connections to other nodes ("peer nodes"). Each DRBD 30 In this table, horizontally, devices can be accessed from resources by their 34 devices, and from connections and devices to their resource. 37 devices can be accessed by their minor device number via the drbd_devices idr. 41 devices and connections; their lifetime is determined by the lifetime of the
|
/openbmc/u-boot/doc/ |
H A D | README.virtio | 9 devices, including supported boards, build instructions, driver details etc. 23 spec. While VirtIO devices are commonly implemented as PCI devices on x86, 24 embedded devices models like ARM/RISC-V, which does not normally come with 63 [*] PCI driver for virtio devices 75 VirtIO net and block devices on ARM. 83 On x86, command is slightly different to create PCI VirtIO devices. 116 virtio - virtio block devices sub-system 120 virtio info - show all available virtio block devices 128 To probe all the VirtIO devices, type: 196 for all virtio devices. [all …]
|