devices (reference) in projects: linux-4.4.14

Searched refs:devices (Results 1 – 200 of 1929) sorted by relevance

/linux-4.4.14/drivers/clk/qcom/
D	Kconfig	17 Support for the global clock controller on apq8084 devices. 18 Say Y if you want to use peripheral devices such as UART, SPI, 27 Support for the multimedia clock controller on apq8084 devices. 28 Say Y if you want to support multimedia devices such as display, 35 Support for the global clock controller on ipq806x devices. 36 Say Y if you want to use peripheral devices such as UART, SPI, 44 Support for the LPASS clock controller on ipq806x devices. 45 Say Y if you want to use audio devices such as i2s, pcm, 52 Support for the global clock controller on msm8660 devices. 53 Say Y if you want to use peripheral devices such as UART, SPI, [all …]
/linux-4.4.14/Documentation/ABI/testing/
D	sysfs-devices-memory	1 What: /sys/devices/system/memory 5 The /sys/devices/system/memory contains a snapshot of the 12 What: /sys/devices/system/memory/memoryX/removable 16 The file /sys/devices/system/memory/memoryX/removable 24 What: /sys/devices/system/memory/memoryX/phys_device 28 The file /sys/devices/system/memory/memoryX/phys_device 32 What: /sys/devices/system/memory/memoryX/phys_index 36 The file /sys/devices/system/memory/memoryX/phys_index 41 What: /sys/devices/system/memory/memoryX/state 45 The file /sys/devices/system/memory/memoryX/state [all …]
D	sysfs-bus-coresight-devices-etm4x	1 What: /sys/bus/coresight/devices/<memory_map>.etm/enable_source 11 What: /sys/bus/coresight/devices/<memory_map>.etm/cpu 17 What: /sys/bus/coresight/devices/<memory_map>.etm/nr_pe_cmp 24 What: /sys/bus/coresight/devices/<memory_map>.etm/nr_addr_cmp 31 What: /sys/bus/coresight/devices/<memory_map>.etm/nr_cntr 38 What: /sys/bus/coresight/devices/<memory_map>.etm/nr_ext_inp 44 What: /sys/bus/coresight/devices/<memory_map>.etm/numcidc 51 What: /sys/bus/coresight/devices/<memory_map>.etm/numvmidc 58 What: /sys/bus/coresight/devices/<memory_map>.etm/nrseqstate 65 What: /sys/bus/coresight/devices/<memory_map>.etm/nr_resource [all …]
D	sysfs-devices-soc	`1 What: /sys/devices/socX 5 The /sys/devices/ directory contains a sub-directory for each 11 about devices which are commonly contained in /sys/devices/platform. 13 devices would be better suited to appear as children of that SoC. 15 What: /sys/devices/socX/machine 22 What: /sys/devices/socX/family 29 What: /sys/devices/socX/soc_id 36 What: /sys/devices/socX/revision 43 What: /sys/devices/socX/process 55 expected under most buses. /sys/bus/soc/devices is of particular [all …]`
D	sysfs-bus-iio	1 What: /sys/bus/iio/devices/iio:deviceX 9 What: /sys/bus/iio/devices/triggerX 22 What: /sys/bus/iio/devices/iio:deviceX/buffer 28 What: /sys/bus/iio/devices/iio:deviceX/name 35 What: /sys/bus/iio/devices/iio:deviceX/sampling_frequency 36 What: /sys/bus/iio/devices/iio:deviceX/buffer/sampling_frequency 37 What: /sys/bus/iio/devices/triggerX/sampling_frequency 41 Some devices have internal clocks. This parameter sets the 42 resulting sampling frequency. In many devices this 50 What: /sys/bus/iio/devices/iio:deviceX/sampling_frequency_available [all …]
D	sysfs-bus-coresight-devices-etm3x	1 What: /sys/bus/coresight/devices/<memory_map>.[etm\|ptm]/enable_source 11 What: /sys/bus/coresight/devices/<memory_map>.[etm\|ptm]/addr_idx 18 What: /sys/bus/coresight/devices/<memory_map>.[etm\|ptm]/addr_acctype 29 What: /sys/bus/coresight/devices/<memory_map>.[etm\|ptm]/addr_range 37 What: /sys/bus/coresight/devices/<memory_map>.[etm\|ptm]/addr_single 45 What: /sys/bus/coresight/devices/<memory_map>.[etm\|ptm]/addr_start 53 What: /sys/bus/coresight/devices/<memory_map>.[etm\|ptm]/addr_stop 61 What: /sys/bus/coresight/devices/<memory_map>.[etm\|ptm]/cntr_idx 67 What: /sys/bus/coresight/devices/<memory_map>.[etm\|ptm]/cntr_event 74 What: /sys/bus/coresight/devices/<memory_map>.[etm\|ptm]/cntr_val [all …]
D	sysfs-bus-iio-frequency-ad9523	1 What: /sys/bus/iio/devices/iio:deviceX/pll2_feedback_clk_present 2 What: /sys/bus/iio/devices/iio:deviceX/pll2_reference_clk_present 3 What: /sys/bus/iio/devices/iio:deviceX/pll1_reference_clk_a_present 4 What: /sys/bus/iio/devices/iio:deviceX/pll1_reference_clk_b_present 5 What: /sys/bus/iio/devices/iio:deviceX/pll1_reference_clk_test_present 6 What: /sys/bus/iio/devices/iio:deviceX/vcxo_clk_present 14 What: /sys/bus/iio/devices/iio:deviceX/pllY_locked 21 What: /sys/bus/iio/devices/iio:deviceX/sync_dividers
D	sysfs-devices-power	1 What: /sys/devices/.../power/ 5 The /sys/devices/.../power directory contains attributes 9 What: /sys/devices/.../power/wakeup 13 The /sys/devices/.../power/wakeup attribute allows the user 19 Some devices support "wakeup" events, which are hardware signals 20 used to activate the system from a sleep state. Such devices 31 For the devices that are not capable of generating system wakeup 35 What: /sys/devices/.../power/control 39 The /sys/devices/.../power/control attribute allows the user 42 All devices have one of the following two values for the [all …]
D	sysfs-devices	`1 What: /sys/devices 5 The /sys/devices tree contains a snapshot of the 9 devices within this tree will change. 15 within the /sys/devices tree of the individual devices. 17 devices being added and removed from this tree to find 18 the location of those devices. 20 Note that sometimes not all devices along the directory`
D	sysfs-devices-lpss_ltr	1 What: /sys/devices/.../lpss_ltr/ 5 The /sys/devices/.../lpss_ltr/ directory is only present for 6 devices included into the Intel Lynxpoint Low Power Subsystem 10 What: /sys/devices/.../lpss_ltr/ltr_mode 14 The /sys/devices/.../lpss_ltr/ltr_mode attribute contains an 15 integer number (0 or 1) indicating whether or not the devices' 22 What: /sys/devices/.../lpss_ltr/auto_ltr 26 The /sys/devices/.../lpss_ltr/auto_ltr attribute contains the 34 What: /sys/devices/.../lpss_ltr/sw_ltr 38 The /sys/devices/.../lpss_ltr/auto_ltr attribute contains the
D	sysfs-devices-platform-sh_mobile_lcdc_fb	1 What: /sys/devices/platform/sh_mobile_lcdc_fb.[0-3]/graphics/fb[0-9]/ovl_alpha 5 This file is only available on fb[0-9] devices corresponding 12 What: /sys/devices/platform/sh_mobile_lcdc_fb.[0-3]/graphics/fb[0-9]/ovl_mode 16 This file is only available on fb[0-9] devices corresponding 25 What: /sys/devices/platform/sh_mobile_lcdc_fb.[0-3]/graphics/fb[0-9]/ovl_position 29 This file is only available on fb[0-9] devices corresponding 35 What: /sys/devices/platform/sh_mobile_lcdc_fb.[0-3]/graphics/fb[0-9]/ovl_rop3 39 This file is only available on fb[0-9] devices corresponding
D	sysfs-bus-event_source-devices-events	`1 What: /sys/devices/cpu/events/ 2 /sys/devices/cpu/events/branch-misses 3 /sys/devices/cpu/events/cache-references 4 /sys/devices/cpu/events/cache-misses 5 /sys/devices/cpu/events/stalled-cycles-frontend 6 /sys/devices/cpu/events/branch-instructions 7 /sys/devices/cpu/events/stalled-cycles-backend 8 /sys/devices/cpu/events/instructions 9 /sys/devices/cpu/events/cpu-cycles 30 What: /sys/bus/event_source/devices/<pmu>/events/<event> [all …]`
D	sysfs-bus-pci-devices-cciss	1 Where: /sys/bus/pci/devices/<dev>/ccissX/cXdY/model 8 Where: /sys/bus/pci/devices/<dev>/ccissX/cXdY/rev 15 Where: /sys/bus/pci/devices/<dev>/ccissX/cXdY/unique_id 22 Where: /sys/bus/pci/devices/<dev>/ccissX/cXdY/vendor 29 Where: /sys/bus/pci/devices/<dev>/ccissX/cXdY/block:cciss!cXdY 35 Where: /sys/bus/pci/devices/<dev>/ccissX/rescan 42 Where: /sys/bus/pci/devices/<dev>/ccissX/cXdY/lunid 49 Where: /sys/bus/pci/devices/<dev>/ccissX/cXdY/raid_level 56 Where: /sys/bus/pci/devices/<dev>/ccissX/cXdY/usage_count 63 Where: /sys/bus/pci/devices/<dev>/ccissX/resettable [all …]
D	sysfs-devices-system-cpu	`1 What: /sys/devices/system/cpu/ 10 /sys/devices/system/cpu/cpu#/ 12 What: /sys/devices/system/cpu/kernel_max 13 /sys/devices/system/cpu/offline 14 /sys/devices/system/cpu/online 15 /sys/devices/system/cpu/possible 16 /sys/devices/system/cpu/present 40 What: /sys/devices/system/cpu/probe 41 /sys/devices/system/cpu/release 56 What: /sys/devices/system/cpu/cpu#/node [all …]`
D	sysfs-platform-asus-laptop	`1 What: /sys/devices/platform/asus_laptop/display 16 What: /sys/devices/platform/asus_laptop/gps 24 What: /sys/devices/platform/asus_laptop/ledd 32 echo 0x0T000DDD > /sys/devices/platform/asus_laptop/ 36 What: /sys/devices/platform/asus_laptop/bluetooth 45 What: /sys/devices/platform/asus_laptop/wlan 54 What: /sys/devices/platform/asus_laptop/wimax 61 What: /sys/devices/platform/asus_laptop/wwan`
D	sysfs-bus-usb	1 What: /sys/bus/usb/devices/INTERFACE/authorized 14 What: /sys/bus/usb/devices/usbX/interface_authorized_default 26 Authorized devices are available for use by device 28 USB devices are authorized. 30 Certified Wireless USB devices are not authorized 39 For Certified Wireless USB devices only. 41 A devices's CDID, as 16 space-separated hex octets. 48 For Certified Wireless USB devices only. 59 For Certified Wireless USB devices only. 123 What: /sys/bus/usb/devices/.../power/usb2_hardware_lpm [all …]
D	sysfs-driver-hid	`1 What: For USB devices : /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-b… 2 …For BT devices : /sys/class/bluetooth/hci<addr>/<hid-bus>:<vendor-id>:<product-id>.<num>/report_de… 12 What: For USB devices : /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-b… 13 For BT devices : /sys/class/bluetooth/hci<addr>/<hid-bus>:<vendor-id>:<product-id>.<num>/country`
D	sysfs-platform-ts5500	`1 What: /sys/devices/platform/ts5500/adc 9 What: /sys/devices/platform/ts5500/ereset 17 What: /sys/devices/platform/ts5500/id 24 What: /sys/devices/platform/ts5500/jumpers 33 What: /sys/devices/platform/ts5500/name 40 What: /sys/devices/platform/ts5500/rs485 48 What: /sys/devices/platform/ts5500/sram`
D	sysfs-bus-acpi	`1 What: /sys/bus/acpi/devices/.../path 12 What: /sys/bus/acpi/devices/.../modalias 20 What: /sys/bus/acpi/devices/.../hid 29 What: /sys/bus/acpi/devices/.../description 36 What: /sys/bus/acpi/devices/.../adr 42 objects representing devices having standard enumeration 45 What: /sys/bus/acpi/devices/.../uid 52 What: /sys/bus/acpi/devices/.../eject`
D	sysfs-bus-intel_th-devices-gth	`1 What: /sys/bus/intel_th/devices/<intel_th_id>-gth/masters/* 8 What: /sys/bus/intel_th/devices/<intel_th_id>-gth/outputs/[0-7]_port 18 What: /sys/bus/intel_th/devices/<intel_th_id>-gth/outputs/[0-7]_drop 25 What: /sys/bus/intel_th/devices/<intel_th_id>-gth/outputs/[0-7]_null 31 What: /sys/bus/intel_th/devices/<intel_th_id>-gth/outputs/[0-7]_flush 38 What: /sys/bus/intel_th/devices/<intel_th_id>-gth/outputs/[0-7]_reset 44 What: /sys/bus/intel_th/devices/<intel_th_id>-gth/outputs/[0-7]_smcfreq`
D	sysfs-driver-toshiba_acpi	1 What: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/kbd_backlight_mode 14 Also note that toggling this value on type 1 devices, requires 18 What: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/kbd_backlight_timeout 31 What: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/position 38 What: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/touchpad 48 What: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/available_kbd_modes 62 What: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/kbd_type 72 What: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/usb_sleep_charge 89 What: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/sleep_functions_on_battery 105 What: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/usb_rapid_charge [all …]
D	sysfs-platform-msi-laptop	`1 What: /sys/devices/platform/msi-laptop-pf/lcd_level 8 What: /sys/devices/platform/msi-laptop-pf/auto_brightness 17 What: /sys/devices/platform/msi-laptop-pf/wlan 24 What: /sys/devices/platform/msi-laptop-pf/bluetooth 33 What: /sys/devices/platform/msi-laptop-pf/touchpad 41 What: /sys/devices/platform/msi-laptop-pf/turbo_mode 54 What: /sys/devices/platform/msi-laptop-pf/eco_mode 64 What: /sys/devices/platform/msi-laptop-pf/turbo_cooldown 75 What: /sys/devices/platform/msi-laptop-pf/auto_fan`
D	sysfs-platform-asus-wmi	`1 What: /sys/devices/platform/<platform>/cpufv 12 What: /sys/devices/platform/<platform>/camera 19 What: /sys/devices/platform/<platform>/cardr 26 What: /sys/devices/platform/<platform>/touchpad 33 What: /sys/devices/platform/<platform>/lid_resume`
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 …]
D	sysfs-bus-pci	10 found in /sys/bus/pci/devices/. For example: 23 found in /sys/bus/pci/devices/. For example: 66 re-discover previously removed devices. 68 What: /sys/bus/pci/devices/.../msi_bus 75 drivers of all child devices under the bridge. Drivers 78 What: /sys/bus/pci/devices/.../msi_irqs/ 82 The /sys/devices/.../msi_irqs directory contains a variable set 86 What: /sys/bus/pci/devices/.../msi_irqs/<N> 93 What: /sys/bus/pci/devices/.../remove 100 What: /sys/bus/pci/devices/.../pci_bus/.../rescan [all …]
D	sysfs-devices-firmware_node	`1 What: /sys/devices/.../firmware_node/ 5 The /sys/devices/.../firmware_node directory contains attributes 9 What: /sys/devices/.../firmware_node/description 13 The /sys/devices/.../firmware/description attribute contains a string`
D	sysfs-bus-event_source-devices-hv_gpci	`1 What: /sys/bus/event_source/devices/hv_gpci/interface/collect_privileged 10 What: /sys/bus/event_source/devices/hv_gpci/interface/ga 17 What: /sys/bus/event_source/devices/hv_gpci/interface/expanded 24 What: /sys/bus/event_source/devices/hv_gpci/interface/lab 31 What: /sys/bus/event_source/devices/hv_gpci/interface/version 38 What: /sys/bus/event_source/devices/hv_gpci/interface/kernel_version`
D	sysfs-driver-wacom	1 What: /sys/bus/hid/devices/<bus>:<vid>:<pid>.<n>/speed 6 The /sys/bus/hid/devices/<bus>:<vid>:<pid>.<n>/speed file 12 What: /sys/bus/hid/devices/<bus>:<vid>:<pid>.<n>/wacom_led/led 23 What: /sys/bus/hid/devices/<bus>:<vid>:<pid>.<n>/wacom_led/status0_luminance 32 What: /sys/bus/hid/devices/<bus>:<vid>:<pid>.<n>/wacom_led/status1_luminance 40 What: /sys/bus/hid/devices/<bus>:<vid>:<pid>.<n>/wacom_led/status_led0_select 49 What: /sys/bus/hid/devices/<bus>:<vid>:<pid>.<n>/wacom_led/status_led1_select 57 What: /sys/bus/hid/devices/<bus>:<vid>:<pid>.<n>/wacom_led/buttons_luminance 64 What: /sys/bus/hid/devices/<bus>:<vid>:<pid>.<n>/wacom_led/button<n>_rawimg 81 What: /sys/bus/hid/devices/<bus>:<vid>:<pid>.<n>/wacom_remote/unpair_remote [all …]
D	sysfs-platform-eeepc-laptop	`1 What: /sys/devices/platform/eeepc/disp 12 What: /sys/devices/platform/eeepc/camera 19 What: /sys/devices/platform/eeepc/cardr 26 What: /sys/devices/platform/eeepc/cpufv 45 What: /sys/devices/platform/eeepc/available_cpufv`
D	sysfs-bus-usb-lvstest	`5 What: /sys/bus/usb/devices/.../get_dev_desc 12 What: /sys/bus/usb/devices/.../u1_timeout 20 What: /sys/bus/usb/devices/.../u2_timeout 28 What: /sys/bus/usb/devices/.../hot_reset 35 What: /sys/bus/usb/devices/.../u3_entry 42 What: /sys/bus/usb/devices/.../u3_exit`
D	sysfs-bus-mei	`1 What: /sys/bus/mei/devices/.../modalias 9 What: /sys/bus/mei/devices/.../name 16 What: /sys/bus/mei/devices/.../uuid 23 What: /sys/bus/mei/devices/.../version`
D	sysfs-bus-bcma	`1 What: /sys/bus/bcma/devices/.../manuf 9 What: /sys/bus/bcma/devices/.../id 17 What: /sys/bus/bcma/devices/.../rev 25 What: /sys/bus/bcma/devices/.../class`
D	sysfs-bus-coresight-devices-etb10	`1 What: /sys/bus/coresight/devices/<memory_map>.etb/enable_sink 7 ex: echo 1 > /sys/bus/coresight/devices/20010000.etb/enable_sink 9 What: /sys/bus/coresight/devices/<memory_map>.etb/status 16 What: /sys/bus/coresight/devices/<memory_map>.etb/trigger_cntr`
D	sysfs-driver-samsung-laptop	`1 What: /sys/devices/platform/samsung/performance_level 21 What: /sys/devices/platform/samsung/battery_life_extender 31 What: /sys/devices/platform/samsung/usb_charge 35 Description: Use your USB ports to charge devices, even 39 What: /sys/devices/platform/samsung/lid_handling`
D	sysfs-driver-hid-lenovo	1 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 9 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 16 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 23 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 31 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 38 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 45 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p…
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.`
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`
D	sysfs-bus-event_source-devices-hv_24x7	`1 What: /sys/bus/event_source/devices/hv_24x7/interface/catalog 11 What: /sys/bus/event_source/devices/hv_24x7/interface/catalog_length 18 What: /sys/bus/event_source/devices/hv_24x7/interface/catalog_version 25 What: /sys/bus/event_source/devices/hv_24x7/event_descs/<event-name> 36 What: /sys/bus/event_source/devices/hv_24x7/event_long_descs/<event-name>`
D	sysfs-devices-system-xen_cpu	`1 What: /sys/devices/system/xen_cpu/ 9 /sys/devices/system/xen_cpu/xen_cpu#/ 12 What: /sys/devices/system/xen_cpu/xen_cpu#/online`
D	sysfs-bus-i2c-devices-hm6352	`1 Where: /sys/bus/i2c/devices/.../heading0_input 8 Where: /sys/bus/i2c/devices/.../power_state 15 Where: /sys/bus/i2c/devices/.../calibration`
D	sysfs-bus-iio-trigger-sysfs	`1 What: /sys/bus/iio/devices/triggerX/trigger_now 13 What: /sys/bus/iio/devices/triggerX/name 20 /sys/bus/iio/devices/iio:deviceY/trigger/current_trigger. 22 What: /sys/bus/iio/devices/iio_sysfs_trigger/add_trigger 33 What: /sys/bus/iio/devices/iio_sysfs_trigger/remove_trigger`
D	sysfs-class-mtd	16 physical/simulated flash devices, partitions on a flash 17 device, or concatenated flash devices. 81 For devices that have variable eraseblock sizes, this 134 In the case of devices lacking any ECC capability, it is 0. 166 a persistent return value of -EUCLEAN on devices where sticky 172 This is generally applicable only to NAND flash devices with ECC 173 capability. It is ignored on devices lacking ECC capability; 174 i.e., devices for which ecc_strength is zero. 186 devices lacking any ECC capability, it is 0. 197 devices lacking any ECC capability, it is 0. [all …]
D	sysfs-bus-iio-mpu6050	`1 What: /sys/bus/iio/devices/iio:deviceX/in_gyro_matrix 2 What: /sys/bus/iio/devices/iio:deviceX/in_accel_matrix 3 What: /sys/bus/iio/devices/iio:deviceX/in_magn_matrix`
D	sysfs-bus-intel_th-devices-pti	`1 What: /sys/bus/intel_th/devices/<intel_th_id>-pti/mode 8 What: /sys/bus/intel_th/devices/<intel_th_id>-pti/freerunning_clock 16 What: /sys/bus/intel_th/devices/<intel_th_id>-pti/clock_divider`
D	sysfs-devices-power_state	`1 What: /sys/devices/.../power_state 5 The /sys/devices/.../power_state attribute is only present for 18 some other devices using them at the moment.`
D	sysfs-bus-mdio	`1 What: /sys/bus/mdio_bus/devices/.../phy_id 11 What: /sys/bus/mdio_bus/devices/.../phy_interface 21 What: /sys/bus/mdio_bus/devices/.../phy_has_fixups`
/linux-4.4.14/Documentation/s390/
D	CommonIO	15 The given devices will be ignored by the common I/O-layer; no detection 16 and device sensing will be done on any of those devices. The subchannel to 23 The devices must be given either as bus ids (0.x.abcd) or as hexadecimal 27 You can use the 'all' keyword to ignore all devices. The 'ipldev' and 'condev' 35 will ignore all devices ranging from 0.0.0023 to 0.0.0042 and the device 39 will ignore all devices but 0.0.4711, 0.0.fd00, 0.0.fd01, 0.0.fd02. 41 By default, no devices are ignored. 49 Lists the ranges of devices (by bus id) which are ignored by common I/O. 51 You can un-ignore certain or all devices by piping to /proc/cio_ignore. 52 "free all" will un-ignore all ignored devices, [all …]
D	driver-model.txt	`4 1. CCW devices 7 All devices which can be addressed by means of ccws are called 'CCW devices' - 10 All ccw devices are accessed via a subchannel, this is reflected in the 11 structures under devices/: 13 devices/ 28 system; it is a pseudo subchannel where disconnected ccw devices are moved to 30 former subchannel. The ccw devices will be moved again to a proper subchannel 34 be found under bus/ccw/devices/. 36 All ccw devices export some data via sysfs. 43 disconnected devices. [all …]`
/linux-4.4.14/Documentation/ABI/stable/
D	sysfs-devices-node	`1 What: /sys/devices/system/node/possible 7 What: /sys/devices/system/node/online 13 What: /sys/devices/system/node/has_normal_memory 19 What: /sys/devices/system/node/has_cpu 25 What: /sys/devices/system/node/has_high_memory 32 What: /sys/devices/system/node/nodeX 40 What: /sys/devices/system/node/nodeX/cpumap 46 What: /sys/devices/system/node/nodeX/cpulist 52 What: /sys/devices/system/node/nodeX/meminfo 59 What: /sys/devices/system/node/nodeX/numastat [all …]`
D	sysfs-bus-xen-backend	1 What: /sys/bus/xen-backend/devices//devtype 9 What: /sys/bus/xen-backend/devices//nodename 17 What: /sys/bus/xen-backend/devices/vbd-/physical_device 26 What: /sys/bus/xen-backend/devices/vbd-/mode 34 What: /sys/bus/xen-backend/devices/vbd-/statistics/f_req 41 What: /sys/bus/xen-backend/devices/vbd-/statistics/oo_req 49 What: /sys/bus/xen-backend/devices/vbd-/statistics/rd_req 56 What: /sys/bus/xen-backend/devices/vbd-/statistics/rd_sect 63 What: /sys/bus/xen-backend/devices/vbd-/statistics/wr_req 70 What: /sys/bus/xen-backend/devices/vbd-/statistics/wr_sect
D	sysfs-devices-system-xen_memory	1 What: /sys/devices/system/xen_memory/xen_memory0/max_retry_count 11 What: /sys/devices/system/xen_memory/xen_memory0/max_schedule_delay 19 What: /sys/devices/system/xen_memory/xen_memory0/retry_count 30 What: /sys/devices/system/xen_memory/xen_memory0/schedule_delay 41 What: /sys/devices/system/xen_memory/xen_memory0/target 49 What: /sys/devices/system/xen_memory/xen_memory0/target_kb 56 What: /sys/devices/system/xen_memory/xen_memory0/info/current_kb 64 What: /sys/devices/system/xen_memory/xen_memory0/info/high_kb 71 What: /sys/devices/system/xen_memory/xen_memory0/info/low_kb
D	sysfs-bus-usb	1 What: /sys/bus/usb/devices/.../power/persist 14 What: /sys/bus/usb/devices/.../power/autosuspend 27 The autosuspend delay for newly-created devices is set to 61 What: /sys/bus/usb/devices/<busnum>-<port[.port]>...:<config num>-<interface num>/supports_autosus… 84 such devices. 88 What: /sys/bus/usb/devices/.../devnum 95 What: /sys/bus/usb/devices/.../bConfigurationValue 103 Note that some devices, in violation of the USB spec, have a 105 bConfigurationValue for these devices will install that 112 What: /sys/bus/usb/devices/.../busnum [all …]
D	sysfs-bus-vmbus	`1 What: /sys/bus/vmbus/devices/vmbus_/id 8 What: /sys/bus/vmbus/devices/vmbus_/class_id 15 What: /sys/bus/vmbus/devices/vmbus_/device_id 22 What: /sys/bus/vmbus/devices/vmbus_/channel_vp_mapping`
D	sysfs-bus-firewire	`1 What: /sys/bus/firewire/devices/fw[0-9]+/ 20 What: /sys/bus/firewire/devices/fw[0-9]+/units 42 What: /sys/bus/firewire/devices/fw[0-9]+/is_local 53 What: /sys/bus/firewire/devices/fw[0-9]+[.][0-9]+/ 71 What: /sys/bus/firewire/devices/*/ 76 Attributes common to IEEE 1394 node devices and unit devices.`
/linux-4.4.14/Documentation/usb/
D	authorization.txt	2 Authorizing (or not) your USB devices to connect to the system 8 of USB devices, fully controlled by user space. 19 $ echo 1 > /sys/bus/usb/devices/DEVICE/authorized 23 $ echo 0 > /sys/bus/usb/devices/DEVICE/authorized 25 Set new devices connected to hostX to be deauthorized by default (ie: 28 $ echo 0 > /sys/bus/usb/devices/usbX/authorized_default 32 $ echo 1 > /sys/bus/usb/devices/usbX/authorized_default 34 By default, Wired USB devices are authorized by default to 36 devices (this is so because we need to do an authentication phase 43 Imagine you want to implement a lockdown so only devices of type XYZ [all …]
D	chipidea.txt	27 echo 1 > /sys/bus/platform/devices/ci_hdrc.0/inputs/b_bus_req 31 echo 0 > /sys/bus/platform/devices/ci_hdrc.0/inputs/a_bus_req 37 echo 0 > /sys/bus/platform/devices/ci_hdrc.0/inputs/b_bus_req 49 echo 0 > /sys/bus/platform/devices/ci_hdrc.0/inputs/a_bus_drop 50 echo 1 > /sys/bus/platform/devices/ci_hdrc.0/inputs/a_bus_req 54 echo 1 > /sys/bus/platform/devices/ci_hdrc.0/inputs/b_bus_req 58 echo 1 > /sys/bus/platform/devices/ci_hdrc.0/inputs/a_bus_drop 64 echo 1 > /sys/bus/platform/devices/ci_hdrc.0/inputs/b_bus_req 79 echo enabled > /sys/bus/platform/devices/ci_hdrc.0/power/wakeup 81 echo enabled > /sys/bus/platform/devices/2184000.usb/power/wakeup [all …]
D	proc_usb_info.txt	6 The usbfs filesystem for USB devices is traditionally mounted at 7 /proc/bus/usb. It provides the /proc/bus/usb/devices file, as well as 12 "devices" file is available in debugfs, typically as 13 /sys/kernel/debug/usb/devices. 27 You can then issue `cat /proc/bus/usb/devices` to extract 29 to interact with USB devices. 49 you can't rely on them for stable access to devices. For example, 50 it's relatively common for devices to re-enumerate while they are 63 in text form by the /proc/bus/usb/devices file, described later. 66 devices. You would open the /proc/bus/usb/BBB/DDD file read/write, [all …]
D	ehci.txt	3 The EHCI driver is used to talk to high speed USB 2.0 devices using 11 USB 1.1 only addressed full speed and low speed. High speed devices 14 USB 1.1 devices may also be used on USB 2.0 systems. When plugged 17 such devices. When USB 1.1 devices plug into USB 2.0 hubs, they 27 While usb-storage devices have been available since mid-2001 (working 29 been available since late 2001, and other kinds of high speed devices 53 and interrupt transfers, including requests to USB 1.1 devices through 63 most USB audio and video devices can't be connected to high speed buses. 72 The EHCI root hub code hands off USB 1.1 devices to its companion 100 take over (at lower speed) all the devices that were previously handled [all …]
D	persist.txt	12 is so that devices can maintain their internal state and hubs can 13 detect connect-change events (devices being plugged in or unplugged). 25 wakes up all the devices attached to that controller are treated as 29 For many sorts of devices this behavior doesn't matter in the least. 36 devices. The effect is exactly the same as if the device really had 49 it's as though you had unplugged all the USB devices. Yes, it's 75 to each of the USB devices below that controller for which the 101 devices for which it is enabled. You can enable the feature by doing 104 echo 1 >/sys/bus/usb/devices/.../power/persist 110 devices where it really matters. [all …]
/linux-4.4.14/Documentation/devicetree/bindings/arm/omap/
D	timer.txt	`5 OMAP44xx devices have timer instances that are 100% 6 register compatible with OMAP3xxx devices as well as 8 So for OMAP44xx devices timer instances may use 11 ti,omap2420-timer (applicable to OMAP24xx devices) 12 ti,omap3430-timer (applicable to OMAP3xxx/44xx devices) 13 ti,omap4430-timer (applicable to OMAP44xx devices) 14 ti,omap5430-timer (applicable to OMAP543x devices) 15 ti,am335x-timer (applicable to AM335x devices) 16 ti,am335x-timer-1ms (applicable to AM335x devices)`
/linux-4.4.14/drivers/gpu/drm/amd/amdgpu/
D	amdgpu_encoders.c	48 if (amdgpu_encoder->devices & amdgpu_connector->devices) { in amdgpu_link_encoder_connector() 50 if (amdgpu_encoder->devices & (ATOM_DEVICE_LCD_SUPPORT)) { in amdgpu_link_encoder_connector() 68 amdgpu_encoder->active_device = amdgpu_encoder->devices & amdgpu_connector->devices; in amdgpu_encoder_set_active_device() 70 amdgpu_encoder->active_device, amdgpu_encoder->devices, in amdgpu_encoder_set_active_device() 71 amdgpu_connector->devices, encoder->encoder_type); in amdgpu_encoder_set_active_device() 86 if (amdgpu_encoder->active_device & amdgpu_connector->devices) in amdgpu_get_connector_for_encoder() 102 if (amdgpu_encoder->devices & amdgpu_connector->devices) in amdgpu_get_connector_for_encoder_init() 123 (amdgpu_encoder->devices & other_amdgpu_encoder->devices)) in amdgpu_get_external_encoder()
D	atombios_encoders.c	90 if ((amdgpu_encoder->devices & (ATOM_DEVICE_LCD_SUPPORT)) && in amdgpu_atombios_encoder_set_backlight_level() 846 else if (amdgpu_encoder->devices & (ATOM_DEVICE_DFP_SUPPORT)) { in amdgpu_atombios_encoder_setup_dig_transmitter() 888 } else if (amdgpu_encoder->devices & (ATOM_DEVICE_DFP_SUPPORT)) { in amdgpu_atombios_encoder_setup_dig_transmitter() 947 else if (amdgpu_encoder->devices & (ATOM_DEVICE_DFP_SUPPORT)) { in amdgpu_atombios_encoder_setup_dig_transmitter() 1009 else if (amdgpu_encoder->devices & (ATOM_DEVICE_DFP_SUPPORT)) { in amdgpu_atombios_encoder_setup_dig_transmitter() 1062 else if (amdgpu_encoder->devices & (ATOM_DEVICE_DFP_SUPPORT)) { in amdgpu_atombios_encoder_setup_dig_transmitter() 1285 if (amdgpu_encoder->devices & (ATOM_DEVICE_LCD_SUPPORT)) in amdgpu_atombios_encoder_setup_dig() 1296 if (amdgpu_encoder->devices & (ATOM_DEVICE_LCD_SUPPORT)) in amdgpu_atombios_encoder_setup_dig() 1323 amdgpu_encoder->encoder_id, mode, amdgpu_encoder->devices, in amdgpu_atombios_encoder_dpms() 1406 if (amdgpu_encoder->devices & ATOM_DEVICE_LCD1_SUPPORT) in amdgpu_atombios_encoder_set_crtc_source() [all …]
D	amdgpu_display.c	384 uint32_t devices; in amdgpu_print_display_setup() local 424 devices = amdgpu_encoder->devices & amdgpu_connector->devices; in amdgpu_print_display_setup() 425 if (devices) { in amdgpu_print_display_setup() 426 if (devices & ATOM_DEVICE_CRT1_SUPPORT) in amdgpu_print_display_setup() 428 if (devices & ATOM_DEVICE_CRT2_SUPPORT) in amdgpu_print_display_setup() 430 if (devices & ATOM_DEVICE_LCD1_SUPPORT) in amdgpu_print_display_setup() 432 if (devices & ATOM_DEVICE_DFP1_SUPPORT) in amdgpu_print_display_setup() 434 if (devices & ATOM_DEVICE_DFP2_SUPPORT) in amdgpu_print_display_setup() 436 if (devices & ATOM_DEVICE_DFP3_SUPPORT) in amdgpu_print_display_setup() 438 if (devices & ATOM_DEVICE_DFP4_SUPPORT) in amdgpu_print_display_setup() [all …]
/linux-4.4.14/Documentation/cgroups/
D	devices.txt	15 devices from the whitelist or add new entries. A child cgroup can 20 An entry is added using devices.allow, and removed using 21 devices.deny. For instance 23 echo 'c 1:3 mr' > /sys/fs/cgroup/1/devices.allow 28 echo a > /sys/fs/cgroup/1/devices.deny 32 echo a > /sys/fs/cgroup/1/devices.allow 56 a cgroup's devices.deny file, all its children will have that entry removed 71 # echo "c 116:* r" > A/devices.deny 75 group whitelist entries denied devices 87 group whitelist entries denied devices [all …]
/linux-4.4.14/Documentation/
D	sysfs-rules.txt	37 - devices are only "devices" 38 There is no such thing like class-, bus-, physical devices, 42 applications that look for devices in sysfs. 45 o devpath (/devices/pci0000:00/0000:00:1d.1/usb2/2-2/2-2:1.0) 52 pointing to /sys/devices must always be resolved to their real 74 - devices which do not have "driver"-link just do not have a 87 - Properties of parent devices never belong into a child device. 88 Always look at the parent devices themselves for determining device 97 and this is below: /sys/devices. 102 There are currently three places for classification of devices: [all …]
D	video-output.txt	`9 laptop, The ACPI video driver registered its output devices and read/write 15 \| \|-- device -> ../../../devices/pci0000:00/0000:00:01.0 20 \| \|-- device -> ../../../devices/pci0000:00/0000:00:01.0 25 \| \|-- device -> ../../../devices/pci0000:00/0000:00:01.0 30 \|-- device -> ../../../devices/pci0000:00/0000:00:01.0`
D	Intel-IOMMU.txt	15 ZLR - Zero length reads from PCI devices 22 device scope relationships between PCI devices and which DMA engine controls 28 There are some devices the BIOS controls, for e.g USB devices to perform 29 PS2 emulation. The regions of memory used for these devices are marked 32 devices that need to access these regions. OS is expected to setup 33 unity mappings for these regions for these devices to access these regions. 44 share the virtual address with all devices under the p2p bridge due to 57 If you encounter issues with graphics devices, you can try adding 109 - For compatibility testing, could use unity map domain for all devices, just 110 provide a 1-1 for all useful memory under a single domain for all devices.
D	cputopology.txt	5 1) /sys/devices/system/cpu/cpuX/topology/physical_package_id: 11 2) /sys/devices/system/cpu/cpuX/topology/core_id: 17 3) /sys/devices/system/cpu/cpuX/topology/book_id: 23 4) /sys/devices/system/cpu/cpuX/topology/thread_siblings: 28 5) /sys/devices/system/cpu/cpuX/topology/thread_siblings_list: 33 6) /sys/devices/system/cpu/cpuX/topology/core_siblings: 38 7) /sys/devices/system/cpu/cpuX/topology/core_siblings_list: 43 8) /sys/devices/system/cpu/cpuX/topology/book_siblings: 48 9) /sys/devices/system/cpu/cpuX/topology/book_siblings_list: 83 /sys/devices/system/cpu and includes these files. The internal
D	dcdbas.txt	`29 /sys/devices/platform/dcdbas/smi_data 30 /sys/devices/platform/dcdbas/smi_data_buf_phys_addr 31 /sys/devices/platform/dcdbas/smi_data_buf_size 32 /sys/devices/platform/dcdbas/smi_request 56 /sys/devices/platform/dcdbas/host_control_action 57 /sys/devices/platform/dcdbas/host_control_smi_type 58 /sys/devices/platform/dcdbas/host_control_on_shutdown`
D	men-chameleon-bus.txt	31 based devices. 35 The current implementation is limited to PCI and PCIe based carrier devices 38 - Multi-resource MCB devices like the VME Controller or M-Module carrier. 39 - MCB devices that need another MCB device, like SRAM for a DMA Controller's 41 - A per-carrier IRQ domain for carrier devices that have one (or more) IRQs 55 Elektronik GmbH. These devices are multi-function devices implemented in a 78 possible future variant. While parsing the table's entries new MCB devices 81 MCB devices are registered at the MCB and thus at the driver core of the 133 When a driver is loaded and the MCB devices it services are found, the MCB
D	vfio.txt	4 to help ensure I/O devices behave within the boundaries they've been 45 meant for translation (ie. solving the addressing problems of devices 46 with limited address spaces). With this, devices can now be isolated 48 things like secure direct assignment of devices into virtual machines. 51 though. Even when an IOMMU is capable of this, properties of devices, 55 between devices within the enclosure, the enclosure may not require 56 transactions between devices to reach the IOMMU. Examples of this 60 can also play a factor in terms of hiding devices. A PCIe-to-PCI 61 bridge masks the devices behind it, making transaction appear as if 68 a set of devices which is isolatable from all other devices in the [all …]
/linux-4.4.14/drivers/staging/iio/Documentation/
D	sysfs-bus-iio-light	2 What: /sys/bus/iio/devices/device[n]/range 9 What: /sys/bus/iio/devices/device[n]/range_available 15 What: /sys/bus/iio/devices/device[n]/adc_resolution 22 What: /sys/bus/iio/devices/device[n]/adc_resolution_available 29 What: /sys/bus/iio/devices/device[n]/in_illuminance0[_input\|_raw] 48 What: /sys/bus/iio/devices/device[n]/in_proximity[_input\|_raw] 57 What: /sys/bus/iio/devices/device[n]/intensity_infrared[_input\|_raw] 66 What: /sys/bus/iio/devices/device[n]/in_illuminance0_target 73 What: /sys/bus/iio/devices/device[n]/in_illuminance0_integration_time 79 What: /sys/bus/iio/devices/device[n]/in_illuminance0_lux_table [all …]
D	sysfs-bus-iio-dds	2 What: /sys/bus/iio/devices/.../out_altvoltageX_frequencyY 13 What: /sys/bus/iio/devices/.../out_altvoltageX_frequencyY_scale 22 What: /sys/bus/iio/devices/.../out_altvoltageX_frequencysymbol 32 What: /sys/bus/iio/devices/.../out_altvoltageX_phaseY 43 What: /sys/bus/iio/devices/.../out_altvoltageX_phaseY_scale 52 What: /sys/bus/iio/devices/.../out_altvoltageX_phasesymbol 61 What: /sys/bus/iio/devices/.../out_altvoltageX_pincontrol_en 62 What: /sys/bus/iio/devices/.../out_altvoltageX_pincontrol_frequency_en 63 What: /sys/bus/iio/devices/.../out_altvoltageX_pincontrol_phase_en 74 What: /sys/bus/iio/devices/.../out_altvoltageX_out_enable [all …]
D	sysfs-bus-iio-impedance-analyzer-ad5933	`1 What: /sys/bus/iio/devices/iio:deviceX/outY_freq_start 7 What: /sys/bus/iio/devices/iio:deviceX/outY_freq_increment 14 What: /sys/bus/iio/devices/iio:deviceX/outY_freq_points 23 What: /sys/bus/iio/devices/iio:deviceX/outY_settling_cycles`
D	sysfs-bus-iio-light-tsl2583	`1 What: /sys/bus/iio/devices/device[n]/lux_table 8 What: /sys/bus/iio/devices/device[n]/illuminance0_calibrate 15 What: /sys/bus/iio/devices/device[n]/illuminance0_input_target`
/linux-4.4.14/drivers/bluetooth/
D	Kconfig	27 This driver is required if you want to use Bluetooth devices with 30 Say Y here to compile support for Bluetooth USB devices into the 63 Say Y here to compile support for Bluetooth SDIO devices into the 71 This driver is required if you want to use Bluetooth devices with 73 UART based Bluetooth PCMCIA and CF devices like Xircom Credit Card 76 Say Y here to compile support for Bluetooth UART devices into the 84 device and host. This protocol is required for most Bluetooth devices 96 USB Bluetooth devices based on CSR BlueCore chip, including PCMCIA and 107 communication between host and Atheros AR300x Bluetooth devices. 120 serial Bluetooth devices that are based on Texas Instruments' [all …]
/linux-4.4.14/drivers/vfio/platform/
D	Kconfig	`2 tristate "VFIO support for platform devices" 6 Support for platform devices with VFIO. This is required to make 7 use of platform devices present on the system using the VFIO 13 tristate "VFIO support for AMBA devices" 16 Support for ARM AMBA devices with VFIO. This is required to make 17 use of ARM AMBA devices present on the system using the VFIO`
/linux-4.4.14/drivers/gpu/drm/radeon/
D	radeon_encoders.c	53 if (radeon_encoder->devices & ATOM_DEVICE_LCD_SUPPORT) in radeon_encoder_clones() 56 if (radeon_encoder->devices & ATOM_DEVICE_DFP2_SUPPORT) in radeon_encoder_clones() 66 if (radeon_clone->devices & (ATOM_DEVICE_LCD_SUPPORT)) in radeon_encoder_clones() 68 if (radeon_clone->devices & ATOM_DEVICE_DFP2_SUPPORT) in radeon_encoder_clones() 168 if (!(radeon_encoder->devices & (ATOM_DEVICE_LCD_SUPPORT))) in radeon_encoder_add_backlight() 213 if (radeon_encoder->devices & radeon_connector->devices) { in radeon_link_encoder_connector() 215 if (radeon_encoder->devices & (ATOM_DEVICE_LCD_SUPPORT)) in radeon_link_encoder_connector() 231 radeon_encoder->active_device = radeon_encoder->devices & radeon_connector->devices; in radeon_encoder_set_active_device() 233 radeon_encoder->active_device, radeon_encoder->devices, in radeon_encoder_set_active_device() 234 radeon_connector->devices, encoder->encoder_type); in radeon_encoder_set_active_device() [all …]
D	atombios_encoders.c	99 if ((radeon_encoder->devices & (ATOM_DEVICE_LCD_SUPPORT)) && in atombios_set_backlight_level() 586 if (radeon_encoder->devices & (ATOM_DEVICE_LCD_SUPPORT)) in atombios_digital_setup() 606 if (radeon_encoder->devices & (ATOM_DEVICE_LCD_SUPPORT)) { in atombios_digital_setup() 635 if (radeon_encoder->devices & (ATOM_DEVICE_LCD_SUPPORT)) { in atombios_digital_setup() 1135 else if (radeon_encoder->devices & (ATOM_DEVICE_DFP_SUPPORT)) { in atombios_dig_transmitter_setup2() 1177 } else if (radeon_encoder->devices & (ATOM_DEVICE_DFP_SUPPORT)) { in atombios_dig_transmitter_setup2() 1236 else if (radeon_encoder->devices & (ATOM_DEVICE_DFP_SUPPORT)) { in atombios_dig_transmitter_setup2() 1298 else if (radeon_encoder->devices & (ATOM_DEVICE_DFP_SUPPORT)) { in atombios_dig_transmitter_setup2() 1351 else if (radeon_encoder->devices & (ATOM_DEVICE_DFP_SUPPORT)) { in atombios_dig_transmitter_setup2() 1595 if (radeon_encoder->devices & (ATOM_DEVICE_LCD_SUPPORT)) in radeon_atom_encoder_dpms_avivo() [all …]
/linux-4.4.14/drivers/staging/most/Documentation/ABI/
D	sysfs-class-most.txt	27 What: /sys/class/most/mostcore/devices 35 What: /sys/class/most/mostcore/devices/<mdev>/description 45 What: /sys/class/most/mostcore/devices/<mdev>/interface 54 What: /sys/class/most/mostcore/devices/<mdev>/<channel>/ 65 What: /sys/class/most/mostcore/devices/<mdev>/<channel>/available_datatypes 73 What: /sys/class/most/mostcore/devices/<mdev>/<channel>/available_directions 81 What: /sys/class/most/mostcore/devices/<mdev>/<channel>/number_of_packet_buffers 90 What: /sys/class/most/mostcore/devices/<mdev>/<channel>/number_of_stream_buffers 99 What: /sys/class/most/mostcore/devices/<mdev>/<channel>/size_of_packet_buffer 108 What: /sys/class/most/mostcore/devices/<mdev>/<channel>/size_of_stream_buffer [all …]
/linux-4.4.14/Documentation/trace/
D	intel_th.txt	15 switch (Global Trace Hub, GTH). These devices are placed on a bus of 29 Common attributes for output devices are described in 30 Documentation/ABI/testing/sysfs-bus-intel_th-output-devices, the most 36 description is at Documentation/ABI/testing/sysfs-bus-intel_th-devices-gth. 57 devices were emumerated. All TH subdevices (devices on intel_th bus) 61 Output devices also get a device node in /dev/intel_thN, where N is 70 $ cat /sys/bus/intel_th/devices/0-msc0/port 75 $ echo 0 > /sys/bus/intel_th/devices/0-gth/masters/33 80 $ echo multi > /sys/bus/intel_th/devices/0-msc0/mode 81 $ echo 64,64 > /sys/bus/intel_th/devices/0-msc0/nr_pages [all …]
D	coresight.txt	87 manage coresight devices on a platform. This first implementation centers on 133 manage coresight devices on a platform. Any coresight compliant device can 143 If everything goes well during the registration process the new devices will 144 show up under /sys/bus/coresight/devices, as showns here for a TC2 platform: 146 root:~# ls /sys/bus/coresight/devices/ 201 root:/sys/bus/coresight/devices# ls 204 root:/sys/bus/coresight/devices# ls 20010000.etb 206 root:/sys/bus/coresight/devices# echo 1 > 20010000.etb/enable_sink 207 root:/sys/bus/coresight/devices# cat 20010000.etb/enable_sink 209 root:/sys/bus/coresight/devices# [all …]
/linux-4.4.14/Documentation/driver-model/
D	porting.txt	14 Most of the work of porting devices drivers to the new model happens 80 subdirectories: 'devices' and 'drivers'. 84 \|-- devices 125 When devices are discovered or registered with the bus type, the 131 necessary for representing devices in sysfs. 136 The driver model maintains an ordered list of devices that it uses 138 devices are shutdown before their physical parents, and vice versa. 140 devices. 174 This should happen on buses that support hotpluggable devices. 186 /sys/devices/pci0/ [all …]
D	class.txt	14 that devices of that class adhere to. Device drivers are the 51 As devices are bound to drivers, they are added to the device class 66 There is no list of devices in the device class. Each driver has a 67 list of devices that it supports. The device class has a list of 68 drivers of that particular class. To access all of the devices in the 88 \|-- devices 97 \|-- devices 102 Each device gets a symlink in the devices/ directory that points to the 107 \|-- devices 121 similarly to the DEVICE_ATTR macro for devices. For example, a definition
D	binding.txt	7 devices and the drivers. With generic device and device driver 14 The bus type structure contains a list of all devices that are on that bus 56 driver's list of devices. 62 A symlink is created in the bus's 'devices' directory that points to 65 A symlink is created in the driver's 'devices' directory that points 82 The bus's list of devices is iterated over to find a match. Devices 83 that already have a driver are skipped. All the devices are iterated 84 over, to bind as many devices as possible to the driver. 92 is removed from the driver's list of devices and the reference count 95 When a driver is removed, the list of devices that it supports is
D	platform.txt	5 is used to connect devices on busses with minimal infrastructure, 11 Platform devices 13 Platform devices are devices that typically appear as autonomous 14 entities in the system. This includes legacy port-based devices and 21 Platform devices are given a name, used in driver binding, and a 84 register platform devices: 90 The general rule is to register only those devices that actually exist, 91 but in some cases extra devices might be registered. For example, a kernel 96 In some cases, boot firmware will export tables describing the devices 98 only way for system setup code to set up the correct devices is to build [all …]
D	bus.txt	`45 of device IDs of devices they support that reside in a bus-specific 54 When a driver is registered with the bus, the bus's list of devices is 63 The lists of devices and drivers are intended to replace the local 64 lists that many buses keep. They are lists of struct devices and 93 \|-- devices 100 \|-- devices 108 the bus's devices directory to the device's directory in the physical 112 \|-- devices 128 similarly to the DEVICE_ATTR macro for devices. For example, a definition`
/linux-4.4.14/Documentation/i2c/
D	instantiating-devices	1 How to instantiate I2C devices 4 Unlike PCI or USB devices, I2C devices are not enumerated at the hardware 5 level. Instead, the software must know which devices are connected on each 6 I2C bus segment, and what address these devices are using. For this 7 reason, the kernel code must instantiate I2C devices explicitly. There are 11 Method 1a: Declare the I2C devices by bus number 17 devices which live on this bus. This is done with an array of struct 45 The above code declares 3 devices on I2C bus 1, including their respective 47 question is registered, the I2C devices will be instantiated automatically 50 The devices will be automatically unbound and destroyed when the I2C bus [all …]
D	ten-bit-addresses	`8 needed when instantiating 10 bit devices via the new_device file in sysfs. 10 I2C messages to and from 10-bit address devices have a different format. 21 case of automatic detection and instantiation of devices by their, 26 Note that 10-bit address devices are still pretty rare, so the limitations`
/linux-4.4.14/drivers/virtio/
D	Kconfig	11 tristate "PCI driver for virtio devices" 17 virtio backends. Most QEMU based VMMs should support these devices 23 bool "Support for legacy virtio draft 0.9.X and older devices" 30 both devices conforming to Virtio 1 specification, and legacy devices. 56 This driver supports virtio input devices such as 62 tristate "Platform bus driver for memory mapped virtio devices" 72 bool "Memory mapped virtio devices parameter parsing" 75 Allow virtio-mmio devices instantiation via the kernel command line
/linux-4.4.14/tools/usb/usbip/
D	README	`48 - List driver assignments for USB devices. 59 - List exported USB devices on the <host>. 75 Physically attach your USB devices to this host. 81 In another terminal, let's look up what USB devices are physically 85 Local USB devices 125 Local USB devices 136 First, let's list available remote devices that are marked as 143 Exportable USB devices 147 : /sys/devices/pci0000:00/0000:00:1f.2/usb1/1-1 152 : /sys/devices/pci0000:00/0000:00:1f.2/usb1/1-2/1-2.2/1-2.2.1 [all …]`
/linux-4.4.14/arch/arm/mach-davinci/
D	Makefile	`13 obj-$(CONFIG_ARCH_DAVINCI_DM644x) += dm644x.o devices.o 14 obj-$(CONFIG_ARCH_DAVINCI_DM355) += dm355.o devices.o 15 obj-$(CONFIG_ARCH_DAVINCI_DM646x) += dm646x.o devices.o 16 obj-$(CONFIG_ARCH_DAVINCI_DM365) += dm365.o devices.o 17 obj-$(CONFIG_ARCH_DAVINCI_DA830) += da830.o devices-da8xx.o 18 obj-$(CONFIG_ARCH_DAVINCI_DA850) += da850.o devices-da8xx.o`
/linux-4.4.14/Documentation/device-mapper/
D	striped.txt	`5 device across one or more underlying devices. Data is written in "chunks", 6 with consecutive chunks rotating among the underlying devices. This can 8 devices in parallel. 11 <num devs>: Number of underlying devices. 18 One or more underlying devices can be specified. The striped device size must 19 be a multiple of the chunk size multiplied by the number of underlying devices. 27 # Create a striped device across any number of underlying devices. The device`
D	dm-raid.txt	79 then the layouts for 2, 3 and 4 devices are: 93 for 2, 3 and 4 devices are: 106 layouts for 2, 3 and 4 devices are: 119 <#raid_devs>: The number of devices composing the array. 130 # RAID4 - 4 data drives, 1 parity (no metadata devices) 131 # No metadata devices specified to hold superblock/bitmap info 139 # RAID4 - 4 data drives, 1 parity (with metadata devices) 161 2: <raid_type> <#devices> <health_chars> \ 167 Here we can see the RAID type is raid4, there are 5 devices - all of 216 When a block is discarded, some storage devices will return zeroes when [all …]
/linux-4.4.14/tools/testing/selftests/cpu-hotplug/
D	cpu-on-off-test.sh	23 if ! ls $SYSFS/devices/system/cpu/cpu* > /dev/null 2>&1; then 29 online_cpus=`cat $SYSFS/devices/system/cpu/online` 33 offline_cpus=`cat $SYSFS/devices/system/cpu/offline` 49 for cpu in $SYSFS/devices/system/cpu/cpu*; do 68 grep -q 1 $SYSFS/devices/system/cpu/cpu$1/online 73 grep -q 0 $SYSFS/devices/system/cpu/cpu$1/online 78 echo 1 > $SYSFS/devices/system/cpu/cpu$1/online 83 echo 0 > $SYSFS/devices/system/cpu/cpu$1/online
/linux-4.4.14/drivers/acpi/
D	thermal.c	154 struct acpi_handle_list devices; member 160 struct acpi_handle_list devices; member 172 u8 devices:1; /* _TZD */ member 186 struct acpi_handle_list devices; member 285 struct acpi_handle_list devices; in acpi_thermal_trips_update() local 392 memset(&devices, 0, sizeof(struct acpi_handle_list)); in acpi_thermal_trips_update() 394 NULL, &devices); in acpi_thermal_trips_update() 402 if (memcmp(&tz->trips.passive.devices, &devices, in acpi_thermal_trips_update() 404 memcpy(&tz->trips.passive.devices, &devices, in acpi_thermal_trips_update() 454 memset(&devices, 0, sizeof(struct acpi_handle_list)); in acpi_thermal_trips_update() [all …]
/linux-4.4.14/drivers/media/usb/dvb-usb/
D	dvb-usb-init.c	185 for (j = 0; j < DVB_USB_ID_MAX_NUM && props->devices[i].cold_ids[j] != NULL; j++) { in dvb_usb_find_device() 186 …deb_info("check for cold %x %x\n", props->devices[i].cold_ids[j]->idVendor, props->devices[i].cold… in dvb_usb_find_device() 187 if (props->devices[i].cold_ids[j]->idVendor == le16_to_cpu(udev->descriptor.idVendor) && in dvb_usb_find_device() 188 props->devices[i].cold_ids[j]->idProduct == le16_to_cpu(udev->descriptor.idProduct)) { in dvb_usb_find_device() 190 desc = &props->devices[i]; in dvb_usb_find_device() 198 for (j = 0; j < DVB_USB_ID_MAX_NUM && props->devices[i].warm_ids[j] != NULL; j++) { in dvb_usb_find_device() 199 …deb_info("check for warm %x %x\n", props->devices[i].warm_ids[j]->idVendor, props->devices[i].warm… in dvb_usb_find_device() 200 if (props->devices[i].warm_ids[j]->idVendor == le16_to_cpu(udev->descriptor.idVendor) && in dvb_usb_find_device() 201 props->devices[i].warm_ids[j]->idProduct == le16_to_cpu(udev->descriptor.idProduct)) { in dvb_usb_find_device() 203 desc = &props->devices[i]; in dvb_usb_find_device()
D	Kconfig	2 tristate "Support for various USB DVB devices" 6 USB1.1 and USB2.0 DVB devices. 11 For a complete list of supported USB devices see the LinuxTV DVB Wiki: 17 bool "Enable extended debug support for all DVB-USB devices" 33 tristate "DiBcom USB DVB-T devices (based on the DiB3000M-B) (see help for device list)" 42 For an up-to-date list of devices supported by this driver, have a look 52 Support for faulty USB IDs due to an invalid EEPROM on some Artec devices. 55 tristate "DiBcom USB DVB-T devices (based on the DiB3000M-C/P) (see help for device list)" 63 For an up-to-date list of devices supported by this driver, have a look 70 tristate "DiBcom DiB0700 USB DVB devices (see help for supported devices)" [all …]
/linux-4.4.14/Documentation/leds/
D	leds-lp55xx.txt	12 Create LED class devices for multiple output channels 58 LP55xx family devices have the internal program memory for running 81 echo 1 > /sys/bus/i2c/devices/xxxx/select_engine 85 echo 1 > /sys/bus/i2c/devices/xxxx/run_engine 89 echo 3 > /sys/bus/i2c/devices/xxxx/select_engine 93 echo "000001100" > /sys/bus/i2c/devices/xxxx/engine3_leds 94 echo 1 > /sys/bus/i2c/devices/xxxx/run_engine 109 echo 2 > /sys/bus/i2c/devices/xxxx/select_engine 113 echo "111111111" > /sys/bus/i2c/devices/xxxx/engine2_leds 114 echo 1 > /sys/bus/i2c/devices/xxxx/run_engine [all …]
D	leds-lp5562.txt	`41 echo 2 > /sys/bus/i2c/devices/xxxx/select_engine # 2 is for green channel 42 echo "RGB" > /sys/bus/i2c/devices/xxxx/engine_mux # engine mux for RGB 46 echo 1 > /sys/bus/i2c/devices/xxxx/run_engine 49 echo 1 or 2 or 3 > /sys/bus/i2c/devices/xxxx/select_engine 50 echo "W" > /sys/bus/i2c/devices/xxxx/engine_mux 54 echo 1 > /sys/bus/i2c/devices/xxxx/run_engine`
/linux-4.4.14/drivers/media/usb/
D	Kconfig	`7 If you have such devices, say Y. 12 comment "Webcam devices" 24 comment "Analog TV USB devices" 33 comment "Analog/digital TV USB devices" 41 comment "Digital TV USB devices" 52 comment "Webcam, TV (analog/digital) USB devices" 57 comment "Software defined radio USB devices"`
/linux-4.4.14/drivers/hwtracing/stm/
D	Kconfig	`2 tristate "System Trace Module devices" 8 Examples of such devices are Intel(R) Trace Hub and Coresight STM. 21 tristate "Kernel console over STM devices" 24 messages to trace hosts over STM devices. 26 If you want to send kernel console messages over STM devices,`
/linux-4.4.14/drivers/usb/usbip/
D	usbip_protocol.txt	5 USB devices and the clients imports them. The device driver for the exported 8 The client may ask for the list of the exported USB devices. To get the list the 12 the OP_REP_DEVLIST packet which lists the exported USB devices. Finally the 17 (imports USB devices) (exports USB devices) 26 Once the client knows the list of exported USB devices it may decide to use one 37 (imports USB devices) (exports USB devices) 91 OP_REQ_DEVLIST: Retrieve the list of exported USB devices. 98 \| \| \| devices. 102 OP_REP_DEVLIST: Reply with the list of exported USB devices. 108 2 \| 2 \| 0x0005 \| Reply code: The list of exported USB devices. [all …]
/linux-4.4.14/drivers/net/wireless/b43/
D	Kconfig	8 b43 is a driver for the Broadcom 43xx series wireless devices. 14 This driver supports the new BCM43xx IEEE 802.11G devices, but not 15 the old IEEE 802.11B devices. Old devices are supported by 19 IEEE 802.11G devices can talk to IEEE 802.11B AccessPoints. 79 Broadcom 43xx device support for Soft-MAC SDIO devices. 85 Note that this does not support Broadcom 43xx Full-MAC devices. 106 bool "Support for G-PHY (802.11g) devices" 115 bool "Support for N-PHY (the main 802.11n series) devices" 126 bool "Support for LP-PHY (low-power 802.11g) devices" 131 and embedded devices. It supports 802.11a/b/g [all …]
/linux-4.4.14/Documentation/blockdev/drbd/
D	data-structure-v9.txt	`8 devices (aka volumes) and connections to other nodes ("peer nodes"). Each DRBD 26 In this table, horizontally, devices can be accessed from resources by their 30 devices, and from connections and devices to their resource. 33 devices can be accessed by their minor device number via the drbd_devices idr. 37 devices and connections; their lifetime is determined by the lifetime of the`
/linux-4.4.14/Documentation/devicetree/bindings/mfd/
D	mfd.txt	`3 These devices comprise a nexus for heterogeneous hardware blocks containing 16 mix of unrelated hardware devices. 21 consider all subnodes of the MFD device as separate devices akin to how 23 memory-mapped bus. For more complex devices, when the nexus driver has to 24 probe registers to figure out what child devices exist etc, this should not 25 be used. In the latter case the child devices will be determined by the`
/linux-4.4.14/drivers/nfc/
D	Kconfig	`2 # Near Field Communication (NFC) devices 5 menu "Near Field Communication (NFC) devices" 13 This driver provides support for NFC NXP PN533 devices. 15 Say Y here to compile support for PN533 devices into the 23 combo devices. This makes use of shared transport line discipline 54 This driver declares two virtual NFC devices supporting NFC-DEP 57 loopback devices. 66 This adds support for Sony Port-100 chip based USB devices such as the`
/linux-4.4.14/drivers/hid/
D	Kconfig	15 devices (such as, but not strictly limited to, Bluetooth) are 18 together with generic HID layer code. The HID devices are added and 29 bool "Battery level reporting for HID devices" 34 This option adds support of reporting battery strength (for HID devices 42 Say Y here if you want to support HID devices (from the USB 44 devices, like monitor controls and Uninterruptable Power Supplies. 46 This module supports these devices separately using a separate 65 corresponding HID Device Driver or provides input devices on top of your 83 Support for generic devices on the HID bus. This includes most 120 Support for some Apple devices which less or more break [all …]
D	hid-roccat.c	72 static struct roccat_device *devices[ROCCAT_MAX_DEVICES]; variable 164 device = devices[minor]; in roccat_open() 214 device = devices[minor]; in roccat_release() 257 device = devices[minor]; in roccat_report_event() 310 if (devices[minor]) in roccat_connect() 316 devices[minor] = device; in roccat_connect() 328 devices[minor] = NULL; in roccat_connect() 359 device = devices[minor]; in roccat_disconnect() 367 devices[minor] = NULL; in roccat_disconnect() 388 device = devices[minor]; in roccat_ioctl()
D	hid-lgff.c	`59 static const struct dev_type devices[] = { variable 140 for (i = 0; i < ARRAY_SIZE(devices); i++) { in lgff_init() 141 if (dev->id.vendor == devices[i].idVendor && in lgff_init() 142 dev->id.product == devices[i].idProduct) { in lgff_init() 143 ff_bits = devices[i].ff; in lgff_init()`
/linux-4.4.14/Documentation/ia64/
D	serial.txt	3 As of 2.6.10, serial devices on ia64 are named based on the 6 /dev/ttyS1, etc., and PCI devices are named sequentially 7 starting after the ACPI devices. 12 table[1] that tells the kernel about devices that can be used 14 or the EFI ConOut path contained only UART devices, the 22 Any additional ACPI or PCI devices were registered sequentially 27 change, but we registered devices that might not really exist. 45 EFI knows what your console devices are, but it doesn't tell the 48 devices are, but not all firmware supplies it. Also, EFI supports 74 all the serial devices, which can happen a minute or more after the [all …]
/linux-4.4.14/drivers/net/wireless/libertas/
D	Kconfig	`9 A library for Marvell Libertas 8xxx devices. 15 A driver for Marvell Libertas 8388 USB devices. 21 A driver for Marvell Libertas 8385 CompactFlash devices. 27 A driver for Marvell Libertas 8385/8686/8688 SDIO devices. 33 A driver for Marvell Libertas 8686 SPI devices.`
/linux-4.4.14/drivers/net/wireless/rt2x00/
D	Kconfig	80 bool "rt2800pci - Include support for rt33xx devices" 88 bool "rt2800pci - Include support for rt35xx devices (EXPERIMENTAL)" 97 bool "rt2800pci - Include support for rt53xx devices (EXPERIMENTAL)" 105 bool "rt2800pci - Include support for rt3290 devices (EXPERIMENTAL)" 154 bool "rt2800usb - Include support for rt33xx devices" 162 bool "rt2800usb - Include support for rt35xx devices (EXPERIMENTAL)" 170 bool "rt2800usb - Include support for rt3573 devices (EXPERIMENTAL)" 172 This enables support for RT3573 chipset based wireless USB devices 176 bool "rt2800usb - Include support for rt53xx devices (EXPERIMENTAL)" 183 bool "rt2800usb - Include support for rt55xx devices (EXPERIMENTAL)" [all …]
/linux-4.4.14/arch/sh/boards/mach-rsk/
D	Makefile	`2 obj-$(CONFIG_SH_RSK7203) += devices-rsk7203.o 3 obj-$(CONFIG_SH_RSK7264) += devices-rsk7264.o 4 obj-$(CONFIG_SH_RSK7269) += devices-rsk7269.o`
/linux-4.4.14/Documentation/filesystems/
D	ubifs.txt	6 to work with flash devices. It is important to understand, that UBIFS 9 which work with MTD devices, not block devices. The other Linux 12 To make it more clear, here is a small comparison of MTD devices and 13 block devices. 15 1 MTD devices represent flash devices and they consist of eraseblocks of 16 rather large size, typically about 128KiB. Block devices consist of 18 2 MTD devices support 3 main operations - read from some offset within an 20 eraseblock. Block devices support 2 main operations - read a whole 38 level abstraction than a MTD device. The programming model of UBI devices 39 is very similar to MTD devices - they still consist of large eraseblocks, [all …]
/linux-4.4.14/tools/power/cpupower/bench/
D	cpufreq-bench_script.sh	`43 echo $up_threshold >/sys/devices/system/cpu/cpu0/cpufreq/ondemand/up_threshold 44 echo $sampling_rate >/sys/devices/system/cpu/cpu0/cpufreq/ondemand/sampling_rate 45 up_threshold_set=$(cat /sys/devices/system/cpu/cpu0/cpufreq/ondemand/up_threshold) 46 sampling_rate_set=$(cat /sys/devices/system/cpu/cpu0/cpufreq/ondemand/sampling_rate)`
/linux-4.4.14/Documentation/devicetree/bindings/arm/keystone/
D	keystone.txt	`4 Boards with Keystone2 based devices (TCI66xxK2H) SOC shall have the 8 - compatible: All TI specific devices present in Keystone SOC should be in 9 the form "ti,keystone-*". Generic devices like gic, arch_timers, ns16550 10 type UART should use the specified compatible for those devices.`
/linux-4.4.14/drivers/devfreq/
D	tegra-devfreq.c	173 struct tegra_devfreq_device devices[ARRAY_SIZE(actmon_device_configs)]; member 317 for (i = 0; i < ARRAY_SIZE(tegra->devices); i++) { in actmon_isr() 318 if (val & tegra->devices[i].config->irq_mask) { in actmon_isr() 319 actmon_isr_device(tegra, tegra->devices + i); in actmon_isr() 398 for (i = 0; i < ARRAY_SIZE(tegra->devices); i++) { in tegra_actmon_rate_notify_cb() 399 dev = &tegra->devices[i]; in tegra_actmon_rate_notify_cb() 417 for (i = 0; i < ARRAY_SIZE(tegra->devices); i++) { in tegra_actmon_enable_interrupts() 418 dev = &tegra->devices[i]; in tegra_actmon_enable_interrupts() 438 for (i = 0; i < ARRAY_SIZE(tegra->devices); i++) { in tegra_actmon_disable_interrupts() 439 dev = &tegra->devices[i]; in tegra_actmon_disable_interrupts() [all …]
/linux-4.4.14/drivers/staging/unisys/Documentation/
D	overview.txt	10 allow guest partitions on the same server to share devices that would 30 devices), or "console partition" (for virtual keyboard and mouse devices). 41 not be discussed in this document. Shared SR-IOV devices should be used 60 devices reside. It provides a registration function named 73 devices it discovers, as it includes a MODALIAS environment variable of this 102 /sys/devices/visorbus<x>/dev<y>) 150 Documentation/driver-model/, the hierarchy of s-Par virtual devices is 152 /sys/bus/visorbus/devices/ might look like: 154 vbus1:dev1 -> ../../../devices/visorbus1/vbus1:dev1 155 vbus1:dev2 -> ../../../devices/visorbus1/vbus1:dev2 [all …]
/linux-4.4.14/Documentation/hwmon/
D	hih6130	`18 The difference between the two devices is that the HIH-6131 has a condensation 21 The devices communicate with the I2C protocol. All sensors are set to the same 25 Please see Documentation/i2c/instantiating-devices for details on how to 26 instantiate I2C devices.`
D	lineage-pem	`4 Supported devices: 29 This driver does not probe for Lineage CPL devices, since there is no register 31 the devices explicitly. 36 $ echo lineage-pem 0x40 > /sys/bus/i2c/devices/i2c-1/new_device 46 All Lineage CPL devices report output voltage and device temperature as well as 51 supported on newer devices. The driver detects if those attributes are supported,`
D	max6650	`24 The 2 devices are very similar, but the MAX6550 has a reduced feature 27 The driver is not able to distinguish between the 2 devices. 46 This driver does not auto-detect devices. You will have to instantiate the 47 devices explicitly. Please see Documentation/i2c/instantiating-devices for`
D	htu21	`21 The devices communicate with the I2C protocol. All sensors are set to the 25 This driver does not auto-detect devices. You will have to instantiate the 26 devices explicitly. Please see Documentation/i2c/instantiating-devices`
/linux-4.4.14/tools/testing/selftests/memory-hotplug/
D	mem-on-off-test.sh	`21 if ! ls $SYSFS/devices/system/memory/memory* > /dev/null 2>&1; then 34 for memory in $SYSFS/devices/system/memory/memory*; do 54 grep -q online $SYSFS/devices/system/memory/memory$1/state 59 grep -q offline $SYSFS/devices/system/memory/memory$1/state 64 echo online > $SYSFS/devices/system/memory/memory$1/state 69 echo offline > $SYSFS/devices/system/memory/memory$1/state`
/linux-4.4.14/Documentation/mic/
D	mic_overview.txt	`6 PCIe devices. The card itself runs a bootstrap after reset that 11 for the X100 devices. 14 devices for networking, storage and console. We provide these devices 17 the standard virtio framework for network, disk and console devices, 23 a virtual bus called mic bus is created and virtual dma devices are 25 and used only by the host driver to transfer data for the virtio devices. 32 boot, shutdown and reset of Intel MIC devices. It communicates with a COSM`
/linux-4.4.14/Documentation/laptops/
D	sony-laptop.txt	7 Sony Vaio laptops. This driver mixes both devices functions under the same 13 Some models report hotkeys through the SNC or SPIC devices, such events are 15 subsystem. See the logs of /proc/bus/input/devices to find out what those 16 events are and which input devices are created by the driver. 41 /sys/devices/platform/sony-laptop/ 61 # echo "1" > /sys/devices/platform/sony-laptop/brightness_default 63 # echo "8" > /sys/devices/platform/sony-laptop/brightness_default 65 # cat /sys/devices/platform/sony-laptop/brightness_default 68 # echo "0" > /sys/devices/platform/sony-laptop/audiopower 70 # echo "1" > /sys/devices/platform/sony-laptop/audiopower [all …]
/linux-4.4.14/Documentation/misc-devices/
D	eeprom	50 EEPROMs on any I2C adapter. The supported devices are generically called 52 industry-standard devices may vary by manufacturer. 59 The other devices will not be found on a DIMM because they respond to more 79 * Full support for larger devices (24C04, 24C08, 24C16). These are not 80 typically found on a PC. These devices will appear as separate devices at 83 * Support for really large devices (24C32, 24C64, 24C128, 24C256, 24C512). 84 These devices require two-byte address fields and are not supported. 94 should have some EEPROM directories in /sys/bus/i2c/devices/* of names such
/linux-4.4.14/Documentation/power/
D	basic-pm-debugging.txt	49 devices 50 - test the freezing of processes and suspending of devices 53 - test the freezing of processes, suspending of devices and platform 57 - test the freezing of processes, suspending of devices, platform 61 - test the freezing of processes, suspending of devices, platform global 63 platform/system devices 69 /sys/power/pm_test (eg. "devices" to test the freezing of processes and 70 suspending devices) and issue the standard hibernation commands. For example, 71 to use the "devices" test mode along with the "platform" mode of hibernation, 74 # echo devices > /sys/power/pm_test [all …]
D	pci.txt	10 devices. For general description of the kernel's interfaces related to device 11 power management refer to Documentation/power/devices.txt and 28 devices into states in which they draw less power (low-power states) at the 38 PCI devices may be put into low-power states in two ways, by using the device 75 The implementation of the PCI PM Spec is optional for conventional PCI devices, 76 but it is mandatory for PCI Express devices. If a device supports the PCI PM 81 The PCI PM Spec defines 4 operating states for devices (D0-D3) and for buses 87 one is D3hot, referred to as the software accessible D3, because devices can be 88 programmed to go into it. The second one, D3cold, is the state that PCI devices 92 removed from all devices on the bus. [all …]
D	devices.txt	21 Drivers will use one or both of these models to put devices into low-power 37 using the relevant /sys/devices/.../power/wakeup file (for Ethernet 45 However, devices are not generally independent of each other (for 47 devices have been suspended). Moreover, depending on the bus type the 61 very system-specific, and often device-specific. Also, that if enough devices 67 Most suspended devices will have quiesced all I/O: no more DMA or IRQs (except 81 management of devices they are concerned with. These interfaces cover both 132 The core methods to suspend and resume devices reside in struct dev_pm_ops 150 /sys/devices/.../power/wakeup files 164 devices (i.e. devices whose "can_wakeup" flags are set) and is created (or [all …]
/linux-4.4.14/Documentation/devicetree/bindings/powerpc/fsl/
D	pmc.txt	`22 - reg: For devices compatible with "fsl,mpc8349-pmc", the first resource 26 For devices compatible with "fsl,mpc8548-pmc", the first resource 29 - interrupts: For "fsl,mpc8349-pmc"-compatible devices, the first 32 - fsl,mpc8313-wakeup-timer: For "fsl,mpc8313-pmc"-compatible devices, 41 supports disabling and resuming devices at any time. 46 This sleep controller only supports disabling devices during system 53 disabling. This sleep controller does not support configuring devices`
/linux-4.4.14/Documentation/fb/
D	viafb.txt	106 This option is used to specify active devices.(CRT, DVI, CRT+LCD...) 115 To enable two devices, such as CRT+DVI: 208 output devices that could be available on your platform. It is likely 220 forwarded to one or more output devices. Reading those files is a way 221 to query which output devices are currently used by an iga. 224 If there are no output devices printed the output of this iga is lost. 226 Writing to these files allows adjusting the output devices during 227 runtime. One can add new devices, remove existing ones or switch 231 and removal of devices. So a prefix '+' adds the devices from your list 232 to the already existing ones, '-' removes the listed devices from the [all …]
/linux-4.4.14/Documentation/ABI/obsolete/
D	sysfs-driver-hid-roccat-ryos	1 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 9 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 21 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 31 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 41 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 51 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 61 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 71 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 81 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 92 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… [all …]
D	sysfs-driver-hid-roccat-isku	1 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 12 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 20 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 31 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 41 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 51 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 61 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 71 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 81 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 91 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… [all …]
D	sysfs-driver-hid-roccat-koneplus	1 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 12 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 24 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 36 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 44 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 55 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 70 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 82 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 98 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 111 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… [all …]
D	sysfs-driver-hid-roccat-konepure	1 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 13 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 21 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 29 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 40 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 55 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 71 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 80 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 88 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 97 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p…
D	sysfs-bus-usb	`1 What: /sys/bus/usb/devices/.../power/level 16 During normal use, devices should be left in the "auto" 24 devices to support suspend/resume, many of them do not. 26 initializes all non-hub devices in the "on" level. Some`
D	sysfs-driver-hid-roccat-kovaplus	1 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 11 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 22 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 32 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 42 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 54 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 62 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 77 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 89 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 105 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p…
D	sysfs-driver-hid-roccat-pyra	1 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 19 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 28 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 40 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 48 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 63 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 75 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 91 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 104 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 115 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p…
D	sysfs-driver-hid-roccat-savu	1 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 16 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 24 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 39 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 47 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 58 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 70 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p…
/linux-4.4.14/Documentation/cpuidle/
D	sysfs.txt	`8 /sys/devices/system/cpu/cpuidle 24 /sys/devices/system/cpu/cpuX/cpuidle 28 # ls -lR /sys/devices/system/cpu/cpu0/cpuidle/ 29 /sys/devices/system/cpu/cpu0/cpuidle/: 36 /sys/devices/system/cpu/cpu0/cpuidle/state0: 46 /sys/devices/system/cpu/cpu0/cpuidle/state1: 56 /sys/devices/system/cpu/cpu0/cpuidle/state2: 66 /sys/devices/system/cpu/cpu0/cpuidle/state3:`
/linux-4.4.14/Documentation/w1/
D	w1.generic	12 All w1 slave devices must be connected to a w1 bus master device. 14 Example w1 master devices: 18 Emulated devices, such as a RS232 converter, parallel port adapter, etc 26 - the w1 bus is periodically searched for new slave devices 47 Slave devices are handled by a driver written for a family of w1 devices. 67 Emulated devices must provide the ability to set the output signal level 98 If you have a w1 bus that never changes (you don't add or remove devices), 104 redetect manually removed devices that are present and timeout manually 105 added devices that aren't on the bus. 120 rw - (optional) created for slave devices which do not have
/linux-4.4.14/drivers/media/usb/usbvision/
D	Kconfig	`2 tristate "USB video devices based on Nogatech NT1003/1004/1005" 7 There are more than 50 different USB video devices based on 9 devices.`
/linux-4.4.14/arch/arm/mach-pxa/
D	csb701.c	`52 static struct platform_device *devices[] __initdata = { variable 62 return platform_add_devices(devices, ARRAY_SIZE(devices)); in csb701_init()`
D	mp900.c	`79 static struct platform_device *devices[] __initdata = { variable 90 platform_add_devices(devices, ARRAY_SIZE(devices)); in mp900c_init()`
D	himalaya.c	`124 static struct platform_device *devices[] __initdata = { variable 156 platform_add_devices(devices, ARRAY_SIZE(devices)); in himalaya_init()`
/linux-4.4.14/drivers/pci/hotplug/
D	rpaphp_pci.c	`104 slot->pci_devs = &bus->devices; in rpaphp_enable_slot() 118 if (list_empty(&bus->devices)) in rpaphp_enable_slot() 121 if (!list_empty(&bus->devices)) { in rpaphp_enable_slot() 129 list_for_each_entry (dev, &bus->devices, bus_list) in rpaphp_enable_slot()`
/linux-4.4.14/drivers/nfc/nfcmrvl/
D	Kconfig	`4 The core driver to support Marvell NFC devices. 16 This driver provides support for Marvell NFC-over-USB devices: 29 This driver provides support for Marvell NFC-over-UART devices 40 This driver provides support for Marvell NFC-over-I2C devices. 51 This driver provides support for Marvell NFC-over-SPI devices.`
/linux-4.4.14/drivers/platform/x86/
D	acer-wmi.c	156 u16 devices; /* Other type devices default status / member 170 u16 devices; / Set Device / member 177 u16 devices; / Get Device / member 183 u16 devices; / Current Device Status / member 255 struct dentry devices; member 1033 .devices = device, in wmid3_get_device_status() 1068 *value = !!(return_value.devices & device); in wmid3_get_device_status() 1098 u16 devices; in wmid3_set_device_status() local 1102 .devices = commun_func_bitmap, in wmid3_set_device_status() 1111 .devices = commun_func_bitmap, in wmid3_set_device_status() [all …]
/linux-4.4.14/drivers/vfio/pci/
D	vfio_pci.c	329 struct vfio_pci_dependent_device devices; member 344 fill->devices[fill->cur].group_id = iommu_group_id(iommu_group); in vfio_pci_fill_devs() 345 fill->devices[fill->cur].segment = pci_domain_nr(pdev->bus); in vfio_pci_fill_devs() 346 fill->devices[fill->cur].bus = pdev->bus->number; in vfio_pci_fill_devs() 347 fill->devices[fill->cur].devfn = pdev->devfn; in vfio_pci_fill_devs() 616 struct vfio_pci_dependent_device devices = NULL; in vfio_pci_ioctl() local 649 if (hdr.argsz < sizeof(hdr) + (fill.max * sizeof(devices))) { in vfio_pci_ioctl() 655 devices = kcalloc(fill.max, sizeof(devices), GFP_KERNEL); in vfio_pci_ioctl() 656 if (!devices) in vfio_pci_ioctl() 659 fill.devices = devices; in vfio_pci_ioctl() [all …]
D	Kconfig	`2 tristate "VFIO support for PCI devices" 13 bool "VFIO PCI support for VGA devices" 17 region on VGA devices for accessing legacy VGA addresses used by`
/linux-4.4.14/drivers/bcma/
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`
/linux-4.4.14/Documentation/hid/
D	hidraw.txt	12 custom HID devices. 14 Hidraw is also useful for communicating with non-conformant HID devices 18 communication with these non-conformant devices is impossible using hiddev. 20 these non-conformant devices. 32 devices attached to the system. There is a tutorial on libudev with a 42 devices, the reports read using read() are the reports sent from the device 50 byte. For devices which do not use numbered reports, the report data 55 The write() function will write a report to the device. For USB devices, if 92 For USB devices, the string contains the physical path to the device (the 93 USB controller, hubs, ports, etc). For Bluetooth devices, the string [all …]
/linux-4.4.14/sound/core/
D	device.c	`63 list_for_each_prev(p, &card->devices) { in snd_device_new() 101 list_for_each_entry(dev, &card->devices, list) in look_for_dev() 211 list_for_each_entry(dev, &card->devices, list) { in snd_device_register_all() 229 list_for_each_entry_reverse(dev, &card->devices, list) in snd_device_disconnect_all() 243 list_for_each_entry_safe_reverse(dev, next, &card->devices, list) in snd_device_free_all()`
/linux-4.4.14/drivers/net/usb/
D	Kconfig	2 # USB Network devices configuration 19 device based on the EL1210A chip. Supported devices are: 59 adapters, including some "no brand" devices. It does NOT work on 60 SmartBridges smartNIC or on Belkin F5U111 devices - you should use 78 complete list of supported devices. 139 others), and devices that interoperate using the standard 146 a two-node link, or "eth0" for most CDC-Ethernet devices. Those 165 This driver should work with at least the following devices: 183 what other networking devices you have in use. 195 This driver should work with at least the following devices: [all …]
/linux-4.4.14/arch/h8300/kernel/
D	sim-console.c	`71 static struct platform_device *devices[] __initdata = { variable 77 early_platform_add_devices(devices, in sim_console_register() 78 ARRAY_SIZE(devices)); in sim_console_register()`
/linux-4.4.14/arch/arm/mach-netx/
D	nxdkn.c	`84 static struct platform_device *devices[] __initdata = { variable 92 platform_add_devices(devices, ARRAY_SIZE(devices)); in nxdkn_init()`
/linux-4.4.14/drivers/iio/imu/inv_mpu6050/
D	Kconfig	`2 # inv-mpu6050 drivers for Invensense MPU devices and combos 6 tristate "Invensense MPU6050 devices" 12 This driver supports the Invensense MPU6050 devices.`
/linux-4.4.14/drivers/net/can/usb/
D	Kconfig	`19 This driver supports the Geschwister Schneider USB/CAN devices. 27 This driver adds support for Kvaser CAN/USB devices like Kvaser 30 The driver provides support for the following devices: 76 tristate "8 devices USB2CAN interface" 79 from 8 devices (http://www.8devices.com).`
/linux-4.4.14/drivers/net/wireless/p54/
D	Kconfig	`9 also need to be enabled in order to support any devices. 11 These devices require softmac firmware which can be found at 23 These devices require softmac firmware which can be found at 33 This driver supports most devices that are supported by the 34 fullmac prism54 driver plus many devices which are not 56 Unlike the PCI or USB devices, the SPI variants don't have`
/linux-4.4.14/drivers/staging/gdm724x/
D	Kconfig	`9 This driver supports GCT GDM724x LTE chip based USB modem devices. 10 It exposes 4 network devices to be used per PDN and 2 tty devices to be`
/linux-4.4.14/drivers/lightnvm/
D	core.c	134 list_for_each_entry(dev, &nvm_devices, devices) { in nvm_register_mgr() 162 list_for_each_entry(dev, &nvm_devices, devices) in nvm_find_nvm_dev() 344 list_add(&dev->devices, &nvm_devices); in nvm_register() 367 list_del(&dev->devices); in nvm_unregister() 515 list_for_each_entry(dev, &nvm_devices, devices) in __nvm_configure_remove() 638 list_for_each_entry(dev, &nvm_devices, devices) { in nvm_configure_get() 704 struct nvm_ioctl_get_devices *devices; in nvm_ioctl_get_devices() local 711 devices = kzalloc(sizeof(struct nvm_ioctl_get_devices), GFP_KERNEL); in nvm_ioctl_get_devices() 712 if (!devices) in nvm_ioctl_get_devices() 716 list_for_each_entry(dev, &nvm_devices, devices) { in nvm_ioctl_get_devices() [all …]
/linux-4.4.14/Documentation/block/
D	writeback_cache_control.txt	8 Many storage devices, especially in the consumer market, come with volatile 9 write back caches. That means the devices signal I/O completion to the 45 worry if the underlying devices need any explicit cache flushing and how 55 bits need to be propagated to underlying devices, and a global flush needs 60 devices with volatile caches need to implement the support for these 67 For devices that do not support volatile write caches there is no driver 70 requests that have a payload. For devices with volatile write caches the 79 layer. For devices that also support the FUA bit the block layer needs
/linux-4.4.14/drivers/base/
D	isa.c	`103 struct device *dev = isa_driver->devices; in isa_unregister_driver() 120 isa_driver->devices = NULL; in isa_register_driver() 154 isa_dev->next = isa_driver->devices; in isa_register_driver() 155 isa_driver->devices = &isa_dev->dev; in isa_register_driver() 160 if (!error && !isa_driver->devices) in isa_register_driver()`
/linux-4.4.14/Documentation/ide/
D	warm-plug-howto.txt	`5 To warm-plug devices on a port 'idex': 16 no other active references to devices before doing "delete_devices" step, 17 also do not attempt "scan" step on devices currently in use -- otherwise`
/linux-4.4.14/Documentation/devicetree/bindings/
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), ...]; 89 Some IP cores actually implement 2 or more logical devices. In 96 makes the assumption that both logical devices have the same bus 99 enumerate logical devices within an IP core. For example, the 147 to the devices. The device tree structure should reflect the bus 233 device tree. The following are bindings for specific devices: 259 Xilinx Ethernet devices. In addition to general xilinx properties [all …]
/linux-4.4.14/sound/usb/6fire/
D	chip.c	`39 static struct usb_device *devices[SNDRV_CARDS] = SNDRV_DEFAULT_PTR; variable 98 if (devices[i] == device) { in usb6fire_chip_probe() 104 } else if (!devices[i] && regidx < 0) in usb6fire_chip_probe() 112 devices[regidx] = device; in usb6fire_chip_probe() 190 devices[chip->regidx] = NULL; in usb6fire_chip_disconnect()`
/linux-4.4.14/Documentation/w1/slaves/
D	w1_therm	`14 w1_therm provides basic temperature conversion for ds18*20 devices, and the 31 Parasite powered devices are limited to one slave performing a 32 temperature conversion at a time. If none of the devices are parasite 33 powered it would be possible to convert all the devices at the same 41 command to check if there are pariste powered devices on the bus. 43 In case the detection of parasite devices using this command fails`
/linux-4.4.14/drivers/mtd/ubi/
D	Kconfig	6 logical volumes on top of MTD devices, hides some complexities of 20 of UBI devices. When this threshold is exceeded, UBI starts performing 70 the device. Using fastmap makes only sense on large devices where 75 fastmap support. On typical flash devices the whole fastmap fits 81 tristate "MTD devices emulation driver (gluebi)" 84 devices on top of UBI volumes: for each UBI volumes an MTD device is 91 bool "Read-only block devices on top of UBI volumes" 95 This option enables read-only UBI block devices support. UBI block 96 devices will be layered on top of UBI volumes, which means that the
/linux-4.4.14/sound/drivers/
D	virmidi.c	`83 static struct platform_device *devices[SNDRV_CARDS]; variable 153 for (i = 0; i < ARRAY_SIZE(devices); ++i) in snd_virmidi_unregister_all() 154 platform_device_unregister(devices[i]); in snd_virmidi_unregister_all() 180 devices[i] = device; in alsa_card_virmidi_init()`
/linux-4.4.14/drivers/pci/
D	remove.c	`75 &bus->devices, bus_list) in pci_stop_bus_device() 89 &bus->devices, bus_list) in pci_remove_bus_device() 136 &bus->devices, bus_list) in pci_stop_root_bus() 154 &bus->devices, bus_list) in pci_remove_root_bus()`
D	Kconfig	`69 PCI devices from a PCI backend to support PCI driver domains. 72 bool "Interrupts on hypertransport devices" 76 This allows native hypertransport devices to use interrupts. 88 I/O Virtualization is a PCI feature supported by some devices 89 which allows them to create virtual devices which share their 99 PRI is the PCI Page Request Interface. It allows PCI devices that are 109 Process Address Space Identifiers (PASIDs) can be used by PCI devices`
/linux-4.4.14/arch/arm/mach-ixp4xx/
D	goramo_mlr.c	359 int i, devices = 1; /* flash / in gmlr_init() local 402 device_tab[devices++] = &device_uarts; / max index 1 / in gmlr_init() 405 device_tab[devices++] = &device_eth_tab[0]; / max index 2 / in gmlr_init() 407 device_tab[devices++] = &device_eth_tab[1]; / max index 3 / in gmlr_init() 410 device_tab[devices++] = &device_hss_tab[0]; / max index 4 / in gmlr_init() 412 device_tab[devices++] = &device_hss_tab[1]; / max index 5 / in gmlr_init() 415 device_tab[devices++] = &device_i2c; / max index 6 */ in gmlr_init() 446 platform_add_devices(device_tab, devices); in gmlr_init()
/linux-4.4.14/init/
D	do_mounts_md.c	`130 dev_t devices[MD_SB_DISKS+1]; in md_setup_drive() local 170 devices[i] = dev; in md_setup_drive() 174 devices[i] = 0; in md_setup_drive() 204 while (devices[ainfo.raid_disks]) in md_setup_drive() 214 dev = devices[i]; in md_setup_drive() 227 dev = devices[i]; in md_setup_drive()`
/linux-4.4.14/drivers/hid/usbhid/
D	Kconfig	`11 mice, joysticks, graphic tablets, or any other HID based devices 13 (UPS) and monitor control devices. 32 devices. 38 Say Y here if you want to support HID devices (from the USB 40 devices, like monitor controls and Uninterruptable Power Supplies. 42 This module supports these devices separately using a separate`
/linux-4.4.14/Documentation/rapidio/
D	sysfs.txt	9 subdirectory with the following name, /sys/bus/rapidio/devices/<device_name>. 21 /sys/bus/rapidio/devices/00:e:0000 22 /sys/bus/rapidio/devices/00:e:0002 23 /sys/bus/rapidio/devices/00:s:0001 51 This attribute is similar in behavior to the "config" attribute of PCI devices 79 lnext - returns names of devices linked to the switch except one of a device 116 devices: "rapidio_port". 134 0 = small (8-bit destination ID, max. 256 devices), 135 1 = large (16-bit destination ID, max. 65536 devices). 140 devices are described in Section 1 above. [all …]
/linux-4.4.14/arch/arm/firmware/
D	Kconfig	`16 Some devices (including most Tegra-based consumer devices on the 22 required on devices using Trusted Foundations. See`
/linux-4.4.14/drivers/pcmcia/
D	cardbus.c	`34 list_for_each_entry(dev, &bus->devices, bus_list) { in cardbus_config_irq_and_cls() 80 list_for_each_entry(dev, &bus->devices, bus_list) in cb_alloc() 122 list_for_each_entry_safe(dev, tmp, &bus->devices, bus_list) in cb_free()`
/linux-4.4.14/arch/arm/mach-sa1100/
D	pleb.c	`61 static struct platform_device *devices[] __initdata = { variable 107 platform_add_devices(devices, ARRAY_SIZE(devices)); in pleb_init()`
/linux-4.4.14/arch/arm/mach-imx/
D	mach-scb9328.c	`106 static struct platform_device *devices[] __initdata = { variable 126 platform_add_devices(devices, ARRAY_SIZE(devices)); in scb9328_init()`
D	mach-apf9328.c	`112 static struct platform_device *devices[] __initdata = { variable 132 platform_add_devices(devices, ARRAY_SIZE(devices)); in apf9328_init()`
/linux-4.4.14/drivers/iommu/
D	dmar.c	113 void dmar_free_dev_scope(struct dmar_dev_scope *devices, int cnt) in dmar_free_dev_scope() argument 118 if (devices && cnt) { in dmar_free_dev_scope() 119 for_each_active_dev_scope(devices, cnt, i, tmp_dev) in dmar_free_dev_scope() 121 kfree(devices); in dmar_free_dev_scope() 124 devices = NULL; in dmar_free_dev_scope() 222 struct dmar_dev_scope *devices, in dmar_insert_dev_scope() argument 251 for_each_dev_scope(devices, devices_cnt, i, tmp) in dmar_insert_dev_scope() 253 devices[i].bus = info->dev->bus->number; in dmar_insert_dev_scope() 254 devices[i].devfn = info->dev->devfn; in dmar_insert_dev_scope() 255 rcu_assign_pointer(devices[i].dev, in dmar_insert_dev_scope() [all …]
/linux-4.4.14/drivers/mtd/
D	Kconfig	6 used for solid state file systems on embedded devices. This option 8 themselves with the kernel and for potential users of MTD devices 9 to enumerate the devices which are present and obtain a handle on 11 particular hardware and users of MTD devices. If unsure, say N. 30 'images' in flash devices by putting a table one of the erase 117 The ARM Firmware Suite allows the user to divide flash devices into 148 This provides partions parsing for BCM63xx devices with CFE 155 This provides partitions parser for devices based on BCM47xx 167 tristate "Caching block device access to MTD devices" 172 as block devices, it is possible to use MTD devices which are based [all …]
/linux-4.4.14/Documentation/PCI/
D	pci-iov-howto.txt	`15 devices. The physical device is referred to as Physical Function (PF) 16 while the virtual devices are referred to as Virtual Functions (VF). 44 The second method is the recommended method for new/future VF devices. 48 The VF is treated as hot-plugged PCI devices in the kernel, so they 49 should be able to work in the same way as real PCI devices. The VF 62 /sys/bus/pci/devices/<DOMAIN:BUS:DEVICE.FUNCTION>/sriov_numvfs 69 /sys/bus/pci/devices/<DOMAIN:BUS:DEVICE.FUNCTION>/sriov_numvfs`
/linux-4.4.14/block/
D	Kconfig	`11 kernel. This may be useful for embedded devices. 18 Also, SCSI character devices and USB storage will be disabled since 27 bool "Support for large (2TB+) block devices and files" 31 Enable block devices or files of size 2TB and larger. 34 (2TB+) block devices, including RAID, disk, Network Block Device, 82 Some storage devices allow extra information to be 108 the kernel boot args. This is typically of use for embedded devices`
/linux-4.4.14/drivers/gpu/host1x/
D	bus.c	32 static LIST_HEAD(devices); 226 list_for_each_entry(device, &host1x->devices, list) { in host1x_add_client() 248 list_for_each_entry_safe(device, dt, &host1x->devices, list) { in host1x_del_client() 407 list_add_tail(&device->list, &host1x->devices); in host1x_device_add() 450 list_for_each_entry(device, &host1x->devices, list) { in host1x_attach_driver() 471 list_for_each_entry_safe(device, tmp, &host1x->devices, list) in host1x_detach_driver() 483 list_add_tail(&host1x->list, &devices); in host1x_register() 527 list_for_each_entry(host1x, &devices, list) in host1x_driver_register_full() 554 list_for_each_entry(host1x, &devices, list) { in host1x_client_register() 580 list_for_each_entry(host1x, &devices, list) { in host1x_client_unregister()
/linux-4.4.14/Documentation/devicetree/bindings/input/
D	e3x0-button.txt	`9 - "ettus,e3x0-button": For devices such as the NI Ettus Research USRP E3x0 13 - <0 30 1>, <0 31 1>: For devices such as the NI Ettus Research USRP E3x0 15 - "press", "release": For devices such as the NI Ettus Research USRP E3x0`
/linux-4.4.14/Documentation/devicetree/bindings/iommu/
D	samsung,sysmmu.txt	`5 devices like MFC, FIMC, FIMD, GScaler, FIMC-IS and so forth. 13 System MMUs are in many to one relation with peripheral devices, i.e. single 27 to implement child devices or sub-devices which are the client devices of the 33 the "Generic IOMMU Binding" support for attaching devices to the IOMMU.`
/linux-4.4.14/include/linux/
D	dmar.h	`57 struct dmar_dev_scope devices;/ target device array / member 116 struct dmar_dev_scope devices, u16 segment); 118 extern void dmar_free_dev_scope(struct dmar_dev_scope devices, int cnt); 121 struct dmar_dev_scope devices, 124 u16 segment, struct dmar_dev_scope devices,`
/linux-4.4.14/Documentation/fmc/
D	API.txt	`30 The functions to register and unregister n devices are meant to be used 31 by carriers that host more than one mezzanine. The devices must all be 33 devices in the array are affected. Usually, the driver matching the 34 first device will reprogram the FPGA, so other devices must know they 37 If a carrier hosts slots that are driven by different FPGA devices, it`
/linux-4.4.14/Documentation/dvb/
D	README.dvb-usb	1 Documentation for dvb-usb-framework module and its devices 28 The source code of the particular DVB USB devices does just the communication 35 Objective is to migrate all the usb-devices (dibusb, cinergyT2, maybe the 42 Supported devices 54 2005-04-17 - all dibusb devices ported to make use of the dvb-usb-framework 65 2005-01-31 - distorted streaming is gone for USB1.1 devices 70 - tuner quirks for some weird devices (Artec T1 AN2235 device has sometimes a 83 2004-11-05 - added support for a new devices (Grandtec/Avermedia/Artec) 168 2.1. Adding support for devices 174 A lot of the currently supported devices are USB1.1 and thus they have a [all …]
/linux-4.4.14/sound/usb/line6/
D	Kconfig	`10 This is a driver for PODxt and other similar devices, 27 This is a driver for POD HD300, 400 and 500 devices. 35 This is a driver for TonePort GX, UX1 and UX2 devices.`
/linux-4.4.14/drivers/media/platform/vivid/
D	Kconfig	`21 Say Y here if you want to test video apps or debug V4L devices. 25 int "Maximum number of devices" 29 This allows you to specify the maximum number of devices supported`
/linux-4.4.14/Documentation/acpi/
D	enumeration.txt	5 devices behind serial bus controllers. 8 SoC/Chipset to appear only in ACPI namespace. These are typically devices 15 platform devices. 21 As both ACPI and Device Tree represent a tree of devices (and their 25 The ACPI implementation enumerates devices behind busses (platform, SPI and 26 I2C), creates the physical devices and binds them to their ACPI handle in 35 Since we are using platform devices to represent devices that are not 67 like to be accessible to slave devices via generic API call 142 Slave devices behind SPI bus have SpiSerialBus resource attached to them. 143 This is extracted automatically by the SPI core and the slave devices are [all …]
/linux-4.4.14/drivers/usb/storage/
D	Kconfig	12 Say Y here if you want to connect USB mass storage devices to your 15 USB flash devices, and memory sticks, along with 16 similar devices. This driver may also be used for some cameras 21 (BLK_DEV_SD) for most USB storage devices. 69 Say Y here if you want to use USB Mass Store devices based 87 Say Y here to include additional code to support storage devices 139 and Fujifilm DPC-R1 USB Card reader/writer devices. 141 These devices are based on the Alauda chip and support both 179 Say Y here if you want to use SAT (ata pass through) on devices based 198 (BLK_DEV_SD) for most USB storage devices. [all …]
/linux-4.4.14/drivers/md/
D	dm-table.c	57 struct list_head devices; member 191 INIT_LIST_HEAD(&t->devices); in dm_table_create() 215 static void free_devices(struct list_head devices, struct mapped_device md) in free_devices() argument 219 list_for_each_safe(tmp, next, devices) { in free_devices() 253 free_devices(&t->devices, t->md); in dm_table_destroy() 405 dd = find_device(&t->devices, dev); in dm_get_device() 417 list_add(&dd->list, &t->devices); in dm_get_device() 464 struct list_head devices = &ti->table->devices; in dm_put_device() local 467 list_for_each_entry(dd, devices, list) { in dm_put_device() 840 struct list_head devices; in dm_table_set_type() local [all …]
/linux-4.4.14/drivers/misc/mic/
D	Kconfig	`43 Core (MIC) family of PCIe form factor coprocessor devices that 46 devices are currently supported. 65 virtio devices. Intel MIC X100 devices are currently supported. 81 Core (MIC) family of PCIe form factor coprocessor devices that 101 devices. COSM drivers implement functions such as boot, 102 shutdown, reset and reboot of MIC devices.`
/linux-4.4.14/net/wimax/
D	Kconfig	`10 Select to configure support for devices that provide 14 Please note that most of these devices require signing up 20 Broadband devices`
/linux-4.4.14/drivers/s390/block/
D	Kconfig	`24 prompt "Support for DASD devices" 34 prompt "Profiling support for dasd devices" 45 ECKD devices are the most commonly used devices. You should enable 53 Select this option to be able to access FBA devices. It is safe to`
/linux-4.4.14/drivers/pci/pcie/
D	aspm.c	132 list_for_each_entry(child, &linkbus->devices, bus_list) in pcie_set_clkpm_nocheck() 159 list_for_each_entry(child, &linkbus->devices, bus_list) { in pcie_clkpm_cap_init() 191 child = list_entry(linkbus->devices.next, struct pci_dev, bus_list); in pcie_aspm_configure_common_clock() 205 list_for_each_entry(child, &linkbus->devices, bus_list) { in pcie_aspm_configure_common_clock() 243 list_for_each_entry(child, &linkbus->devices, bus_list) in pcie_aspm_configure_common_clock() 359 child = list_entry(linkbus->devices.next, struct pci_dev, bus_list); in pcie_aspm_cap_init() 395 list_for_each_entry(child, &linkbus->devices, bus_list) { in pcie_aspm_cap_init() 403 list_for_each_entry(child, &linkbus->devices, bus_list) { in pcie_aspm_cap_init() 457 list_for_each_entry(child, &linkbus->devices, bus_list) in pcie_config_aspm_link() 488 list_for_each_entry(child, &pdev->subordinate->devices, bus_list) { in pcie_aspm_sanity_check() [all …]

12 3 4 5 6 7 8 9 10

Project(s)

Full Search
Definition
Symbol
File Path
History
Type