Lines Matching refs:debugfs

13 debugfs has no rules at all.  Developers can put any information they want
14 there.  The debugfs filesystem is also intended to not serve as a stable
17 even debugfs interfaces are best designed with the idea that they will need
22     mount -t debugfs none /sys/kernel/debug
25 The debugfs root directory is accessible only to the root user by
29 Note that the debugfs API is exported GPL-only to modules.
31 Code using debugfs should include <linux/debugfs.h>.  Then, the first order
33 debugfs files::
39 created in the debugfs root.  On success, the return value is a struct
43 indication that the kernel has been built without debugfs support and none
46 The most general way to create a file within a debugfs directory is with::
59 ERR_PTR(-ERROR) on error, or ERR_PTR(-ENODEV) if debugfs support is
74 actually necessary; the debugfs code provides a number of helper functions
109 As might be expected, this function will create a debugfs file to represent
121 Boolean values can be placed in debugfs with::
130 Also, atomic_t values can be placed in debugfs with::
159 debugfs offers two functions: one to make a registers-only file, and
186 If you want to dump a u32 array in debugfs, you can create a file with::
208 The "dev" argument is the device related to this debugfs file, and
221 A call to debugfs_change_name() will give a new name to an existing debugfs
226 There is one important thing that all debugfs users must take into account:
227 there is no automatic cleanup of any directories created in debugfs.  If a
228 module is unloaded without explicitly removing debugfs entries, the result
230 So all debugfs users - at least those which can be built as modules - must