| /openbmc/openbmc/meta-google/recipes-google/gpio/gpio-ctrl/ |
| H A D | lib.sh | 69 local sysfs
71 sysfs="${gpio_sysfs_lookup_cache["$id"]}"
75 if ! sysfs="$(grep -xl "$val" /sys/class/gpio/gpiochip*/label)"; then
79 sysfs="${sysfs%/label}"
82 for sysfs in $(echo /sys/class/gpio/gpiochip*); do
87 sysfs=
89 if [ -z "$sysfs" ]; then
99 gpio_sysfs_lookup_cache["$id"]="$sysfs"
103 ngpio=$(<"$sysfs"/ngpio)
105 echo "$name with gpiochip $sysfs only has $ngpio but wants $offset" >&2
[all …]
|
| /openbmc/linux/Documentation/translations/zh_TW/filesystems/ |
| H A D | sysfs.txt | 30 sysfs - 用於導出內核對象(kobject)的文件系統
39 sysfs 簡介:
45 sysfs 始終與 kobject 的底層結構緊密相關。請閱讀
50 使用 sysfs
56 mount -t sysfs sysfs /sys
64 內核的對象層次到用戶空間。sysfs 中的頂層目錄代表著內核對象層次的
153 sysfs 會爲這個類型調用適當的方法。當一個文件被讀寫時，這個方法會
259 sysfs 目錄的安排顯示了內核數據結構之間的關係。
261 頂層 sysfs 目錄如下:
293 設備 sysfs 接口快捷的方法。
[all …]
|
| /openbmc/linux/Documentation/translations/zh_CN/filesystems/ |
| H A D | sysfs.txt | 27 sysfs - 用于导出内核对象(kobject)的文件系统
36 sysfs 简介:
42 sysfs 始终与 kobject 的底层结构紧密相关。请阅读
47 使用 sysfs
53 mount -t sysfs sysfs /sys
61 内核的对象层次到用户空间。sysfs 中的顶层目录代表着内核对象层次的
150 sysfs 会为这个类型调用适当的方法。当一个文件被读写时，这个方法会
256 sysfs 目录的安排显示了内核数据结构之间的关系。
258 顶层 sysfs 目录如下:
290 设备 sysfs 接口快捷的方法。
[all …]
|
| /openbmc/linux/tools/testing/selftests/cgroup/ |
| H A D | with_stress.sh | 19 echo $verb$subsys_ctrl >$sysfs/cgroup.subtree_control
28 sysfs=`mount -t cgroup2 | head -1 | awk '{ print $3 }'`
29 if [ ! -d "$sysfs" ]; then
34 if ! echo +$subsys_ctrl >$sysfs/cgroup.subtree_control ; then
35 echo "Skipping: cannot enable $subsys_ctrl in $sysfs" >&2
39 if ! echo -$subsys_ctrl >$sysfs/cgroup.subtree_control ; then
40 echo "Skipping: cannot disable $subsys_ctrl in $sysfs" >&2
50 sysfs=
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-tty | 30 sysfs rather than via ioctls.
39 sysfs rather than via ioctls.
48 sysfs rather than via ioctls.
57 sysfs rather than via ioctls.
66 sysfs rather than via ioctls.
75 sysfs rather than via ioctls.
84 sysfs rather than via ioctls.
93 sysfs rather than via ioctls.
102 sysfs rather than via ioctls.
111 sysfs rather than via ioctls.
[all …]
|
| H A D | sysfs-bus-event_source-devices-hv_gpci | 6 (See ABI/testing/sysfs-bus-event_source-devices-format).
81 This sysfs file exposes the cpumask which is designated to make
94 * User needs root privileges to read data from this sysfs file.
105 Possible error codes while reading this sysfs file:
126 * User needs root privileges to read data from this sysfs file.
137 Possible error codes while reading this sysfs file:
158 * User needs root privileges to read data from this sysfs file.
169 Possible error codes while reading this sysfs file:
190 * User needs root privileges to read data from this sysfs file.
201 Possible error codes while reading this sysfs file:
[all …]
|
| H A D | sysfs-class-firmware | 5 Description: The data sysfs file is used for firmware-fallback and for
6 firmware uploads. Cat a firmware image to this sysfs file
7 after you echo 1 to the loading sysfs file. When the firmware
8 image write is complete, echo 0 to the loading sysfs file. This
30 for the status sysfs file and <ERROR> will be one of the
33 error sysfs file is only meaningful when the current firmware
41 Description: The loading sysfs file is used for both firmware-fallback and
43 you are writing a firmware file to the data sysfs node. Echo
57 written to the data sysfs file. This value is periodically
|
| /openbmc/openbmc/meta-openembedded/meta-networking/recipes-daemons/openhpi/files/ |
| H A D | openhpi-sysfs-cross-compile.patch | 1 Fix sysfs when cross-compiling
3 Use proper paths for sysfs plugins when cross-compiling
11 diff --git a/plugins/sysfs/sysfs2hpi.c b/plugins/sysfs/sysfs2hpi.c
13 --- a/plugins/sysfs/sysfs2hpi.c
14 +++ b/plugins/sysfs/sysfs2hpi.c
20 +#include <sysfs/libsysfs.h>
|
| /openbmc/linux/fs/sysfs/ |
| H A D | Kconfig | 3 bool "sysfs file system support" if EXPERT
7 The sysfs filesystem is a virtual filesystem that the kernel uses to
11 Users can use sysfs to ascertain useful information about the running
13 which driver each is bound to. sysfs can also be used to tune devices
16 Some system agents rely on the information in sysfs to operate.
17 /sbin/hotplug uses device and object attributes in sysfs to assist in
20 sysfs is currently used by the block subsystem to mount the root
21 partition. If sysfs is disabled you must specify the boot device on
|
| /openbmc/linux/tools/testing/selftests/powerpc/dscr/ |
| H A D | dscr_sysfs_test.c | 32 DIR *sysfs; in check_all_cpu_dscr_defaults() local
36 sysfs = opendir(CPU_PATH); in check_all_cpu_dscr_defaults()
37 if (!sysfs) { in check_all_cpu_dscr_defaults()
42 while ((dp = readdir(sysfs))) { in check_all_cpu_dscr_defaults()
59 closedir(sysfs); in check_all_cpu_dscr_defaults()
63 closedir(sysfs); in check_all_cpu_dscr_defaults()
|
| /openbmc/linux/Documentation/networking/ |
| H A D | sysfs-tagging.rst | 10 The problem. Network devices show up in sysfs and with the network
16 sysfs, sysfs now has tagging directory support.
19 the sysfs directory entries we ensure that we don't have conflicts
23 Each sysfs directory entry may be tagged with a namespace via the
29 Each sysfs superblock's kernfs_super_info contains an array
31 kobj_nstype first mounts sysfs, a new superblock is created. It
32 will be differentiated from other sysfs mounts by having its
35 the contents of other namespaces' sysfs mounts. Therefore, when a
|
| /openbmc/linux/Documentation/gpu/amdgpu/ |
| H A D | flashing.rst | 9 For supported GPUs, `amdgpu` will export a series of sysfs files that can be
15 2. "Write" the IFWI image to the sysfs file `psp_vbflash`. This will stage the IFWI in memory.
16 3. "Read" from the `psp_vbflash` sysfs file to initiate the flash process.
17 4. Poll the `psp_vbflash_status` sysfs file to determine when the flash process completes.
22 is done using the `usbc_pd_fw` sysfs file.
25 * Writing the name of a firmware payload stored in `/lib/firmware/amdgpu` to the sysfs file will in…
31 sysfs files
|
| H A D | ras.rst | 5 The AMDGPU RAS interfaces are exposed via sysfs (for informational queries) and
8 RAS debugfs/sysfs Control and Error Injection Interfaces
20 RAS Error Count sysfs Interface
24 :doc: AMDGPU RAS sysfs Error Count Interface
32 RAS VRAM Bad Pages sysfs Interface
36 :doc: AMDGPU RAS sysfs gpu_vram_bad_pages Interface
48 The test verifies the RAS feature enabled status and makes sure the necessary sysfs and debugfs fil…
|
| /openbmc/linux/tools/lib/api/fs/ |
| H A D | fs.c | 146 FS(sysfs, sysfs, SYSFS);
430 const char *sysfs = sysfs__mountpoint(); in sysfs__read_ull_base() local
432 if (!sysfs) in sysfs__read_ull_base()
435 snprintf(path, sizeof(path), "%s/%s", sysfs, entry); in sysfs__read_ull_base()
453 const char *sysfs = sysfs__mountpoint(); in sysfs__read_int() local
455 if (!sysfs) in sysfs__read_int()
458 snprintf(path, sizeof(path), "%s/%s", sysfs, entry); in sysfs__read_int()
466 const char *sysfs = sysfs__mountpoint(); in sysfs__read_str() local
468 if (!sysfs) in sysfs__read_str()
521 const char *sysfs = sysfs__mountpoint(); in sysfs__write_int() local
[all …]
|
| /openbmc/linux/Documentation/translations/zh_CN/userspace-api/ |
| H A D | sysfs-platform_profile.rst | 4 :Original: Documentation/userspace-api/sysfs-platform_profile.rst
20 platform_profile属性的目的是提供一个通用的sysfs API来选择这些平台自动配置
32 sysfs-platform_profile ABI 文档定义了一个固定的配置文件名集合。驱动程序
40 sysfs-platform_profile ABI文档中。
|
| /openbmc/linux/Documentation/translations/zh_CN/core-api/ |
| H A D | kobject.rst | 28 特定的类型，并且，通常在sysfs虚拟文件系统中表示。
43 当你看到一个下面全是其他目录的sysfs目录时，通常这些目录中的每一个都对应
193 有时，开发者想要的只是在sysfs层次结构中创建一个简单的目录，而不必去搞那些复杂
199 这个函数将创建一个kobject，并将其放在sysfs中指定的父kobject下面的位置。要创
221 道，那么使用kobject就没有什么意义。当sysfs被引入时，即使是可预测的对象生命
274 类型的对象如何在 sysfs 中被表示；它们超出了本文的范围。
291 - kset也是sysfs中的一个子目录，与kset相关的kobjects可以在这里显示
293 sysfs层次结构的顶级目录就是以这种方式构建的。
316 来销毁它。这将从sysfs中删除该kset并递减其引用计数值。当引用计数
361 sysfs内务将被正确处理。
[all …]
|
| /openbmc/linux/Documentation/filesystems/ |
| H A D | sysfs.rst | 4 sysfs - _The_ filesystem for exporting kernel objects
18 sysfs is a RAM-based filesystem initially based on ramfs. It provides
22 sysfs is tied inherently to the kobject infrastructure. Please read
27 Using sysfs
33 mount -t sysfs sysfs /sys
40 created for it in sysfs. That directory is created as a subdirectory
42 userspace. Top-level directories in sysfs represent the common
46 sysfs internally stores a pointer to the kobject that implements a
127 For the common cases sysfs.h provides convenience macros to make
290 The top level sysfs directory looks like::
[all …]
|
| /openbmc/linux/Documentation/translations/zh_CN/PCI/ |
| H A D | sysfs-pci.rst | 4 :Original: Documentation/PCI/sysfs-pci.rst
15 通过sysfs访问PCI设备资源
18 sysfs，通常挂载在/sys，在支持它的平台上提供对PCI资源的访问。例如，一个特定的总线可能看起
92 拔功能，例如关闭设备的电源。该设备被从内核的PCI设备列表中移除，它的sysfs目录被移除，并且该
95 通过sysfs访问原有资源
98 如果底层平台支持的话，传统的I/O端口和ISA内存资源也会在sysfs中提供。它们位于PCI类的层次结构
|
| /openbmc/linux/Documentation/translations/zh_CN/admin-guide/mm/damon/ |
| H A D | usage.rst | 24 - *sysfs接口。*
26 使用它，用户可以通过读取和写入特殊的sysfs文件来使用DAMON的主要功能。因此，你可以编写和使
27 用你个性化的DAMON sysfs包装程序，代替你读/写sysfs文件。 `DAMON用户空间工具
34 :ref:`sysfs interface <sysfs_interface>`。
40 sysfs接口
42 DAMON的sysfs接口是在定义 ``CONFIG_DAMON_SYSFS`` 时建立的。它在其sysfs目录下创建多
43 个目录和文件， ``<sysfs>/kernel/mm/damon/`` 。你可以通过对该目录下的文件进行写入和
58 DAMON sysfs接口的文件层次结构如下图所示。在下图中，父子关系用缩进表示，每个目录有
95 DAMON sysfs接口的根是 ``<sysfs>/kernel/mm/damon/`` ，它有一个名为 ``admin`` 的
311 # cd <sysfs>/kernel/mm/damon/admin
[all …]
|
| /openbmc/linux/Documentation/driver-api/rapidio/ |
| H A D | sysfs.rst | 5 The RapidIO sysfs files have moved to:
6 Documentation/ABI/testing/sysfs-bus-rapidio and
7 Documentation/ABI/testing/sysfs-class-rapidio
|
| /openbmc/linux/Documentation/driver-api/firmware/ |
| H A D | fw_upload.rst | 8 persistent sysfs nodes to enable users to initiate firmware updates for
11 upload uses the same *loading* and *data* sysfs files described in the
12 documentation for firmware fallback. It also adds additional sysfs files
21 firmware upload by echoing a 1 to the *loading* sysfs file for the target
22 device. Next, the user writes the firmware image to the *data* sysfs
24 sysfs file to signal completion. Echoing 0 to *loading* also triggers the
99 Corresponding strings are reported through the status sysfs node that
116 In addition to the *loading* and *data* sysfs files, there are additional
117 sysfs files to monitor the status of the data transfer to the target
122 The additional sysfs files are:
|
| /openbmc/linux/Documentation/admin-guide/ |
| H A D | video-output.rst | 6 The output sysfs class driver provides an abstract video output layer that
8 device through common sysfs interface. For example, on my IBM ThinkPad T42
10 method for 'state' with output sysfs class. The user interface under sysfs is::
|
| /openbmc/linux/Documentation/translations/zh_CN/infiniband/ |
| H A D | sysfs.rst | 3 :Original: Documentation/infiniband/sysfs.rst
20 sysfs接口已移至
21 Documentation/ABI/stable/sysfs-class-infiniband.
|
| /openbmc/linux/mm/damon/ |
| H A D | Makefile | 6 obj-$(CONFIG_DAMON_SYSFS) += sysfs-common.o sysfs-schemes.o sysfs.o
|
| /openbmc/linux/Documentation/translations/zh_TW/cpu-freq/ |
| H A D | cpufreq-stats.rst | 13 sysfs CPUFreq Stats的一般說明
32 這些統計數據在/sysfs中以一堆只讀接口的形式提供。這個接口（在配置好後）將出現在
33 /sysfs（<sysfs root>/devices/system/cpu/cpuX/cpufreq/stats/）中cpufreq下的一個單
131 一旦啓用了這個選項，並且你的CPU支持cpufrequency，你就可以在/sysfs中看到CPU頻率統計。
|