| /Documentation/ABI/testing/ |
| D | sysfs-class-watchdog | 5 It is a read only file. It contains status of the watchdog
6 device at boot. It is equivalent to WDIOC_GETBOOTSTATUS of
13 It is a read only file. It contains identity string of
20 It is a read only file. While reading, it gives '1' if that
21 device supports nowayout feature else, it gives '0'.
27 It is a read only file. It gives active/inactive status of
34 It is a read only file. It contains watchdog device's
35 internal status bits. It is equivalent to WDIOC_GETSTATUS
42 It is a read only file. It contains value of time left for
43 reset generation. It is equivalent to WDIOC_GETTIMELEFT of
[all …]
|
| D | sysfs-platform-chipidea-usb2 | 5 It returns string "gadget" or "host" when read it, it indicates
8 It will do role switch when write "gadget" or "host" to it.
|
| D | sysfs-c2port | 3 Contact: Rodolfo Giometti <giometti@linux.it>
11 Contact: Rodolfo Giometti <giometti@linux.it>
19 Contact: Rodolfo Giometti <giometti@linux.it>
27 Contact: Rodolfo Giometti <giometti@linux.it>
34 Contact: Rodolfo Giometti <giometti@linux.it>
42 Contact: Rodolfo Giometti <giometti@linux.it>
49 Contact: Rodolfo Giometti <giometti@linux.it>
56 Contact: Rodolfo Giometti <giometti@linux.it>
63 Contact: Rodolfo Giometti <giometti@linux.it>
71 Contact: Rodolfo Giometti <giometti@linux.it>
[all …]
|
| /Documentation/filesystems/ |
| D | hpfs.txt | 9 is taken from it
16 Set owner/group/mode for files that do not have it specified in extended
25 - there is a list of text extensions (I thing it's better to not convert
27 change it in the source. Original readonly HPFS contained some strange
28 heuristic algorithm that I removed. I thing it's danger to let the
34 danger. I tried to write it so that it won't crash if check=normal on
36 used for debugging (for example it checks if file is allocated in
37 bitmaps when accessing it).
41 When to mark filesystem dirty so that OS/2 checks it.
63 access it under names 'a.', 'a..', 'a . . . ' etc.
[all …]
|
| D | path-lookup.rst | 12 It has subsequently been updated to reflect changes in the kernel
21 exploration is needed to discover, is that it is complex. There are
24 acquainted with such complexity and has tools to help manage it. One
50 It is tempting to describe the second kind as starting with a
52 slashes and components, it can be empty, in other words. This is
54 in Linux permit it when the ``AT_EMPTY_PATH`` flag is given. For
56 can execute it by calling `execveat() <execveat_>`_ passing
61 it must identify a directory that already exists, otherwise an error
65 calls interpret it quite differently (e.g. some create it, some do
66 not), but it might not even exist: neither the empty pathname nor the
[all …]
|
| D | porting.rst | 58 informative error value to report). Call it foo_fill_super(). Now declare::
89 it by internal locking (most of filesystems couldn't care less) - you
98 and ->readdir() are called without BKL now. Grab it on entry, drop upon return
109 individual fs sb_op functions. If you don't need it, remove it.
116 free to drop it...
130 an existing filesystem, set it according to ->fs_flags::
136 FS_LITTER is gone - just remove it from fs_flags.
143 went in - and hadn't been documented ;-/). Just remove it from fs_flags
163 Briefly it allows for the definition of decode_fh and encode_fh operations
168 It is planned that this will be required for exporting once the code
[all …]
|
| D | xfs-self-describing-metadata.txt | 10 adequate for supporting PB scale filesystems with billions of inodes, however it
20 For example, it is entirely possible to manually use xfs_db and a bit of
22 determine the root cause of a corruption problem, but it is still mainly a
24 weren't the ultimate cause of a corruption event. It may take a few hours to a
40 magic number in the metadata block, we have no other way of identifying what it
41 is supposed to be. We can't even identify if it is the right place. Put simply,
42 you can't look at a single metadata block in isolation and say "yes, it is
50 went wrong, but it is impossible to tell what order the blocks were linked into
70 numbers in the metadata objects. That is, if it has the current magic number,
71 the metadata isn't self identifying. If it contains a new magic number, it is
[all …]
|
| D | autofs.txt | 5 autofs - how it works
61 always a regular directory, otherwise it is a mount trap when it is
71 option and particularly whether it is less than five or not.
93 the inode has S_AUTOMOUNT set, or can be set directly) then it is
97 should be mounted on the directory and to return it. The VFS is
102 automount daemon asking it to find and mount the filesystem. The
104 everything is ready. It will then return "`NULL`" indicating that the
110 reflected on the client. However it is not sufficient for autofs. As
124 to `false`. It may return one of three things:
139 autofs returns this if it detects that the process performing the
[all …]
|
| /Documentation/process/ |
| D | management-style.rst | 7 on who you ask) management style for the linux kernel. It's meant to
14 to do with reality. It started as a lark, but that doesn't mean that it
17 Btw, when talking about "kernel manager", it's all about the technical
24 People", and NOT read it. Burn it, it's a great symbolic gesture.
27 making it painfully obvious to the questioner that we don't have a clue
39 manager must be to make it. That's very deep and obvious, but it's not
60 It helps to realize that the key difference between a big decision and a
75 It turns out that since nobody would be stupid enough to ever really let
76 a kernel manager have huge fiscal responsibility **anyway**, it's usually
83 you made a year ago wasn't a big decision after all, since it could be
[all …]
|
| /Documentation/admin-guide/pm/ |
| D | cpuidle.rst | 20 a program is suspended and instructions belonging to it are not fetched from
25 it is an opportunity to save energy.
39 (program) from memory and executing them, but it need not work this way
43 program) at a time, it is a CPU. In that case, if the hardware is asked to
46 Second, if the processor is multi-core, each core in it is able to follow at
52 enter an idle state, that applies to the core that asked for it in the first
53 place, but it also may apply to a larger unit (say a "package" or a "cluster")
54 that the core belongs to (in fact, it may apply to an entire hierarchy of larger
57 remaining core asks the processor to enter an idle state, that may trigger it
70 by one of them, the hardware thread (or CPU) that asked for it is stopped, but
[all …]
|
| D | cpufreq.rst | 29 In some situations it is desirable or even necessary to run the program as fast
32 available). In some other cases, however, it may not be necessary to execute
34 relatively long time without utilizing it entirely may be regarded as wasteful.
35 It also may not be physically possible to maintain maximum CPU capacity for too
45 to as CPU performance scaling or CPU frequency scaling (because it involves
57 interfaces for all platforms that support CPU performance scaling. It defines
72 platform-independent form in the majority of cases, so it should be possible
80 interface it comes from and may not be easily represented in an abstract,
91 control the P-state of multiple CPUs at the same time and writing to it affects
112 It is only possible to register one scaling driver at a time, so the scaling
[all …]
|
| /Documentation/media/uapi/dvb/ |
| D | frontend-stat-properties.rst | 8 .. TODO: replace it to GFDL-1.1-or-later WITH no-invariant-sections
23 It should be noted, however, that new OFDM delivery systems like ISDB
43 - ``scale`` - Scale for the value. It can be:
46 frontend, but it was not possible to collect it (could be a
70 - ``FE_SCALE_NOT_AVAILABLE`` - it failed to measure it, or the
89 - ``FE_SCALE_NOT_AVAILABLE`` - it failed to measure it, or the
110 In order to get the BER (Bit Error Rate) measurement, it should be
115 bit count measurements. The frontend may reset it when a
120 - ``FE_SCALE_NOT_AVAILABLE`` - it failed to measure it, or the
137 It should be noted that this measurement can be smaller than the total
[all …]
|
| /Documentation/scsi/ |
| D | qlogicfas.txt | 16 Nor does it support the PCI-Basic, which is supported by the
28 the Linux PCMCIA driver, you will have to adjust it or otherwise stop
29 it from configuring the card.
31 I am working with the PCMCIA group to make it more flexible, but that
37 configuration. As shipped, it provides a balance between speed and
42 It may be a good idea to enable RESET_AT_START, especially if the
45 command or something. It comes up faster if this is set to zero, and
46 if you have reliable hardware and connections it may be more useful to
51 Make sure it works properly under DOS. You should also do an initial FDISK
61 large executable or archive). It should be at least 5 megabytes, but
[all …]
|
| /Documentation/security/keys/ |
| D | request-key.rst | 46 does not need to link the key to a keyring to prevent it from being immediately
48 it's up to the caller to destroy the key.
50 The request_key_tag() call is like the in-kernel request_key(), except that it
59 The request_key_rcu() call is like the request_key_tag() call, except that it
82 a suitable key there. If there is, it returns the key. If there isn't,
86 3) request_key() sees that A doesn't have the desired key yet, so it creates
104 Kerberos TGT key). It just requests the appropriate key, and the keyring
107 This will permit it to then search the keyrings of process A with the
108 UID, GID, groups and security info of process A as if it was process A,
111 8) The program then does what it must to get the data with which to
[all …]
|
| /Documentation/driver-api/usb/ |
| D | persist.rst | 20 required to behave as though the device has been unplugged. It's a
23 device is still attached or perhaps it was removed and a different
29 though they had disconnected. This is always safe and it is the
35 system woke up, who cares? It'll still work the same when you type on
36 it.
52 it's as though you had unplugged all the USB devices. Yes, it's
64 the system can't be suspended at all. (All right, it _can_ be
65 suspended -- but it will crash as soon as it wakes up, which isn't
72 The kernel includes a feature called USB-persist. It tries to work
76 It works like this. If the kernel sees that a USB host controller is
[all …]
|
| /Documentation/power/ |
| D | s2ram.rst | 13 simple module unload can fix it.
21 always it's a driver that is buggy. Thank God for the suspend/resume
23 way to debug these things, and it's actually pretty powerful (but
41 - if it doesn't come back up (which is usually the problem), reboot by
52 fix it, disable it, or trace into its resume function.
62 used to run with "radeonfb" (it's an ATI Radeon mobility). It turns out
63 that "radeonfb" simply cannot resume that device - it tries to set the
64 PLL's, and it just _hangs_. Using the regular VGA console and letting X
65 resume it instead works fine.
74 pm_trace is not compatible with asynchronous suspend, so it turns
[all …]
|
| D | swsusp.rst | 21 it may cause some problems, too. If you change kernel command line
22 between suspend and resume, it may do something wrong. If you change
23 your hardware while system is suspended... well, it was not good idea;
24 but it will probably only crash.
26 ( ) suspend/resume support is needed to make it safe.
36 line or specify it using /sys/power/resume.
40 resume_offset=<number> on the kernel command line or specify it
52 to RAM (provided your platform supports it), you can try::
66 before suspend (it is limited to around 2/5 of available RAM by default).
69 if found, it then checks the contents for the hibernation image signature.
[all …]
|
| D | userland-swsusp.rst | 10 done it already.
25 reading, it is considered to be in the suspend mode. Otherwise it is
27 reading and writing. It is also impossible to have the device open more than
49 from it (0) (after resume the system finds itself finishing the
52 it out of the kernel
56 uploaded snapshot image; before calling it you should transfer
67 this number, but if it turns out to be impossible, the kernel will
93 partitions the offset is always 0, but it is different from zero for
108 be preceded by the SNAPSHOT_FREEZE call and it is also necessary
112 to disk, and then the system is suspended to RAM (this makes it possible
[all …]
|
| D | pci.rst | 34 Usually, a device is put into a low-power state when it is underutilized or
35 completely inactive. However, when it is necessary to use the device once
36 again, it has to be put back into the "fully functional" state (full-power
53 to put the device that sent it into the full-power state. However, the PCI Bus
56 It is assumed that the platform firmware will perform this task and therefore,
57 even though a PCI device is set up to generate PMEs, it also may be necessary to
63 preparing the device to generate wakeup signals. In that case, however, it
75 introduced between the PCI 2.1 and PCI 2.2 Specifications. It defined a
80 but it is mandatory for PCI Express devices. If a device supports the PCI PM
81 Spec, it has an 8 byte power management capability field in its PCI
[all …]
|
| /Documentation/filesystems/configfs/ |
| D | configfs.txt | 20 is discovered) and it is registered with sysfs. Its attributes then
22 readdir(3)/read(2). It may allow some attributes to be modified via
28 mkdir(2). It is destroyed via rmdir(2). The attributes appear at
41 it by doing
47 subsystems. Once a client subsystem is loaded, it will appear as a
70 write_bin_attribute method will be invoked on the final close, therefore it is
76 When an item needs to be destroyed, remove it with rmdir(2). An
77 item cannot be destroyed if any other item has a link to it (via
83 access remote block devices. Call it FakeNBD. FakeNBD uses configfs
86 the driver about it. Here's where configfs comes in.
[all …]
|
| /Documentation/fb/ |
| D | matroxfb.rst | 13 * It provides a nice large console (128 cols + 48 lines with 1024x768)
24 How to use it?
93 XF{68,86}_FBDev should work just fine, but it is non-accelerated. On non-intel
108 Driver contains SVGALib compatibility code. It is turned on by choosing textual
109 mode for console. You can do it at boot time by using videomode
112 Switching to another console and back fixes it. I hope that it is SVGALib's
127 it always probe for memory. Default is to use whole detected
132 configuration, you can override it by this (you cannot override
133 `off`). It is default.
134 noaccel do not use acceleration engine. It does not work on Alphas.
[all …]
|
| /Documentation/driver-api/driver-model/ |
| D | binding.rst | 6 driver that can control it. Bus drivers have typically handled this
16 type in the system. When device_register is called for a device, it is
19 for a driver, it is inserted at the end of this list. These are the
27 to find one that supports it. In order to determine that, the device
31 algorithm, it is up to the bus driver to provide a callback to compare
39 chance to verify that it really does support the hardware, and that
40 it's in a working state.
46 the class to which it belongs. Device drivers belong to one and only one
49 and actually register it with the class, which happens with the
91 When a device is removed, the reference count for it will eventually
[all …]
|
| /Documentation/hwmon/ |
| D | submitting-patches.rst | 12 * It should be unnecessary to mention, but please read and follow:
30 and a consistent coding style makes it easier for others to understand
36 architecture. If run-time testing was not achieved, it should be written
40 CONFIG_SMP, make sure it compiles for all configuration variants.
52 your patch into a cleanup part and the actual addition. This makes it easier
62 formatting is clean. If unsure about formatting in your new driver, run it
64 cleanup, but it is a good start.
80 * Avoid macros to generate groups of sensor attributes. It not only confuses
81 checkpatch, but also makes it more difficult to review the code.
84 may save a line or so in the source, it obfuscates the code and makes code
[all …]
|
| /Documentation/RCU/ |
| D | UP.rst | 8 is that since there is only one CPU, it should not be necessary to
11 work a surprising amount of the time, it is a very bad idea in general.
21 is referencing element B when it is interrupted by softirq processing,
37 by having call_rcu() directly invoke its arguments only if it was called
41 elements A, B, and C in process contexts, but that it invokes a function
42 on each element as it is scanned. Suppose further that this function
43 deletes element B from the list, then passes it to call_rcu() for deferred
44 freeing. This may be a bit unconventional, but it is perfectly legal
47 its arguments would cause it to fail to make the fundamental guarantee
52 Why is it *not* legal to invoke synchronize_rcu() in this case?
[all …]
|
| /Documentation/maintainer/ |
| D | pull-requests.rst | 30 have just created. It is recommended that you choose a meaningful tag name,
43 last commit in the ``char-misc-next`` branch, and sign it with your gpg key
51 so outline what is contained here, why it should be merged, and what, if
54 merge the pull request. So write it up well, as it will be in the kernel
60 to understand what I'm pulling, and why I should pull it. I also
61 want to use that message as the message for the merge, so it should
67 that you don't maintain, explain _why_. I will see it in the
68 diffstat anyway, and if you didn't mention it, I'll just be extra
71 what they do and why they do it, but explain the _timing_. What
77 make it into the pull request email), or you can make the signed
[all …]
|