Home
last modified time | relevance | path

Searched refs:sysfs (Results 1 – 200 of 459) sorted by relevance

123

/linux-4.1.27/Documentation/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"
82 for f in $sysfs/*
111 if [ ! -d "$sysfs" ]; then
122 for f in $sysfs/*
163 if [ ! -d "$sysfs" ]; then
DMakefile4 mpssd-objs := mpssd.o sysfs.o
/linux-4.1.27/drivers/gpu/drm/nouveau/
Dnouveau_sysfs.c50 struct nouveau_sysfs *sysfs = nouveau_sysfs(drm_device(d)); in nouveau_sysfs_pstate_get() local
56 ret = nvif_mthd(&sysfs->ctrl, NVIF_CONTROL_PSTATE_INFO, in nouveau_sysfs_pstate_get()
69 ret = nvif_mthd(&sysfs->ctrl, NVIF_CONTROL_PSTATE_ATTR, in nouveau_sysfs_pstate_get()
84 ret = nvif_mthd(&sysfs->ctrl, in nouveau_sysfs_pstate_get()
120 struct nouveau_sysfs *sysfs = nouveau_sysfs(drm_device(d)); in nouveau_sysfs_pstate_set() local
149 ret = nvif_mthd(&sysfs->ctrl, NVIF_CONTROL_PSTATE_USER, in nouveau_sysfs_pstate_set()
163 struct nouveau_sysfs *sysfs = nouveau_sysfs(dev); in nouveau_sysfs_fini() local
167 if (sysfs && sysfs->ctrl.priv) { in nouveau_sysfs_fini()
169 nvif_object_fini(&sysfs->ctrl); in nouveau_sysfs_fini()
172 drm->sysfs = NULL; in nouveau_sysfs_fini()
[all …]
Dnouveau_sysfs.h13 return nouveau_drm(dev)->sysfs; in nouveau_sysfs()
/linux-4.1.27/Documentation/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-4.1.27/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-dev5 Description: The /sys/dev tree provides a method to look up the sysfs
10 corresponding sysfs path for the given device.
Dsysfs-class-pktcdvd7 sysfs interface
11 these files in the sysfs:
62 To use the pktcdvd sysfs interface directly, you can do:
Dsysfs-bus-rpmsg11 This sysfs entry contains the name of this channel.
26 This sysfs entry contains the src (local) rpmsg address
44 This sysfs entry contains the dst (remote) rpmsg address
73 This sysfs entry tells us whether the channel is a local
Dsysfs-class-mic.txt53 to the state sysfs entry to ensure the card is shutdown during
57 When written, this sysfs entry triggers different state change
62 sysfs entries.
105 When read, this sysfs entry provides the path name under
115 When read, this sysfs entry provides the path name under
125 When read, this sysfs entry provides the current bootmode for
126 the card. This sysfs entry can be written with the following
Dsysfs-bus-event_source-devices-hv_24x716 also extractable from the provided binary "catalog" sysfs entry.
23 extractable from the provided binary "catalog" sysfs entry.
Dsysfs-class-pwm7 Framework and provides a sysfs interface for using PWM
31 Exports a PWM channel from the PWM chip for sysfs control.
Dsysfs-firmware-dmi33 doesn't matter), they will be represented in sysfs as
50 Each DMI entry in sysfs has the common header values
81 sysfs. Not all types are specialized.
Dsysfs-bus-iio-trigger-sysfs5 This file is provided by the iio-trig-sysfs stand-alone trigger
Dsysfs-devices-sun13 So reading the sysfs file, we can identify a physical position
Dsysfs-kernel-iommu_groups10 links to the sysfs devices contained in this group.
Dsysfs-bus-usb75 sysfs restrictions.
82 extra bus folder "usb-serial" in sysfs; apart from that
91 that was dynamically added via the new_id sysfs entry.
145 is usb port device's sysfs directory.
Dsysfs-class-iommu-intel-iommu7 Format: %llx. This allows association of a sysfs
Dsysfs-class-extcon5 Provide a place in sysfs for the extcon objects.
29 this sysfs node.
Dsysfs-firmware-efi-runtime-map11 kernel. The mappings are exported to sysfs so userspace tools
/linux-4.1.27/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-4.1.27/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 zero or one
26 Each sysfs superblock's sysfs_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 …]
Defivarfs.txt5 using entries in sysfs to maintain EFI variables. The old sysfs EFI
9 than a single page, sysfs isn't the best interface for this.
D00-INDEX134 sysfs-pci.txt
135 - info on accessing PCI device resources through sysfs.
136 sysfs-tagging.txt
137 - info on sysfs tagging to avoid duplicates.
138 sysfs.txt
139 - info on sysfs, a ram-based filesystem for exporting kernel objects.
Dsysfs-pci.txt1 Accessing PCI device resources through sysfs
4 sysfs, usually mounted at /sys, provides access to PCI resources on platforms
85 PCI devices, the sysfs directory for it is removed, and the device will be
89 Accessing legacy resources through sysfs
92 Legacy I/O port and ISA memory resources are also provided in sysfs if the
/linux-4.1.27/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:
Dsysfs-rules.txt1 Rules on how to access information in the Linux kernel sysfs
3 The kernel-exported sysfs exports internal kernel implementation details
6 internal API. Therefore, there are aspects of the sysfs interface that
9 To minimize the risk of breaking users of sysfs, which are in most cases
11 of sysfs must follow some rules to use an as-abstract-as-possible way to
14 abstractions these programs provide instead of accessing sysfs directly.
16 But if you really do want or need to access sysfs directly, please follow
18 versions of the sysfs interface.
21 It makes assumptions about sysfs which are not true. Its API does not
27 to sysfs has failed; it causes more problems than it solves. It
[all …]
Diostats.txt13 the sysfs file system, which must be mounted in order to obtain
14 the information. Throughout this document we'll assume that sysfs
16 Both /proc/diskstats and sysfs use the same source for the information
26 2.6 sysfs:
36 The advantage of one over the other is that the sysfs choice works well
152 In 2.6, sysfs is not mounted by default. If your distribution of
156 none /sys sysfs defaults 0 0
Ddcdbas.txt3 The Dell Systems Management Base Driver provides a sysfs interface for
26 The driver creates the following sysfs entries for systems management
52 The driver creates the following sysfs entries for systems management software
Drfkill.txt99 soft and hard block are properly separated (unlike sysfs, see below) and
110 Additionally, each rfkill device is registered in sysfs and emits uevents.
120 "type" sysfs files explained above.
123 For further details consult Documentation/ABI/stable/sysfs-class-rfkill.
Dpwm.txt49 Using PWMs with the sysfs interface
52 If CONFIG_SYSFS is enabled in your kernel configuration a simple sysfs
60 export - Exports a PWM channel for use with sysfs (write-only).
62 unexport - Unexports a PWM channel from sysfs (write-only).
Dkobject.txt22 usually, a representation in the sysfs virtual filesystem.
42 When you see a sysfs directory full of other directories, generally each
123 register the kobject with sysfs, the function kobject_add() must be called:
214 in the sysfs hierarchy, and not have to mess with the whole complication of
221 This function will create a kobject and place it in sysfs in the location
244 predictable object lifecycles become more complicated when sysfs is brought
302 sysfs; they are beyond the scope of this document.
319 - A kset is also a subdirectory in sysfs, where the associated kobjects
322 the sysfs hierarchy are constructed in this way.
345 to destroy it. This removes the kset from sysfs and decrements its reference
[all …]
Deisa.txt4 new EISA/sysfs API.
8 has been possible through sysfs, which defines a nice enough set of
22 allocates I/O resources, allows fancy naming through sysfs, and
113 The sysfs framework calls .probe and .remove functions upon device
Dmemory-hotplug.txt17 3. sysfs files for memory hotplug
33 Note(2): This text assumes that sysfs is mounted at /sys.
68 management tables, and makes sysfs files for new memory's operation.
82 Logical Memory Hotplug phase is triggered by write of sysfs file by system
133 3 sysfs files for memory hotplug
135 All memory blocks have their device information in sysfs. Each memory block
141 For the memory block covered by the sysfs directory. It is expected that all
329 You can offline a memory block by using the same sysfs interface that was used
Dedac.txt56 to have their states harvested and presented to userspace via the sysfs
78 In the kernel there is a PCI device attribute located in sysfs that is
133 EDAC sysfs INTERFACE
135 EDAC presents a 'sysfs' interface for control, reporting and attribute
197 in EDAC's sysfs interface. Starting in directory
237 For a description of the sysfs API, please see:
238 Documentation/ABI/testing/sysfs/devices-edac
244 When CONFIG_EDAC_LEGACY_SYSFS is enabled, the sysfs will contain the
541 User space access to an edac_device is through the sysfs interface.
543 At the location /sys/devices/system/edac (sysfs) new edac_device devices will
[all …]
Dcputopology.txt2 Export CPU topology info via sysfs. Items (attributes) are similar
40 related sysfs files will only be created if CONFIG_SCHED_BOOK is selected.
/linux-4.1.27/tools/perf/util/
Dpmu.c76 const char *sysfs = sysfs__mountpoint(); in pmu_format() local
78 if (!sysfs) in pmu_format()
82 "%s" EVENT_SOURCE_DEVICE_PATH "%s/format", sysfs, name); in pmu_format()
310 const char *sysfs = sysfs__mountpoint(); in pmu_aliases() local
312 if (!sysfs) in pmu_aliases()
316 "%s/bus/event_source/devices/%s/events", sysfs, name); in pmu_aliases()
357 const char *sysfs = sysfs__mountpoint(); in pmu_type() local
359 if (!sysfs) in pmu_type()
363 "%s" EVENT_SOURCE_DEVICE_PATH "%s/type", sysfs, name); in pmu_type()
385 const char *sysfs = sysfs__mountpoint(); in pmu_read_sysfs() local
[all …]
/linux-4.1.27/Documentation/zh_CN/
Dgpio.txt307 * GPIOF_EXPORT_DIR_FIXED - 将 gpio 导出到 sysfs，并保持方向
531 使用“gpiolib”实现框架的平台可以选择配置一个 GPIO 的 sysfs 用户接口。
597 sysfs 文件的开始部分，也可以关闭这个文件并重新打开它来读取数据。
637 /* 创建一个 sysfs 连接到已导出的 GPIO 节点 */
641 /* 改变 sysfs 中的一个 GPIO 节点的极性 */
644 在一个内核驱动申请一个 GPIO 之后，它可以通过 gpio_export()使其在 sysfs
651 在 GPIO 被导出之后，gpio_export_link()允许在 sysfs 文件系统的任何地方
652 创建一个到这个 GPIO sysfs 节点的符号链接。这样驱动就可以通过一个描述性的
653 名字，在 sysfs 中他们所拥有的设备下提供一个(到这个 GPIO sysfs 节点的)接口。
656 GPIO 线的极性差异。这个仅对 sysfs 接口起作用。极性的改变可以在 gpio_export()
/linux-4.1.27/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-4.1.27/Documentation/hwmon/
Dhwmon-kernel-api.txt15 then please read the following file: Documentation/hwmon/sysfs-interface.
23 cases, <linux/hwmon-sysfs.h>. linux/hwmon.h declares the following
44 monitoring sysfs attributes are expected to have been created and attached to
50 device name. The registration function wil create a name sysfs attribute
55 a pointer to a list of sysfs attribute groups. The list must be NULL terminated.
57 as well as all sysfs attributes attached to the hwmon device.
73 The header file linux/hwmon-sysfs.h provides a number of useful macros to
74 declare and use hardware monitoring sysfs attributes.
79 will need to be passed to the sysfs attribute handling function.
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
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 …]
Dtmp40141 The driver provides the common sysfs-interface for temperatures (see
42 Documentation/hwmon/sysfs-interface under Temperatures).
49 Exported via sysfs attributes tempX_lowest and tempX_highest.
53 Exported via sysfs attribute temp_reset_history. Writing 1 to this
Dtmp10324 The driver provides the common sysfs-interface for temperatures (see
25 Documentation/hwmon/sysfs-interface under Temperatures).
Dtmp10225 The driver provides the common sysfs-interface for temperatures (see
26 Documentation/hwmon/sysfs-interface under Temperatures).
Dibmpowernv17 'hwmon' populates the 'sysfs' tree having attribute files, each for a given
21 the DT maps to an attribute file in 'sysfs'. The node exports unique 'sensor-id'
Dltc424542 into the values specified in the sysfs-interface document. The current readings
89 voltages, then the in10_input and in11_input sysfs attributes will not be
95 slowly, -EAGAIN will be returned when you read the sysfs attribute containing
Dsubmitting-patches92 completely initialize your chip first, then create sysfs entries and register
95 * Do not provide support for deprecated sysfs attributes.
101 Standard attributes are specified in Documentation/hwmon/sysfs-interface.
103 * When deciding which sysfs attributes to support, look at the chip's
Df71882fg81 The Voltage, Fan and Temperature Monitoring uses the standard sysfs
82 interface as documented in sysfs-interface, without any exceptions.
129 standard sysfs interface. The number and type of trip points is chip
130 depended, see which files are available in sysfs.
Dina2xx55 compile-time or via the shunt_resistor attribute in sysfs at run-time. Please
60 Documentation/hwmon/sysfs-interface. Internally the interval is the sum of
Dlm7328 conversion time via the 'update_interval' sysfs attribute for the
85 feature is exposed via the sysfs attributes.
Dsysfs-interface1 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.
711 sysfs attribute writes interpretation
714 hwmon sysfs attributes always contain numbers, so the first thing to do is to
[all …]
Dpwm-fan17 the hwmon's sysfs interface.
Dhih613028 sysfs-Interface
Dg7629 http://natisbad.org/NAS/ref/GMT_EDS-762_763-080710-0.2.pdf. sysfs
10 bindings are described in Documentation/hwmon/sysfs-interface.
Dfam15h_power36 package and not for a single node. Thus the driver creates sysfs
Dadt741126 sysfs-Interface
Dds62022 returned via sysfs displays post decimal positions.
Dshtc139 sysfs-Interface
Dda905524 By using sysfs attributes we can measure the system voltage VDDOUT,
Dhtu2129 sysfs-Interface
/linux-4.1.27/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.
Dporting.txt24 doing so, they will exported via the sysfs filesystem. sysfs can be
27 # mount -t sysfs sysfs /sys
131 necessary for representing devices in sysfs.
142 Also, the location of the device's sysfs directory depends on a
143 device's parent. sysfs exports a directory structure that mirrors
145 sysfs will accurately represent the hierarchy.
183 When the device is registered, a directory in sysfs is created.
184 The PCI tree in sysfs looks like:
268 Drivers are exported via sysfs in their bus's 'driver's directory.
355 symlink is created in the driver's sysfs directory that points to the
[all …]
Dclass.txt79 sysfs directory structure
81 There is a top-level sysfs directory named 'class'.
131 sysfs directory using:
137 class's directory in sysfs.
Ddevice.txt48 Attributes of devices can be exported by a device driver through sysfs.
50 Please see Documentation/filesystems/sysfs.txt for more information
51 on how sysfs works.
Dbus.txt85 sysfs
138 sysfs directory using:
/linux-4.1.27/drivers/staging/iio/light/
DKconfig16 Data from sensor is accessible via sysfs.
24 This driver supports the sysfs interface to get the ALS, IR intensity,
33 Access ALS data via iio, sysfs.
41 Provides iio_events and direct access via sysfs.
/linux-4.1.27/drivers/video/fbdev/omap2/dss/
DMakefile7 omapdss-y += manager.o manager-sysfs.o overlay.o overlay-sysfs.o apply.o \
8 dispc-compat.o display-sysfs.o
/linux-4.1.27/drivers/media/usb/pvrusb2/
DMakefile1 obj-pvrusb2-sysfs-$(CONFIG_VIDEO_PVRUSB2_SYSFS) := pvrusb2-sysfs.o
15 $(obj-pvrusb2-sysfs-y) $(obj-pvrusb2-debugifc-y)
DKconfig20 bool "pvrusb2 sysfs support"
24 This option enables the operation of a sysfs based
59 in the pvrusb2 driver, hosted through sysfs.
/linux-4.1.27/Documentation/dvb/
Dudev.txt1 The DVB subsystem currently registers to the sysfs subsystem using the
5 are presented through sysfs. Other things that might be interesting are
12 creating the DVB device nodes manually up to now due to the missing sysfs
19 sysfs device name into the well known dvb adapter / device naming scheme.
44 For every device that registers to the sysfs subsystem with a "dvb" prefix,
/linux-4.1.27/drivers/firmware/
DKconfig14 BIOS tries boot from. This information is then exported via sysfs.
30 bool "Add firmware-provided memory map to sysfs" if EXPERT
37 See also Documentation/ABI/testing/sysfs-firmware-memmap.
64 tristate "BIOS update support for DELL systems via sysfs"
79 The Dell Systems Management Base Driver provides a sysfs interface
92 bool "Export DMI identification via sysfs to userspace"
101 tristate "DMI table support in sysfs"
106 data via sysfs. This is useful for consuming the data without
131 Boot Firmware Table (iBFT) via sysfs to userspace. If you wish to
DMakefile5 obj-$(CONFIG_DMI_SYSFS) += dmi-sysfs.o
/linux-4.1.27/Documentation/thermal/
Dexynos_thermal_emulation17 When it's enabled, sysfs node will be created as
20 The sysfs node, 'emul_node', will contain value 0 for the initial state. When you input any
21 temperature you want to update to sysfs node, it automatically enable emulation mode and
33 Disabling emulation mode only requires writing value 0 to sysfs node.
Dsysfs-api.txt13 The generic thermal sysfs provides a set of interfaces for thermal zone
22 The main task of the thermal sysfs driver is to expose thermal zone attributes
31 1. thermal sysfs driver interface functions
152 .no_hwmon: a boolean to indicate if the thermal to hwmon sysfs interface
153 is required. when no_hwmon == false, a hwmon sysfs interface
160 2. sysfs attributes structure
165 Thermal sysfs attributes will be represented under /sys/class/thermal.
166 Hwmon sysfs I/F extension is also available under /sys/class/hwmon
196 Besides the thermal zone device sysfs I/F and cooling device sysfs I/F,
197 the generic thermal driver also creates a hwmon sysfs I/F for each _type_
[all …]
Dx86_pkg_temperature_thermal36 are in milli-degree Celsius. Refer to "Documentation/thermal/sysfs-api.txt" for
/linux-4.1.27/drivers/staging/iio/cdc/
DKconfig11 (ad7150, ad7151, ad7156) Provides direct access via sysfs.
21 (ad7152, ad7153) Provides direct access via sysfs.
31 (AD7745, AD7746, AD7747) Provides direct access via sysfs.
/linux-4.1.27/drivers/powercap/
DKconfig2 # Generic power capping sysfs interface configuration
6 bool "Generic powercap sysfs driver"
8 The power capping sysfs interface allows kernel subsystems to expose power
/linux-4.1.27/drivers/staging/iio/resolver/
DKconfig11 to digital converters, ad2s90, provides direct access via sysfs.
23 via sysfs.
34 to digital converters, ad2s1210, provides direct access via sysfs.
/linux-4.1.27/Documentation/acpi/
Dnamespace.txt192 sysfs as directories in the subtree under /sys/devices/LNXSYSTM:00. The
236 directory in sysfs will contain the 'path' attribute whose value is
241 column), so its sysfs directory will not contain the 'path'
247 its namespace path will be present in its sysfs directory. For
262 the corresponding ACPI namespace node. The object's sysfs directory
290 If an ACPI device object is linked to a "physical" device, its sysfs
291 directory contains the "physical_node" symbolic link to the sysfs
293 sysfs directory will then contain the "firmware_node" symbolic link to
294 the sysfs directory of the companion ACPI device object.
299 bus number of the parent PCI bridge is 0, the sysfs directory
[all …]
Dvideo_extension.txt13 1 Export a sysfs interface for user space to control backlight level
17 and set the required backlight operation structure for it for the sysfs
21 The backlight sysfs interface has a standard definition here:
22 Documentation/ABI/stable/sysfs-class-backlight.
95 level through the sysfs interface.
/linux-4.1.27/drivers/firmware/efi/
DKconfig5 tristate "EFI Variable Support via sysfs"
10 Interface) variable information via sysfs. You may read,
40 bool "Export efi runtime maps to sysfs"
48 See also Documentation/ABI/testing/sysfs-firmware-efi-runtime-map.
/linux-4.1.27/Documentation/blockdev/
Dzram.txt12 Statistics for individual zram devices are exported through sysfs nodes at
61 Set disk size by writing the value to sysfs node 'disksize'.
78 Set memory limit by writing the value to sysfs node 'mem_limit'.
104 read Documentation/ABI/testing/sysfs-block-zram.
133 per-stat sysfs attributes are considered to be deprecated.
136 -- deprecated RO sysfs nodes will eventually be removed (in linux 4.11)
139 Documentation/ABI/obsolete/sysfs-block-zram
141 Basically, every attribute that has its own read accessible sysfs node
180 Write any positive value to 'reset' sysfs node
/linux-4.1.27/Documentation/gpio/
D00-INDEX11 sysfs.txt
12 - Information about the GPIO sysfs interface
Dsysfs.txt5 configure a sysfs user interface to GPIOs. This is different from the
82 poll(2) returns, either lseek(2) to the beginning of the sysfs
131 /* create a sysfs link to an exported GPIO node */
135 /* change the polarity of a GPIO node in sysfs */
139 the sysfs interface by gpiod_export(). The driver can control whether the
148 symlinks from elsewhere in sysfs to the GPIO sysfs node. Drivers can
149 use this to provide the interface under their own device in sysfs with
/linux-4.1.27/Documentation/i2c/
Dslave-eeprom-backend8 located in sysfs:
12 As of 2015, Linux doesn't support poll on binary sysfs files, so there is no
Dold-module-parameters14 sysfs-based interface is described in the documentation file
27 New method (sysfs interface):
36 New method (sysfs interface):
/linux-4.1.27/drivers/soc/versatile/
DKconfig10 core modules providing some sysfs information about the ASIC
19 providing some sysfs information about the ASIC variant.
/linux-4.1.27/Documentation/rapidio/
Dsysfs.txt1 RapidIO sysfs Files
25 NOTE: An enumerating or discovering endpoint does not create a sysfs entry for
58 Currently Linux RapidIO subsystem does not create any endpoint specific sysfs
60 drivers will add their device-specific sysfs attributes but such attributes are
66 RapidIO switches have additional attributes in sysfs. RapidIO subsystem supports
67 common and device-specific sysfs attributes for switches. Because switches are
69 device-specific sysfs attributes by specifying a callback function that may be
115 "Master Port" or "mport") are presented in sysfs as the special class of
/linux-4.1.27/tools/power/cpupower/
D.gitignore14 lib/sysfs.lo
15 lib/sysfs.o
/linux-4.1.27/Documentation/input/
Dyealink.txt7 - LCD full support, yealink.ko / sysfs API
8 - LED full support, yealink.ko / sysfs API
9 - dialtone full support, yealink.ko / sysfs API
10 - ringtone full support, yealink.ko / sysfs API
40 find the sysfs files.
41 A: The sysfs files are located on the particular usb endpoint. On most
110 For userland the following interfaces are available using the sysfs interface:
Dntrig.txt10 and utility functions accessible with sysfs and module parameters.
20 devices. Adjusting parameters with sysfs will override the load time values,
43 Additional sysfs items
/linux-4.1.27/Documentation/block/
Dswitching-sched.txt11 assuming that you have sysfs mounted on /sys. If you don't have sysfs mounted,
14 # mount none /sys -t sysfs
D00-INDEX19 queue-sysfs.txt
20 - Queue's sysfs entries
Dcapability.txt3 This file documents the sysfs file block/<disk>/capability
/linux-4.1.27/Documentation/cpu-freq/
Dcpufreq-stats.txt21 These statistics are provided in /sysfs as a bunch of read_only interfaces. This
23 in /sysfs (<sysfs root>/devices/system/cpu/cpuX/cpufreq/stats/) for each CPU.
119 - trans_table goes against the traditional /sysfs rule of one value per
124 will be able to see the CPU frequency statistics in /sysfs.
Duser-guide.txt33 3.1 Preferred interface: sysfs
142 3.1 Preferred Interface: sysfs
145 The preferred interface is located in the sysfs filesystem. If you
/linux-4.1.27/drivers/staging/iio/frequency/
DKconfig11 AD9832 and AD9835, provides direct access via sysfs.
21 AD9833, AD9834, AD9837 and AD9838, provides direct access via sysfs.
/linux-4.1.27/Documentation/laptops/
Dthinkpad-acpi.txt80 is a new sysfs-based interface which is not complete yet.
86 all new functionality will be implemented on the sysfs interface.
88 The sysfs interface tries to blend in the generic Linux sysfs subsystems
94 Notes about the sysfs interface:
97 to the sysfs interfaces will be enforced, as will correctness in the
98 thinkpad-acpi's implementation of sysfs interfaces.
100 Also, any bugs in the thinkpad-acpi sysfs driver code or in the
101 thinkpad-acpi's implementation of the sysfs interfaces will be fixed for
106 Applications interfacing to the thinkpad-acpi sysfs interfaces must
107 follow all sysfs guidelines and correctly process all errors (the sysfs
[all …]
Dtoshiba_haps.txt26 however, this driver only provides a notification via a sysfs file to let
27 userspace tools or daemons act accordingly, as well as providing a sysfs
68 The sysfs files under /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS620A:00/ are:
/linux-4.1.27/Documentation/misc-devices/
Dad525x_dpot.txt5 The ad525x_dpot driver exports a simple sysfs interface. This allows you to
31 Locate the device in your sysfs tree. This is probably easiest by going into
38 address of 0x2f, we descend (unrelated sysfs entries have been trimmed).
/linux-4.1.27/tools/thermal/tmon/
DREADME15 introduced sysfs entry at /sys/class/thermal with a matrix of symbolic
28 sysfs.c : access to the generic thermal sysfs
/linux-4.1.27/Documentation/leds/
Dleds-class-flash.txt15 Following sysfs attributes are exposed for controlling flash LED devices:
16 (see Documentation/ABI/testing/sysfs-class-led-flash)
Dleds-lp5521.txt41 sysfs contains a selftest entry.
101 disabled and it is not visible in the sysfs.
Dleds-lp5562.txt25 so additional sysfs is required.
120 disabled and it is not visible in the sysfs.
/linux-4.1.27/Documentation/DocBook/
D.filesystems.xml.cmd2 …k.c fs/block_dev.c kernel/sysctl.c fs/proc/base.c fs/eventfd.c fs/sysfs/file.c fs/sysfs/symlink.c …
D.kernel-api.xml.cmd2 …sysfs.c drivers/pci/hotplug/pci_hotplug_core.c drivers/firmware/dmi_scan.c drivers/firmware/edd.c …
D.rapidio.xml.cmd2 …ers/rapidio/rio-access.c drivers/rapidio/rio-driver.c drivers/rapidio/rio-sysfs.c arch/powerpc/sys…
/linux-4.1.27/block/
DMakefile5 obj-$(CONFIG_BLOCK) := bio.o elevator.o blk-core.o blk-tag.o blk-sysfs.o \
9 blk-mq-sysfs.o blk-mq-cpu.o blk-mq-cpumap.o ioctl.o \
/linux-4.1.27/drivers/iio/frequency/
DKconfig18 Clock Generator. The driver provides direct access via sysfs.
36 Wideband Synthesizers. The driver provides direct access via sysfs.
/linux-4.1.27/Documentation/PCI/
Dpci-iov-howto.txt6 -- sysfs-based SRIOV enable-/disable-ment
36 In the second method, a write to the sysfs file sriov_numvfs will
60 (b) For the second method, from sysfs:
67 (b) For the second method, from sysfs:
/linux-4.1.27/Documentation/w1/slaves/
Dw1_ds28e0415 Support is provided through the sysfs files "eeprom" and "pio". CRC checking
32 The 2 PIOs of the DS28E04-100 are accessible via the "pio" sysfs file.
Dw1_ds240618 The driver provides two sysfs files. state is readable; it gives the
/linux-4.1.27/drivers/staging/iio/Documentation/
Doverview.txt21 hwmon with simple polled access to device channels via sysfs.
31 turned on or off (if possible) via sysfs interfaces.
57 sysfs-bus-iio - abi documentation file.
/linux-4.1.27/Documentation/cdrom/
Dpacket-writing.txt93 Using the pktcdvd sysfs interface
96 Since Linux 2.6.20, the pktcdvd module has a sysfs interface
110 For a description of the sysfs interface look into the file:
112 Documentation/ABI/testing/sysfs-class-pktcdvd
/linux-4.1.27/Documentation/filesystems/configfs/
Dconfigfs.txt15 sysfs's functionality. Where sysfs is a filesystem-based view of
19 With sysfs, an object is created in kernel (for example, when a device
20 is discovered) and it is registered with sysfs. Its attributes then
21 appear in sysfs, allowing userspace to read the attributes via
24 destroyed in kernel, the kernel controls the lifecycle of the sysfs
25 representation, and sysfs is merely a window on all this.
30 As with sysfs, readdir(3) queries the list of items and/or attributes.
31 symlink(2) can be used to group items together. Unlike sysfs, the
35 Both sysfs and configfs can and should exist together on the same
48 subdirectory (or more than one) under /config. Like sysfs, the
[all …]
/linux-4.1.27/drivers/sh/superhyway/
DMakefile6 obj-$(CONFIG_SYSFS) += superhyway-sysfs.o
/linux-4.1.27/drivers/dio/
DMakefile5 obj-y := dio.o dio-driver.o dio-sysfs.o
/linux-4.1.27/drivers/iio/trigger/
DMakefile7 obj-$(CONFIG_IIO_SYSFS_TRIGGER) += iio-trig-sysfs.o
DKconfig26 module will be called iio-trig-sysfs.
/linux-4.1.27/drivers/dca/
DMakefile2 dca-objs := dca-core.o dca-sysfs.o
/linux-4.1.27/drivers/video/fbdev/omap2/omapfb/
DMakefile2 omapfb-y := omapfb-main.o omapfb-sysfs.o omapfb-ioctl.o
/linux-4.1.27/drivers/thermal/
DKconfig2 # Generic thermal sysfs drivers configuration
6 tristate "Generic Thermal sysfs driver"
27 hwmon sysfs interface.
30 have hwmon sysfs interface too.
130 Enable this option to make a emul_temp sysfs node in thermal zone
131 directory to support temperature emulation. With emulation sysfs node,
137 flooding this sysfs node with low temperature values.
/linux-4.1.27/sound/aoa/soundbus/
DMakefile2 snd-aoa-soundbus-objs := core.o sysfs.o
/linux-4.1.27/tools/testing/selftests/rcutorture/doc/
Drcu-test-image.txt25 sysfs /sys sysfs defaults 0 0
Dinitrd.txt32 mount -t sysfs -o nodev,noexec,nosuid sysfs /sys
/linux-4.1.27/Documentation/w1/
Dw1.generic25 - sysfs entries for that w1 master are created
59 You can call above methods by reading appropriate sysfs files.
77 w1 master sysfs interface
105 w1 slave sysfs interface
/linux-4.1.27/drivers/pps/
DMakefile5 pps_core-y := pps.o kapi.o sysfs.o
/linux-4.1.27/Documentation/powerpc/
Dhvcs.txt53 for sysfs mounting are outside the scope of this document.
140 The tty layer creates sysfs entries which contain the major and minor
142 output of the sysfs directory shows where these numbers are presented:
145 |-- *other sysfs base dirs*
164 |-- *other sysfs base dirs*
248 vty-server adapter is associated with which /dev/hvcs* node a special sysfs
249 attribute has been added to each vty-server sysfs entry. This entry is
292 connected vty is a manual procedure using a write to a sysfs attribute
298 "vterm_state" sysfs attribute within each vty-server's sysfs entry is used.
324 Each vty-server has a sysfs entry in the /sys/devices/vio directory, which
[all …]
/linux-4.1.27/drivers/net/wimax/i2400m/
Ddebug-levels.h41 D_SUBMODULE_DECLARE(sysfs),
DMakefile10 sysfs.o \
Dsysfs.c31 #define D_SUBMODULE sysfs
DKconfig32 code using the sysfs debug-levels file.
/linux-4.1.27/arch/sh/drivers/dma/
DMakefile5 obj-$(CONFIG_SH_DMA_API) += dma-sh.o dma-api.o dma-sysfs.o
/linux-4.1.27/drivers/leds/trigger/
DKconfig7 be configured via sysfs. If unsure, say Y.
16 via sysfs. Some LED hardware can be programmed to start
27 controlled via sysfs. It's useful to notify the user on
/linux-4.1.27/drivers/infiniband/hw/mlx4/
DMakefile3 mlx4_ib-y := ah.o cq.o doorbell.o mad.o main.o mr.o qp.o srq.o mcg.o cm.o alias_GUID.o sysfs.o
/linux-4.1.27/drivers/rapidio/
DMakefile5 rapidio-y := rio.o rio-access.o rio-driver.o rio-sysfs.o
/linux-4.1.27/drivers/misc/cxl/
DMakefile1 cxl-y += main.o file.o irq.o fault.o native.o context.o sysfs.o debugfs.o pci.o trace.o
/linux-4.1.27/Documentation/video4linux/
DREADME.pvrusb243 Linux APIs (V4L, sysfs, maybe DVB in the future).
55 sysfs high level interface will work equally well for similar
93 the tuner's frequency through sysfs while simultaneously streaming
122 interfaces (e.g. V4L, sysfs, etc), and in fact even those high
127 controlling the hardware. High level interfaces (e.g. V4L, sysfs)
181 pvrusb2-sysfs.[ch] - This is the high level interface which ties the
182 pvrusb2 driver into sysfs. Through this interface you can do
Dfimc.txt98 4.5. sysfs
101 API the driver creates a sysfs entry associated with "s5p-fimc-md" platform
112 The sysfs entry allows to instruct the capture node driver not to configure
/linux-4.1.27/net/ieee802154/
DMakefile6 header_ops.o sysfs.o nl802154.o trace.o
/linux-4.1.27/drivers/base/power/
DMakefile1 obj-$(CONFIG_PM) += sysfs.o generic_ops.o common.o qos.o runtime.o
/linux-4.1.27/drivers/net/wireless/b43legacy/
DMakefile6 b43legacy-y += sysfs.o
/linux-4.1.27/drivers/md/bcache/
DMakefile5 io.o journal.o movinggc.o request.o stats.o super.o sysfs.o trace.o\
/linux-4.1.27/tools/testing/selftests/memory-hotplug/
Dmem-on-off-test.sh14 SYSFS=`mount -t sysfs | head -1 | awk '{ print $3 }'`
17 echo $msg sysfs is not mounted >&2
/linux-4.1.27/tools/testing/selftests/cpu-hotplug/
Dcpu-on-off-test.sh16 SYSFS=`mount -t sysfs | head -1 | awk '{ print $3 }'`
19 echo $msg sysfs is not mounted >&2
/linux-4.1.27/drivers/zorro/
DMakefile5 obj-$(CONFIG_ZORRO) += zorro.o zorro-driver.o zorro-sysfs.o
/linux-4.1.27/drivers/usb/core/
DMakefile6 usbcore-y += config.o file.o buffer.o sysfs.o endpoint.o
/linux-4.1.27/fs/nilfs2/
DMakefile5 ifile.o alloc.o gcinode.o ioctl.o sysfs.o
/linux-4.1.27/drivers/usb/wusbcore/
DMakefile11 dev-sysfs.o \
/linux-4.1.27/Documentation/ide/
D00-INDEX14 - using sysfs to remove and add IDE devices.
/linux-4.1.27/fs/efivarfs/
DKconfig7 variable support via sysfs, as it doesn't suffer from the
/linux-4.1.27/Documentation/ABI/stable/
Dsysfs-devices2 # is documented in Documentation/sysfs-rules.txt
Dsysfs-acpi-pmprofile5 Description: The ACPI pm_profile sysfs interface exports the platform
Dsysfs-bus-firewire49 Values: 1: The sysfs entry represents a local node (a controller card).
50 0: The sysfs entry represents a remote node.
/linux-4.1.27/drivers/net/wireless/ti/wlcore/
DMakefile2 boot.o init.o debugfs.o scan.o sysfs.o vendor_cmd.o
/linux-4.1.27/drivers/staging/iio/impedance-analyzer/
DKconfig13 Network Analyzer, AD5933/4, provides direct access via sysfs.
/linux-4.1.27/Documentation/x86/x86_64/
D00-INDEX12 - Configurable sysfs parameters for the x86-64 machine check code.
/linux-4.1.27/drivers/net/wireless/ath/ath5k/
DMakefile17 ath5k-y += sysfs.o
/linux-4.1.27/Documentation/scsi/
Dlibsas.txt35 register your SAS driver with the sysfs SAS tree it creates.
330 The sysfs tree has the following purposes:
342 That is, the sysfs domain tree doesn't show or keep state if
351 is reflected in the sysfs tree immediately, and the device(s)
364 In each expander directory in sysfs, there is a file called
365 "smp_portal". It is a binary sysfs attribute file, which
375 2. Open the expander's SMP portal sysfs file in RW mode.
390 argument, the sysfs file name of the SMP portal to the
/linux-4.1.27/Documentation/arm/Samsung-S3C24XX/
DCPUfreq.txt50 sysfs
53 The core code exports extra information via sysfs in the directory
/linux-4.1.27/arch/sh/drivers/
DKconfig17 framework that allows for sysfs driven switch status reporting.
/linux-4.1.27/drivers/infiniband/hw/mthca/
DKconfig17 the driver is loaded through sysfs).
/linux-4.1.27/drivers/cpuidle/
DMakefile5 obj-y += cpuidle.o driver.o governor.o sysfs.o governors/
/linux-4.1.27/drivers/staging/ozwpan/
DTODO4 sysfs entries
/linux-4.1.27/drivers/char/tpm/
DMakefile5 tpm-y := tpm-interface.o tpm-dev.o tpm-sysfs.o tpm-chip.o tpm2-cmd.o
/linux-4.1.27/drivers/staging/fwserial/
DTODO8 3. Expose means of controlling attach/detach of peers via sysfs. Include
/linux-4.1.27/net/batman-adv/
DMakefile37 batman-adv-y += sysfs.o
/linux-4.1.27/Documentation/networking/
Dcxacru.txt11 There is a script cxacru-cf.py to convert an existing file to the sysfs form.
16 several sysfs attribute files for retrieving device statistics:
DREADME.ipw2200243 An entry in the sysfs can support reading and/or writing. You can
244 typically query the contents of a sysfs entry through the use of cat,
257 Where $VALUE would be a number in the case of this sysfs entry. The
258 input to sysfs files does not have to be a number. For example, the
259 firmware loader used by hotplug utilizes sysfs entries for transferring
262 The Intel(R) PRO/Wireless 2915ABG Driver for Linux exposes sysfs entries
/linux-4.1.27/drivers/staging/iio/
DTODO10 1) Possibly add sysfs exports of constant useful to userspace.
31 2) Add sysfs elements necessary to allow device agnostic
/linux-4.1.27/net/core/
DMakefile15 obj-y += net-sysfs.o
/linux-4.1.27/drivers/net/wireless/b43/
DMakefile17 b43-y += sysfs.o
/linux-4.1.27/drivers/infiniband/core/
DMakefile11 ib_core-y := packer.o ud_header.o verbs.o sysfs.o \
/linux-4.1.27/Documentation/cpuidle/
Dcore.txt23 SEE ALSO: sysfs.txt in this directory.
Dgovernor.txt21 users can switch between drivers using /sysfs interface (when enabled).
/linux-4.1.27/net/wireless/
DMakefile12 cfg80211-y += core.o sysfs.o radiotap.o util.o reg.o scan.o nl80211.o
/linux-4.1.27/drivers/iommu/
DMakefile3 obj-$(CONFIG_IOMMU_API) += iommu-sysfs.o
/linux-4.1.27/net/dsa/
DKconfig26 via the hwmon sysfs interface and exposes the onboard sensors.
/linux-4.1.27/Documentation/spi/
Dspi-lm70llp54 the bound "hwmon/lm70" protocol driver through its sysfs hook, using a
57 and exports it through sysfs.
/linux-4.1.27/drivers/staging/fbtft/
DMakefile3 fbtft-y += fbtft-core.o fbtft-sysfs.o fbtft-bus.o fbtft-io.o
/linux-4.1.27/arch/arm/mach-u300/
DKconfig29 Debug support for U300 in sysfs, procfs etc.
/linux-4.1.27/arch/tile/kernel/
DMakefile9 sysfs.o time.o traps.o unaligned.o vdso.o \
/linux-4.1.27/Documentation/pcmcia/
Ddriver.txt5 sysfs
Ddevicetable.txt23 "modalias" in the sysfs directory of the PCMCIA device. It generates a string
/linux-4.1.27/fs/btrfs/
DMakefile7 extent_map.o sysfs.o struct-funcs.o xattr.o ordered-data.o \
/linux-4.1.27/drivers/pci/
DMakefile6 pci-driver.o search.o pci-sysfs.o rom.o setup-res.o \
/linux-4.1.27/net/wimax/
DKconfig35 the sysfs debug-levels file.
/linux-4.1.27/drivers/staging/iio/adc/
DKconfig92 via sysfs.
114 ST SPEAr SoC. Provides direct access via sysfs.
/linux-4.1.27/Documentation/power/
Dpm_qos_interface.txt147 create a sysfs attribute pm_qos_resume_latency_us under the device's power
152 PM QoS list of resume latency constraints and remove sysfs attribute
156 Add a request to the device's PM QoS list of flags and create sysfs attributes
162 of flags and remove sysfs attributes pm_qos_no_power_off and pm_qos_remote_wakeup
214 If .set_latency_tolerance() is present for the device, sysfs attribute
Dinterface.txt4 The power management subsystem provides a unified sysfs interface to
6 running. The interface exists in /sys/power/ directory (assuming sysfs
/linux-4.1.27/drivers/net/ethernet/mellanox/mlx4/
DKconfig46 the driver is loaded through sysfs).
/linux-4.1.27/drivers/power/
DKconfig6 via sysfs and uevent (if available) and/or APM kernel interface
302 Say Y to enable support for the MAX8903 DC-DC charger and sysfs.
352 Say Y to enable support for the battery charger control sysfs and
365 Say Y to enable support for the battery charger control sysfs and
372 Say Y to enable support for the battery charger control sysfs and
/linux-4.1.27/drivers/staging/media/bcm2048/
DTODO10 The sysfs stuff should be replaced by controls as well. A lot of the RDS
/linux-4.1.27/drivers/pwm/
DMakefile2 obj-$(CONFIG_PWM_SYSFS) += sysfs.o
/linux-4.1.27/drivers/staging/iio/Documentation/dac/
Dmax51728 Via the iio sysfs interface, there are three attributes available: out1_raw,
/linux-4.1.27/tools/lib/api/fs/
Dfs.c168 FS__MOUNTPOINT(sysfs, FS__SYSFS);

123