| /Linux-v5.10/Documentation/translations/zh_CN/filesystems/ |
| D | sysfs.txt | 1 Chinese translated version of Documentation/filesystems/sysfs.rst
13 Documentation/filesystems/sysfs.rst 的中文翻译
27 sysfs - 用于导出内核对象(kobject)的文件系统
36 sysfs 简介:
39 sysfs 是一个最初基于 ramfs 且位于内存的文件系统。它提供导出内核
42 sysfs 始终与 kobject 的底层结构紧密相关。请阅读
47 使用 sysfs
50 只要内核配置中定义了 CONFIG_SYSFS ，sysfs 总是被编译进内核。你可
53 mount -t sysfs sysfs /sys
59 任何 kobject 在系统中注册，就会有一个目录在 sysfs 中被创建。这个
[all …]
|
| /Linux-v5.10/Documentation/ABI/testing/ |
| D | sysfs-tty | 29 These sysfs values expose the TIOCGSERIAL interface via
30 sysfs rather than via ioctls.
38 These sysfs values expose the TIOCGSERIAL interface via
39 sysfs rather than via ioctls.
47 These sysfs values expose the TIOCGSERIAL interface via
48 sysfs rather than via ioctls.
56 These sysfs values expose the TIOCGSERIAL interface via
57 sysfs rather than via ioctls.
65 These sysfs values expose the TIOCGSERIAL interface via
66 sysfs rather than via ioctls.
[all …]
|
| D | sysfs-bus-event_source-devices-hv_24x7 | 6 (See ABI/testing/sysfs-bus-event_source-devices-format).
41 also extractable from the provided binary "catalog" sysfs entry.
48 extractable from the provided binary "catalog" sysfs entry.
54 This sysfs interface exposes the number of sockets present in the
61 This sysfs interface exposes the number of chips per socket
68 This sysfs interface exposes the number of cores per chip
75 This sysfs file exposes the cpumask which is designated to make
|
| /Linux-v5.10/tools/testing/selftests/cgroup/ |
| 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=
|
| /Linux-v5.10/fs/sysfs/ |
| 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
|
| /Linux-v5.10/Documentation/networking/ |
| 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
|
| /Linux-v5.10/tools/lib/api/fs/ |
| D | fs.c | 313 FS(sysfs, FS__SYSFS);
458 const char *sysfs = sysfs__mountpoint(); in sysfs__read_ull_base() local
460 if (!sysfs) in sysfs__read_ull_base()
463 snprintf(path, sizeof(path), "%s/%s", sysfs, entry); in sysfs__read_ull_base()
481 const char *sysfs = sysfs__mountpoint(); in sysfs__read_int() local
483 if (!sysfs) in sysfs__read_int()
486 snprintf(path, sizeof(path), "%s/%s", sysfs, entry); in sysfs__read_int()
494 const char *sysfs = sysfs__mountpoint(); in sysfs__read_str() local
496 if (!sysfs) in sysfs__read_str()
499 snprintf(path, sizeof(path), "%s/%s", sysfs, entry); in sysfs__read_str()
[all …]
|
| /Linux-v5.10/tools/testing/selftests/powerpc/dscr/ |
| D | dscr_sysfs_test.c | 42 DIR *sysfs; in check_all_cpu_dscr_defaults() local
46 sysfs = opendir(CPU_PATH); in check_all_cpu_dscr_defaults()
47 if (!sysfs) { in check_all_cpu_dscr_defaults()
52 while ((dp = readdir(sysfs))) { in check_all_cpu_dscr_defaults()
71 closedir(sysfs); in check_all_cpu_dscr_defaults()
|
| /Linux-v5.10/Documentation/filesystems/ |
| 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
30 sysfs is always compiled in if CONFIG_SYSFS is defined. You can access
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
48 the past this kobject pointer has been used by sysfs to do reference
50 With the current sysfs implementation the kobject reference count is
[all …]
|
| D | efivarfs.rst | 8 using entries in sysfs to maintain EFI variables. The old sysfs EFI
12 than a single page, sysfs isn't the best interface for this.
43 - Documentation/ABI/stable/sysfs-firmware-efi-vars
|
| /Linux-v5.10/Documentation/driver-api/rapidio/ |
| 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
|
| /Linux-v5.10/Documentation/admin-guide/ |
| 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::
|
| D | sysfs-rules.rst | 1 Rules on how to access information in sysfs
4 The kernel-exported sysfs exports internal kernel implementation details
7 internal API. Therefore, there are aspects of the sysfs interface that
10 To minimize the risk of breaking users of sysfs, which are in most cases
12 of sysfs must follow some rules to use an as-abstract-as-possible way to
15 abstractions these programs provide instead of accessing sysfs directly.
17 But if you really do want or need to access sysfs directly, please follow
19 versions of the sysfs interface.
22 It makes assumptions about sysfs which are not true. Its API does not
28 to sysfs has failed; it causes more problems than it solves. It
[all …]
|
| /Linux-v5.10/drivers/hwtracing/coresight/ |
| D | Makefile | 7 coresight-sysfs.o
17 coresight-etm3x-sysfs.o
19 coresight-etm4x-y := coresight-etm4x-core.o coresight-etm4x-sysfs.o
25 coresight-cti-sysfs.o
|
| /Linux-v5.10/Documentation/gpu/ |
| D | amdgpu.rst | 90 The AMDGPU RAS interfaces are exposed via sysfs (for informational queries) and
93 RAS debugfs/sysfs Control and Error Injection Interfaces
105 RAS Error Count sysfs Interface
109 :doc: AMDGPU RAS sysfs Error Count Interface
117 RAS VRAM Bad Pages sysfs Interface
121 :doc: AMDGPU RAS sysfs gpu_vram_bad_pages Interface
133 The test verifies the RAS feature enabled status and makes sure the necessary sysfs and debugfs fil…
161 GPU sysfs Power State Interfaces
164 GPU power controls are exposed via sysfs files.
221 via sysfs
[all …]
|
| /Linux-v5.10/tools/testing/selftests/cpufreq/ |
| D | main.sh | 49 SYSFS=`mount -t sysfs | head -1 | awk '{ print $3 }'`
52 echo $msg sysfs is not mounted >&2
60 echo $msg cpus not available in sysfs >&2
65 echo $msg cpufreq directory not available in sysfs >&2
|
| /Linux-v5.10/tools/perf/util/ |
| D | pmu.c | 89 const char *sysfs = sysfs__mountpoint(); in pmu_format() local
91 if (!sysfs) in pmu_format()
95 "%s" EVENT_SOURCE_DEVICE_PATH "%s/format", sysfs, name); in pmu_format()
481 const char *sysfs = sysfs__mountpoint(); in pmu_aliases() local
483 if (!sysfs) in pmu_aliases()
487 "%s/bus/event_source/devices/%s/events", sysfs, name); in pmu_aliases()
532 const char *sysfs = sysfs__mountpoint(); in pmu_type() local
534 if (!sysfs) in pmu_type()
538 "%s" EVENT_SOURCE_DEVICE_PATH "%s/type", sysfs, name); in pmu_type()
560 const char *sysfs = sysfs__mountpoint(); in pmu_read_sysfs() local
[all …]
|
| /Linux-v5.10/Documentation/driver-api/driver-model/ |
| D | overview.rst | 82 file system named sysfs.
89 none on /sys type sysfs (rw,noexec,nosuid,nodev)
93 The auto-mounting of sysfs is typically accomplished by an entry similar to
96 none /sys sysfs defaults 0 0
100 none /sys sysfs nodev,noexec,nosuid 0 0
102 If sysfs is not automatically mounted, you can always do it manually with::
104 # mount -t sysfs sysfs /sys
122 More information about the sysfs directory layout can be found in
124 Documentation/filesystems/sysfs.rst.
|
| /Linux-v5.10/fs/configfs/ |
| D | Kconfig | 7 of sysfs's functionality. Where sysfs is a filesystem-based
11 Both sysfs and configfs can and should exist together on the
|
| /Linux-v5.10/Documentation/hwmon/ |
| D | w83791d.rst | 93 See below for the description of the sysfs-interface.
100 The sysfs interface to the global enable is via the sysfs beep_enable file.
103 The sysfs interface to the beep bitmask has migrated from the original legacy
104 method of a single sysfs beep_mask file to a newer method using multiple
105 `*_beep` files as described in `Documentation/hwmon/sysfs-interface.rst`.
108 original legacy method used a single sysfs alarms file containing a bitmap
109 of triggered alarms. The newer method uses multiple sysfs `*_alarm` files
110 (again following the pattern described in sysfs-interface).
118 NOTE: All new code should be written to use the newer sysfs-interface
127 The sysfs-interface is documented in the 'sysfs-interface' file. Only
|
| D | tmp401.rst | 70 The driver provides the common sysfs-interface for temperatures (see
71 Documentation/hwmon/sysfs-interface.rst under Temperatures).
78 Exported via sysfs attributes tempX_lowest and tempX_highest.
82 Exported via sysfs attribute temp_reset_history. Writing 1 to this
93 Exported via sysfs attribute tempX_offset
|
| D | acpi_power_meter.rst | 23 sysfs interface conforms with the specification outlined in the "Power" section
24 of Documentation/hwmon/sysfs-interface.rst.
33 `power[1-*]_average` sysfs file.
40 the case, the `power[1-*]_cap` and related sysfs files will appear. When the
49 well as sent as a poll notification to a sysfs file. The events are as
|
| /Linux-v5.10/drivers/video/fbdev/omap2/omapfb/dss/ |
| D | Makefile | 8 omapdss-y += manager.o manager-sysfs.o overlay.o overlay-sysfs.o apply.o \
9 dispc-compat.o display-sysfs.o
|
| /Linux-v5.10/drivers/media/usb/pvrusb2/ |
| D | Makefile | 2 obj-pvrusb2-sysfs-$(CONFIG_VIDEO_PVRUSB2_SYSFS) := pvrusb2-sysfs.o
16 $(obj-pvrusb2-sysfs-y) $(obj-pvrusb2-debugifc-y)
|
| /Linux-v5.10/Documentation/translations/zh_CN/ |
| D | gpio.txt | 307 * GPIOF_EXPORT_DIR_FIXED - 将 gpio 导出到 sysfs，并保持方向
531 使用“gpiolib”实现框架的平台可以选择配置一个 GPIO 的 sysfs 用户接口。
597 sysfs 文件的开始部分，也可以关闭这个文件并重新打开它来读取数据。
637 /* 创建一个 sysfs 连接到已导出的 GPIO 节点 */
641 在一个内核驱动申请一个 GPIO 之后，它可以通过 gpio_export()使其在 sysfs
648 在 GPIO 被导出之后，gpio_export_link()允许在 sysfs 文件系统的任何地方
649 创建一个到这个 GPIO sysfs 节点的符号链接。这样驱动就可以通过一个描述性的
650 名字，在 sysfs 中他们所拥有的设备下提供一个(到这个 GPIO sysfs 节点的)接口。
|
