Home
last modified time | relevance | path

Searched refs:sysfs (Results 1 – 25 of 599) sorted by relevance

12345678910>>...24

/Linux-v4.19/samples/mic/mpssd/
Dmicctrl32 sysfs="/sys/class/mic"
36 f=$sysfs/$1
46 for f in $sysfs/*
57 f=$sysfs/$1
67 for f in $sysfs/*
78 f=$sysfs/$1
91 for f in $sysfs/*
102 f=$sysfs/$1
112 for f in $sysfs/*
123 f=$sysfs/$1
[all …]
Dmpss37 sysfs="/sys/class/mic"
80 for f in $sysfs/*
109 if [ ! -d "$sysfs" ]; then
120 for f in $sysfs/*
161 if [ ! -d "$sysfs" ]; then
/Linux-v4.19/Documentation/translations/zh_CN/filesystems/
Dsysfs.txt1 Chinese translated version of Documentation/filesystems/sysfs.txt
13 Documentation/filesystems/sysfs.txt 的中文翻译
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-v4.19/Documentation/ABI/testing/
Dsysfs-tty29 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 …]
Dsysfs-class-lcd-s6e63m01 sysfs interface for the S6E63M0 AMOLED LCD panel driver
25 documented in Documentation/ABI/testing/sysfs-class-lcd and in
26 Documentation/ABI/stable/sysfs-class-backlight (under
/Linux-v4.19/fs/sysfs/
DKconfig2 bool "sysfs file system support" if EXPERT
6 The sysfs filesystem is a virtual filesystem that the kernel uses to
10 Users can use sysfs to ascertain useful information about the running
12 which driver each is bound to. sysfs can also be used to tune devices
15 Some system agents rely on the information in sysfs to operate.
16 /sbin/hotplug uses device and object attributes in sysfs to assist in
19 sysfs is currently used by the block subsystem to mount the root
20 partition. If sysfs is disabled you must specify the boot device on
/Linux-v4.19/Documentation/filesystems/
Dsysfs-tagging.txt7 The problem. Network devices show up in sysfs and with the network
13 sysfs, sysfs now has tagging directory support.
16 the sysfs directory entries we ensure that we don't have conflicts
20 Each sysfs directory entry may be tagged with a namespace via the
26 Each sysfs superblock's kernfs_super_info contains an array void
28 kobj_nstype first mounts sysfs, a new superblock is created. It
29 will be differentiated from other sysfs mounts by having its
32 the contents of other namespaces' sysfs mounts. Therefore, when a
Dsysfs.txt2 sysfs - _The_ filesystem for exporting kernel objects.
14 sysfs is a ram-based filesystem initially based on ramfs. It provides
18 sysfs is tied inherently to the kobject infrastructure. Please read
23 Using sysfs
26 sysfs is always compiled in if CONFIG_SYSFS is defined. You can access
29 mount -t sysfs sysfs /sys
36 created for it in sysfs. That directory is created as a subdirectory
38 userspace. Top-level directories in sysfs represent the common
44 the past this kobject pointer has been used by sysfs to do reference
46 With the current sysfs implementation the kobject reference count is
[all …]
/Linux-v4.19/tools/lib/api/fs/
Dfs.c294 FS(sysfs, FS__SYSFS);
439 const char *sysfs = sysfs__mountpoint(); in sysfs__read_ull_base() local
441 if (!sysfs) in sysfs__read_ull_base()
444 snprintf(path, sizeof(path), "%s/%s", sysfs, entry); in sysfs__read_ull_base()
462 const char *sysfs = sysfs__mountpoint(); in sysfs__read_int() local
464 if (!sysfs) in sysfs__read_int()
467 snprintf(path, sizeof(path), "%s/%s", sysfs, entry); in sysfs__read_int()
475 const char *sysfs = sysfs__mountpoint(); in sysfs__read_str() local
477 if (!sysfs) in sysfs__read_str()
480 snprintf(path, sizeof(path), "%s/%s", sysfs, entry); in sysfs__read_str()
[all …]
/Linux-v4.19/tools/testing/selftests/powerpc/dscr/
Ddscr_sysfs_test.c45 DIR *sysfs; in check_all_cpu_dscr_defaults() local
49 sysfs = opendir(CPU_PATH); in check_all_cpu_dscr_defaults()
50 if (!sysfs) { in check_all_cpu_dscr_defaults()
55 while ((dp = readdir(sysfs))) { in check_all_cpu_dscr_defaults()
74 closedir(sysfs); in check_all_cpu_dscr_defaults()
/Linux-v4.19/Documentation/rapidio/
Dsysfs.txt1 The RapidIO sysfs files have moved to:
2 Documentation/ABI/testing/sysfs-bus-rapidio and
3 Documentation/ABI/testing/sysfs-class-rapidio
/Linux-v4.19/Documentation/
Dvideo-output.txt6 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:
/Linux-v4.19/tools/testing/selftests/cpufreq/
Dmain.sh49 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-v4.19/fs/configfs/
DKconfig6 of sysfs's functionality. Where sysfs is a filesystem-based
10 Both sysfs and configfs can and should exist together on the
/Linux-v4.19/Documentation/driver-model/
Doverview.txt80 file system named sysfs.
87 none on /sys type sysfs (rw,noexec,nosuid,nodev)
91 The auto-mounting of sysfs is typically accomplished by an entry similar to
94 none /sys sysfs defaults 0 0
98 none /sys sysfs nodev,noexec,nosuid 0 0
100 If sysfs is not automatically mounted, you can always do it manually with:
102 # mount -t sysfs sysfs /sys
120 More information about the sysfs directory layout can be found in
122 Documentation/filesystems/sysfs.txt.
/Linux-v4.19/Documentation/hwmon/
Dw83791d82 See below for the description of the sysfs-interface.
89 The sysfs interface to the global enable is via the sysfs beep_enable file.
92 The sysfs interface to the beep bitmask has migrated from the original legacy
93 method of a single sysfs beep_mask file to a newer method using multiple
94 *_beep files as described in .../Documentation/hwmon/sysfs-interface.
97 original legacy method used a single sysfs alarms file containing a bitmap
98 of triggered alarms. The newer method uses multiple sysfs *_alarm files
99 (again following the pattern described in sysfs-interface).
107 NOTE: All new code should be written to use the newer sysfs-interface
116 The sysfs-interface is documented in the 'sysfs-interface' file. Only
Dtmp40144 The driver provides the common sysfs-interface for temperatures (see
45 Documentation/hwmon/sysfs-interface under Temperatures).
52 Exported via sysfs attributes tempX_lowest and tempX_highest.
56 Exported via sysfs attribute temp_reset_history. Writing 1 to this
67 Exported via sysfs attribute tempX_offset
Dacpi_power_meter20 sysfs interface conforms with the specification outlined in the "Power" section
21 of Documentation/hwmon/sysfs-interface.
30 power[1-*]_average sysfs file.
37 the case, the power[1-*]_cap and related sysfs files will appear. When the
46 well as sent as a poll notification to a sysfs file. The events are as
Dlm9373 sysfs files prochot1, prochot2, prochot1_avg, prochot2_avg, prochot1_max,
83 These intervals can be found in the sysfs files prochot1_interval and
94 non-zero integer to the sysfs file prochot_short.
101 The sysfs files prochot1_override and prochot2_override contain boolean
103 #P2_PROCHOT, respectively. The sysfs file prochot_override_duty_cycle
111 sysfs files vrdhot1 and vrdhot2. There is one value per file: a boolean for
126 the fan tachometer with a pwm) to the sysfs file fan<n>_smart_tach. A zero
134 15.10.6 of the datasheet for details.) The sysfs files pwm1_override
136 where 0 disables and 1 enables the manual control mode. The sysfs files pwm1
147 The sysfs files pwm1_freq and pwm2_freq are used to select the frequency. The
[all …]
/Linux-v4.19/tools/perf/util/
Dpmu.c86 const char *sysfs = sysfs__mountpoint(); in pmu_format() local
88 if (!sysfs) in pmu_format()
92 "%s" EVENT_SOURCE_DEVICE_PATH "%s/format", sysfs, name); in pmu_format()
474 const char *sysfs = sysfs__mountpoint(); in pmu_aliases() local
476 if (!sysfs) in pmu_aliases()
480 "%s/bus/event_source/devices/%s/events", sysfs, name); in pmu_aliases()
526 const char *sysfs = sysfs__mountpoint(); in pmu_type() local
528 if (!sysfs) in pmu_type()
532 "%s" EVENT_SOURCE_DEVICE_PATH "%s/type", sysfs, name); in pmu_type()
554 const char *sysfs = sysfs__mountpoint(); in pmu_read_sysfs() local
[all …]
/Linux-v4.19/Documentation/admin-guide/
Dsysfs-rules.rst1 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-v4.19/tools/perf/arch/arm64/util/
Dheader.c16 const char *sysfs = sysfs__mountpoint(); in get_cpuid_str() local
22 if (!sysfs || !pmu || !pmu->cpus) in get_cpuid_str()
33 sysfs, cpus->map[cpu]); in get_cpuid_str()
/Linux-v4.19/drivers/media/usb/pvrusb2/
DMakefile2 obj-pvrusb2-sysfs-$(CONFIG_VIDEO_PVRUSB2_SYSFS) := pvrusb2-sysfs.o
16 $(obj-pvrusb2-sysfs-y) $(obj-pvrusb2-debugifc-y)
/Linux-v4.19/drivers/video/fbdev/omap2/omapfb/dss/
DMakefile8 omapdss-y += manager.o manager-sysfs.o overlay.o overlay-sysfs.o apply.o \
9 dispc-compat.o display-sysfs.o
/Linux-v4.19/Documentation/translations/zh_CN/
Dgpio.txt307 * 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 节点的)接口。

12345678910>>...24