| /linux/Documentation/ABI/testing/ |
| H A 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 …]
|
| 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
88 This sysfs file exposes the system topology information by making HCALL
92 * This sysfs file will be created only for power10 and above platforms.
94 * User needs root privileges to read data from this sysfs file.
96 * This sysfs file will be created, only when the HCALL returns "H_SUCCESS",
102 * The end user reading this sysfs file must decode the content as per
105 Possible error codes while reading this sysfs file:
120 This sysfs file exposes the system topology information by making HCALL
124 * This sysfs file will be created only for power10 and above platforms.
[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
|
| /linux/Documentation/translations/zh_CN/filesystems/ |
| H A 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/Documentation/translations/zh_TW/filesystems/ |
| H A D | sysfs.txt | 3 Chinese translated version of Documentation/filesystems/sysfs.rst
15 Documentation/filesystems/sysfs.rst 的中文翻譯
30 sysfs - 用於導出內核對象(kobject)的文件系統
39 sysfs 簡介:
42 sysfs 是一個最初基於 ramfs 且位於內存的文件系統。它提供導出內核
45 sysfs 始終與 kobject 的底層結構緊密相關。請閱讀
50 使用 sysfs
53 只要內核配置中定義了 CONFIG_SYSFS ，sysfs 總是被編譯進內核。你可
56 mount -t sysfs sysfs /sys
62 任何 kobject 在系統中註冊，就會有一個目錄在 sysfs 中被創建。這個
[all …]
|
| /linux/drivers/base/ |
| H A D | auxiliary_sysfs.c | 29 guard(mutex)(&auxdev->sysfs.lock); in auxiliary_irq_dir_prepare()
30 if (auxdev->sysfs.irq_dir_exists) in auxiliary_irq_dir_prepare()
37 auxdev->sysfs.irq_dir_exists = true; in auxiliary_irq_dir_prepare()
38 xa_init(&auxdev->sysfs.irqs); in auxiliary_irq_dir_prepare()
43 * auxiliary_device_sysfs_irq_add - add a sysfs entry for the given IRQ
44 * @auxdev: auxiliary bus device to add the sysfs entry.
73 ret = xa_insert(&auxdev->sysfs.irqs, irq, info, GFP_KERNEL); in auxiliary_device_sysfs_irq_add()
83 xa_store(&auxdev->sysfs.irqs, irq, no_free_ptr(info), GFP_KERNEL); in auxiliary_device_sysfs_irq_add()
87 xa_erase(&auxdev->sysfs.irqs, irq); in auxiliary_device_sysfs_irq_add()
93 * auxiliary_device_sysfs_irq_remove - remove a sysfs entry for the given IRQ
[all …]
|
| /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
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
46 sysfs internally stores a pointer to the kobject that implements a
48 the past this kobject pointer has been used by sysfs to do reference
[all …]
|
| /linux/include/uapi/linux/ |
| H A D | if.h | 47 * set these flags using userspace utilities but there is also a sysfs
49 * are shared for all types of net_devices. The sysfs entries are available
50 * via /sys/class/net/<dev>/flags. Flags which can be toggled through sysfs
53 * even if you try to set them via sysfs. Flags which are always preserved
59 * @IFF_UP: interface is up. Can be toggled through sysfs.
61 * @IFF_DEBUG: turn on debugging. Can be toggled through sysfs.
64 * @IFF_NOTRAILERS: avoid use of trailers. Can be toggled through sysfs.
67 * @IFF_NOARP: no ARP protocol. Can be toggled through sysfs. Volatile.
68 * @IFF_PROMISC: receive all packets. Can be toggled through sysfs.
70 * sysfs.
[all …]
|
| /linux/fs/sysfs/ |
| H A D | Kconfig | 2 config SYSFS config
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/Documentation/networking/ |
| H A D | sysfs-tagging.rst | 4 Sysfs tagging
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/tools/testing/selftests/cpu-hotplug/ |
| H A D | cpu-on-off-test.sh | 4 SYSFS=
20 SYSFS=`mount -t sysfs | head -1 | awk '{ print $3 }'`
22 if [ ! -d "$SYSFS" ]; then
23 echo $msg sysfs is not mounted >&2
27 if ! ls $SYSFS/devices/system/cpu/cpu* > /dev/null 2>&1; then
33 online_cpus=`cat $SYSFS/devices/system/cpu/online`
41 present_cpus=`cat $SYSFS/devices/system/cpu/present`
47 offline_cpus=`cat $SYSFS/devices/system/cpu/offline`
63 for cpu in $SYSFS/devices/system/cpu/cpu*; do
82 grep -q 1 $SYSFS/devices/system/cpu/cpu$1/online
[all …]
|
| /linux/tools/testing/selftests/powerpc/dscr/ |
| H A D | dscr_sysfs_test.c | 3 * POWER Data Stream Control Register (DSCR) sysfs interface test
5 * This test updates to system wide DSCR default through the sysfs interface
7 * well verified from their sysfs interfaces.
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()
|
| /linux/Documentation/admin-guide/ |
| H A 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/Documentation/admin-guide/laptops/ |
| H A D | thinkpad-acpi.rst | 88 is a new sysfs-based interface which is not complete yet.
94 all new functionality will be implemented on the sysfs interface.
96 The sysfs interface tries to blend in the generic Linux sysfs subsystems
102 Notes about the sysfs interface
106 to the sysfs interfaces will be enforced, as will correctness in the
107 thinkpad-acpi's implementation of sysfs interfaces.
109 Also, any bugs in the thinkpad-acpi sysfs driver code or in the
110 thinkpad-acpi's implementation of the sysfs interfaces will be fixed for
115 Applications interfacing to the thinkpad-acpi sysfs interfaces must
116 follow all sysfs guidelines and correctly process all errors (the sysfs
[all …]
|
| /linux/tools/testing/selftests/gpio/ |
| H A D | gpio-mockup-sysfs.sh | 4 # Overrides functions in gpio-mockup.sh to test using the GPIO SYSFS uAPI
6 SYSFS=`grep -w sysfs /proc/mounts | cut -f2 -d' '`
7 [ -d "$SYSFS" ] || skip "sysfs is not mounted"
9 GPIO_SYSFS="${SYSFS}/class/gpio"
12 PLATFORM_SYSFS=$SYSFS/devices/platform
17 # determine the sysfs GPIO number given the $chip and $offset
|
| /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
113 Sysfs Attributes
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
[all …]
|
| /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=
|
| /linux/tools/lib/api/fs/ |
| H A D | fs.c | 147 FS(sysfs, sysfs, SYSFS);
218 * testing). This matches the recommendation in Documentation/admin-guide/sysfs-rules.rst
402 const char *sysfs = sysfs__mountpoint(); in sysfs__read_ull_base() local
404 if (!sysfs) in sysfs__read_ull_base()
407 snprintf(path, sizeof(path), "%s/%s", sysfs, entry); in sysfs__read_ull_base()
425 const char *sysfs = sysfs__mountpoint(); in sysfs__read_int() local
427 if (!sysfs) in sysfs__read_int()
430 snprintf(path, sizeof(path), "%s/%s", sysfs, entry); in sysfs__read_int()
438 const char *sysfs = sysfs__mountpoint(); in sysfs__read_str() local
440 if (!sysfs) in sysfs__read_str()
[all …]
|
| /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…
|
| /linux/Documentation/userspace-api/gpio/ |
| H A D | sysfs.rst | 1 GPIO Sysfs Interface for Userspace
6 been moved to Documentation/ABI/obsolete/sysfs-gpio.
15 The obsolete sysfs ABI
18 configure a sysfs user interface to GPIOs. This is different from the
37 Do NOT abuse sysfs to control hardware that has proper kernel drivers.
43 Paths in Sysfs
102 sysfs file and read the new value or close the file and
155 /* create a sysfs link to an exported GPIO node */
160 the sysfs interface by gpiod_export(). The driver can control whether the
169 symlinks from elsewhere in sysfs to the GPIO sysfs node. Drivers can
[all …]
|
| /linux/Documentation/driver-api/driver-model/ |
| H A 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/tools/testing/selftests/memory-hotplug/ |
| H A D | mem-on-off-test.sh | 4 SYSFS=
18 SYSFS=`mount -t sysfs | head -1 | awk '{ print $3 }'`
20 if [ ! -d "$SYSFS" ]; then
21 echo $msg sysfs is not mounted >&2
25 if ! ls $SYSFS/devices/system/memory/memory* > /dev/null 2>&1; then
30 if ! grep -q 1 $SYSFS/devices/system/memory/memory*/removable; then
43 for memory in $SYSFS/devices/system/memory/memory*; do
63 grep -q online $SYSFS/devices/system/memory/memory$1/state
68 grep -q offline $SYSFS/devices/system/memory/memory$1/state
73 echo online > $SYSFS/devices/system/memory/memory$1/state
[all …]
|
| /linux/Documentation/hwmon/ |
| H A D | lm93.rst | 83 sysfs files prochot1, prochot2, prochot1_avg, prochot2_avg, prochot1_max,
93 These intervals can be found in the sysfs files prochot1_interval and
105 non-zero integer to the sysfs file prochot_short.
112 The sysfs files prochot1_override and prochot2_override contain boolean
114 #P2_PROCHOT, respectively. The sysfs file prochot_override_duty_cycle
123 sysfs files vrdhot1 and vrdhot2. There is one value per file: a boolean for
136 fan tachometer with a pwm) to the sysfs file fan<n>_smart_tach. A zero
145 15.10.6 of the datasheet for details.) The sysfs files pwm1_override
147 where 0 disables and 1 enables the manual control mode. The sysfs files pwm1
159 The sysfs files pwm1_freq and pwm2_freq are used to select the frequency. The
[all …]
|
| /linux/drivers/base/firmware_loader/ |
| H A D | fallback.c | 68 * fw_load_sysfs_fallback() - load a firmware via the sysfs fallback mechanism
69 * @fw_sysfs: firmware sysfs information for the firmware to load
72 * In charge of constructing a sysfs fallback interface for firmware loading.
187 pr_info_once("Ignoring firmware sysfs fallback due to sysctl knob\n"); in fw_run_sysfs_fallback()
194 /* Also permit LSMs and IMA to fail firmware sysfs fallback */ in fw_run_sysfs_fallback()
212 * a fallback mechanism through userspace by exposing a sysfs loading
213 * interface. Userspace is in charge of loading the firmware through the sysfs
214 * loading interface. This sysfs fallback mechanism may be disabled completely
218 * mechanism. A system may want to enforce the sysfs fallback mechanism at all
233 dev_warn(device, "Falling back to sysfs fallback for: %s\n", in firmware_fallback_sysfs()
[all …]
|