| /openbmc/linux/drivers/platform/mellanox/ |
| H A D | Kconfig | 32 space through sysfs interface. The sets of registers for sysfs access
68 does not boot up correctly. This driver provides sysfs access
80 Mellanox BlueField SoC via a sysfs interface.
|
| /openbmc/linux/Documentation/driver-api/firmware/ |
| H A D | fallback-mechanisms.rst | 57 There are really two fallback mechanisms available using one shared sysfs
63 First lets document the shared sysfs loading facility.
65 Firmware sysfs loading facility
69 the firmware infrastructure creates a sysfs interface to enable userspace
70 to load and indicate when firmware is ready. The sysfs directory is created
74 The sysfs directory's file attributes are defined and controlled through
83 To load firmware using the sysfs interface we expose a loading indicator,
120 Since a device is created for the sysfs interface to help load firmware as a
168 at their disposal: rely on the sysfs fallback mechanism but request that no
193 onto the sysfs interface by the timeout value an error is sent to the
[all …]
|
| /openbmc/linux/Documentation/driver-api/iio/ |
| H A D | core.rst | 49 IIO device sysfs interface
52 Attributes are sysfs files used to expose chip info and also allowing
63 :file:`Documentation/ABI/testing/sysfs-bus-iio` file in the Linux kernel
91 Channel sysfs attributes exposed to userspace are specified in the form of
140 This channel's definition will generate two separate sysfs files for raw data
150 and one shared sysfs file for sampling frequency:
|
| H A D | triggers.rst | 18 a specific file in sysfs). A trigger may initiate data capture for a number of
21 IIO trigger sysfs interface
24 There are two locations in sysfs related to triggers:
|
| /openbmc/linux/Documentation/admin-guide/laptops/ |
| H A D | toshiba_haps.rst | 27 however, this driver only provides a notification via a sysfs file to let
28 userspace tools or daemons act accordingly, as well as providing a sysfs
72 The sysfs files under /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS620A:00/ are:
|
| /openbmc/linux/Documentation/arch/x86/x86_64/ |
| H A D | machinecheck.rst | 4 Configurable sysfs parameters for the x86-64 machine check code
25 Documentation/ABI/testing/sysfs-mce for more details.
|
| /openbmc/linux/Documentation/hwmon/ |
| H A D | emc2305.rst | 24 The driver provides the following sysfs interfaces in hwmon subsystem:
32 sysfs interfaces in thermal subsystem:
|
| H A D | pwm-fan.rst | 17 the hwmon's sysfs interface.
22 The driver provides the following sensor accesses in sysfs:
|
| H A D | sbrmi.rst | 45 sysfs-Interface
48 on ``sysfs``, under the directory ``/sys/class/hwmon/hwmonX`` for some value
73 Also, Below shows how get and set the values from sysfs entries individually::
|
| H A D | tmp108.rst | 40 The driver provides the common sysfs-interface for temperatures (see
41 Documentation/hwmon/sysfs-interface.rst under Temperatures).
|
| H A D | sysfs-interface.rst | 1 Naming and data format standards for sysfs files
5 through the sysfs interface. Since lm-sensors 3.0.0, libsensors is
7 implement the standard sysfs interface described in this document.
26 An alternative method that some programs use is to access the sysfs
33 Each chip gets its own directory in the sysfs /sys/devices tree. To
44 All sysfs values are fixed point numbers.
63 When setting values of hwmon sysfs attributes, the string representation of
66 "sysfs attribute writes interpretation" section at the end of this file.
92 See Documentation/ABI/testing/sysfs-class-hwmon for a complete description
606 sysfs attribute writes interpretation
[all …]
|
| /openbmc/linux/Documentation/trace/coresight/ |
| H A D | coresight-config.rst | 15 can then be easily enabled from sysfs or perf.
174 using CoreSight with sysfs.
243 Using Configurations in sysfs
246 Coresight can be controlled using sysfs. When this is in use then a configuration
247 can be made active for the devices that are used in the sysfs session.
251 To enable a configuration for use with sysfs::
267 Note that the active sysfs configuration is a global parameter, therefore
268 only a single configuration can be active for sysfs at any one time.
273 The use of the active configuration by sysfs is independent of the configuration
|
| /openbmc/linux/Documentation/driver-api/ |
| H A D | generic-counter.rst | 320 Signal's directory in sysfs.
328 Count's directory in sysfs.
385 | Counter sysfs | | Counter chrdev |
389 | sysfs output | | character device |
425 | Counter sysfs | | Counter chrdev |
429 | sysfs output | | character device |
465 Counter sysfs
467 Translates counter data to the standard Counter sysfs interface format
472 sysfs attributes.
487 on each Generic Counter interface sysfs attribute.
[all …]
|
| /openbmc/linux/Documentation/w1/slaves/ |
| H A D | w1_ds28e04.rst | 20 Support is provided through the sysfs files "eeprom" and "pio". CRC checking
37 The 2 PIOs of the DS28E04-100 are accessible via the "pio" sysfs file.
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-kernel-fadump | 5 The /sys/kernel/fadump/* is a collection of FADump sysfs
30 This is a special sysfs file and only available when
|
| H A D | sysfs-class-pktcdvd | 1 sysfs interface
4 sysfs: (<devid> is in the format major:minor)
87 To use the pktcdvd sysfs interface directly, you can do::
|
| H A D | sysfs-class-mic | 59 When written, this sysfs entry triggers different state change
67 sysfs entries.
112 When read, this sysfs entry provides the path name under
122 When read, this sysfs entry provides the path name under
132 When read, this sysfs entry provides the current bootmode for
133 the card. This sysfs entry can be written with the following
|
| /openbmc/phosphor-fan-presence/docs/presence/ |
| H A D | eeprom.md | 21 subsystem in sysfs.
29 The name of the eeprom driver in sysfs.
|
| /openbmc/linux/drivers/base/firmware_loader/ |
| H A D | Kconfig | 90 bool "Enable the firmware sysfs fallback mechanism"
94 This option enables a sysfs loading facility to enable firmware
100 built-in. For details on how to work with the sysfs fallback mechanism
106 the requested firmware a sysfs fallback loading facility is made
163 bool "Force the firmware sysfs fallback mechanism when possible"
166 Enabling this option forces a sysfs userspace fallback mechanism
220 bool "Enable users to initiate firmware updates using sysfs"
225 sysfs interface that allows firmware updates to be initiated from
|
| /openbmc/linux/drivers/firmware/ |
| H A D | Kconfig | 55 BIOS tries boot from. This information is then exported via sysfs.
71 bool "Add firmware-provided memory map to sysfs" if EXPERT
78 See also Documentation/ABI/testing/sysfs-firmware-memmap.
105 bool "Export DMI identification via sysfs to userspace"
114 tristate "DMI table support in sysfs"
119 data via sysfs. This is useful for consuming the data without
145 Boot Firmware Table (iBFT) via sysfs to userspace. If you wish to
157 tristate "QEMU fw_cfg device support in sysfs"
163 configuration (fw_cfg) file entries via sysfs. Entries are
193 access through the Intel Service Layer to user space via sysfs
|
| /openbmc/linux/Documentation/arch/s390/ |
| H A D | vfio-ap.rst | 39 sysfs device entries::
74 represented in a bitmask and stored in a sysfs file
92 following sysfs entries::
312 * sysfs attribute structures:
319 sysfs structures for each mediated device type specified in the
353 sysfs attributes for a vfio_ap mediated device are:
391 domains assigned via the corresponding sysfs attributes files
627 respective sysfs mask file in one of two formats:
815 sysfs file.
863 - Must NOT be assigned while the sysfs /sys/bus/ap/apmask and
[all …]
|
| /openbmc/linux/Documentation/admin-guide/perf/ |
| H A D | qcom_l3_pmu.rst | 12 options in sysfs, see /sys/devices/l3cache*. Given that these are uncore PMUs
13 the driver also exposes a "cpumask" sysfs attribute which contains a mask
|
| /openbmc/linux/Documentation/devicetree/bindings/leds/ |
| H A D | leds-trigger-pattern.txt | 15 For example (using sysfs interface):
35 For example (using sysfs interface):
|
| /openbmc/linux/Documentation/translations/zh_CN/core-api/ |
| H A D | padata.rst | 54 过sysfs。前者的定义是::
63 一个实例的cpumasks可能有sysfs文件。例如，pcrypt的文件在
|
| /openbmc/linux/Documentation/admin-guide/mm/ |
| H A D | zswap.rst | 34 Zswap can also be enabled and disabled at runtime using the sysfs interface.
35 An example command to enable zswap at runtime, assuming sysfs is mounted
63 e.g. ``zswap.zpool=zbud``. It can also be changed at runtime using the sysfs
96 It can also be changed at runtime using the sysfs "compressor"
117 disabled at runtime using the sysfs ``same_filled_pages_enabled``
134 It can also be enabled and disabled at runtime using the sysfs
149 again after it became full, use the sysfs ``accept_threshold_percent``
|