1DEBUGFS_CREATE_REGSE(9) The debugfs filesystem DEBUGFS_CREATE_REGSE(9)
2
3
4
6 debugfs_create_regset32 - create a debugfs file that returns register
7 values
8
10 struct dentry * debugfs_create_regset32(const char * name,
11 umode_t mode,
12 struct dentry * parent,
13 struct debugfs_regset32 * regset);
14
16 name
17 a pointer to a string containing the name of the file to create.
18
19 mode
20 the permission that the file should have
21
22 parent
23 a pointer to the parent dentry for this file. This should be a
24 directory dentry if set. If this parameter is NULL, then the file
25 will be created in the root of the debugfs filesystem.
26
27 regset
28 a pointer to a struct debugfs_regset32, which contains a pointer to
29 an array of register definitions, the array size and the base
30 address where the register bank is to be found.
31
33 This function creates a file in debugfs with the given name that
34 reports the names and values of a set of 32-bit registers. If the mode
35 variable is so set it can be read from. Writing is not supported.
36
37 This function will return a pointer to a dentry if it succeeds. This
38 pointer must be passed to the debugfs_remove function when the file is
39 to be removed (no automatic cleanup happens if your module is unloaded,
40 you are responsible here.) If an error occurs, NULL will be returned.
41
42 If debugfs is not enabled in the kernel, the value -ENODEV will be
43 returned. It is not wise to check for this value, but rather, check for
44 NULL or !NULL instead as to eliminate the need for #ifdef in the
45 calling code.
46
48Kernel Hackers Manual 3.10 June 2019 DEBUGFS_CREATE_REGSE(9)