| /f-stack/freebsd/contrib/device-tree/Bindings/leds/ |
| H A D | leds-trigger-pattern.txt | 15 For example (using sysfs interface):
35 For example (using sysfs interface):
|
| /f-stack/freebsd/x86/linux/ |
| H A D | linux_dummy_x86.c | 54 DUMMY(sysfs);
|
| /f-stack/freebsd/contrib/openzfs/etc/init.d/ |
| H A D | zfs-share.in | 37 after sysfs zfs-mount zfs-zed
|
| H A D | zfs-mount.in | 60 after zfs-import sysfs
|
| H A D | zfs-import.in | 42 after sysfs udev
|
| /f-stack/freebsd/contrib/device-tree/Bindings/power/supply/ |
| H A D | lt3651-charger.txt | 19 cannot report changes and userspace will need to periodically read the sysfs
|
| /f-stack/freebsd/contrib/openzfs/module/zcommon/ |
| H A D | zfeature_common.c | 167 zfs_mod_supported_impl(const char *scope, const char *name, const char *sysfs) in zfs_mod_supported_impl() argument
172 int len = asprintf(&path, "%s%s%s%s%s", sysfs, in zfs_mod_supported_impl()
|
| /f-stack/freebsd/contrib/device-tree/Bindings/arm/ |
| H A D | coresight-cpu-debug.txt | 37 "nohlt" in the kernel command line or sysfs node to
|
| H A D | coresight.txt | 122 can be configured dynamically via buffer_size property in sysfs.
|
| /f-stack/freebsd/contrib/device-tree/Bindings/rtc/ |
| H A D | isil,isl12057.txt | 14 get access to the 'wakealarm' sysfs entry, this specific property can
|
| /f-stack/freebsd/contrib/device-tree/Bindings/hwmon/ |
| H A D | baikal,bt1-pvt.yaml | 46 implement the sysfs files-based access to the sensors functionality.
|
| /f-stack/dpdk/doc/guides/nics/ |
| H A D | netvsc.rst | 55 by looking at the sysfs information. To find the UUID for eth1 and
79 On older kernels, the same effect can be had by manual sysfs bind and unbind
|
| H A D | liquidio.rst | 67 Echo number of VFs to be created into ``"sriov_numvfs"`` sysfs entry
|
| H A D | bnx2x.rst | 165 Echo the number of VFs to be created into "sriov_numvfs" sysfs entry
|
| H A D | qede.rst | 234 Echo the number of VFs to be created into ``"sriov_numvfs"`` sysfs entry
|
| H A D | thunderx.rst | 309 Use sysfs to distinguish thunder-nic primary VFs and secondary VFs.
|
| H A D | mlx4.rst | 373 verbs. Related sysfs entries should be present::
|
| /f-stack/dpdk/doc/guides/cryptodevs/ |
| H A D | octeontx.rst | 82 The number of crypto VFs to be enabled can be controlled by setting sysfs entry,
|
| /f-stack/dpdk/doc/guides/rawdevs/ |
| H A D | octeontx2_ep.rst | 25 The number of SDP VFs enabled, can be controlled by setting sysfs
|
| H A D | octeontx2_dma.rst | 44 The number of DMA VFs (queues) enabled can be controlled by setting sysfs
|
| H A D | ioat.rst | 52 The device configuration can also be done by directly interacting with the sysfs nodes.
109 If the device is bound to the IDXD kernel driver (and previously configured with sysfs),
|
| /f-stack/dpdk/doc/guides/eventdevs/ |
| H A D | octeontx.rst | 117 The same can be verified by looking at the following sysfs entry:
|
| /f-stack/dpdk/doc/guides/linux_gsg/ |
| H A D | enable_func.rst | 113 * The userspace-io sysfs config and resource files, for example for ``uio0``::
|
| H A D | linux_drivers.rst | 31 the user can create the VFs using the ``sysfs`` interface,
|
| /f-stack/dpdk/doc/guides/rel_notes/ |
| H A D | release_18_11.rst | 435 via ``sysfs`` interface: ``echo 1 > /sys/class/net/vEth0/carrier``.
437 Note interface should be ``up`` to be able to read/write sysfs interface.
|