| /Documentation/ABI/testing/ |
| D | sysfs-class-regulator | 6 Some regulator directories will contain a field called
20 supplying power to the system (unless some non-Linux
32 Some regulator directories will contain a field called
96 Some regulator directories will contain a field called
111 Some regulator directories will contain a field called
126 Some regulator directories will contain a field called
151 Some regulator directories will contain a field called
166 Some regulator directories will contain a field called
181 Some regulator directories will contain a field called
196 Some regulator directories will contain a field called
[all …]
|
| D | sysfs-devices-real_power_state | 17 In some situations the value of this attribute may be different
19 the same device object. If that happens, some shared power
20 resources used by the device node are only ON because of some
|
| D | sysfs-driver-samsung-laptop | 5 Description: Some Samsung laptops have different "performance levels"
8 of sense, but some users like to modify them to keep
43 Description: Some Samsung laptops handle lid closing quicker and
|
| /Documentation/devicetree/bindings/power/supply/ |
| D | power_supply.txt | 10 compatible = "some,usb-charger";
15 compatible = "some,ac-charger";
20 compatible = "some,battery";
|
| /Documentation/driver-api/firmware/ |
| D | built-in-fw.rst | 25 * Some firmware may be optional
28 * Some firmware files may be really large in size. The remote-proc subsystem
30 * The firmware may need to be scraped out from some device specific location
31 dynamically, an example is calibration data for for some WiFi chipsets. This
|
| /Documentation/scsi/ |
| D | ChangeLog.ncr53c8xx | 55 that supply SCSI_DATA_NONE direction (this avoids some BUG()
74 * And some other ...
91 * And some other ...
131 some minor changes. The driver can now attach any number of
150 - Add support of some 'resource handling' for linux-2.3.13.
153 - Remove some deprecated code.
162 - Some additions to the README.ncr53c8xx file.
187 - Fix some oooold bug that hangs the bus if a device rejects a
188 negotiation. Btw, the corresponding stuff also needed some cleanup
190 - Still some typo that made compilation fail for 64 bit (trivial fix).
[all …]
|
| D | ChangeLog.sym53c8xx | 133 that supply SCSI_DATA_NONE direction (this avoids some BUG()
160 chips will check parity in some special circumstances.
203 - Some fix for Sparc from DSM that went directly to kernel tree.
213 - Some fixes in the MODIFY_DP/IGN_RESIDUE code and residual
241 - Backport some minor improvements of SCRIPTS from the sym_hipd
255 - Work-around PCI chips being reported twice on some platforms.
256 - Add some redundant PCI reads in order to deal with common
258 - Add some other conditionnal code for people who have to deal
270 - Fix some bug in the fully untested MDP handling:) and share
271 some code between MDP handling and residual calculation.
[all …]
|
| D | NinjaSCSI.txt | 20 card, and write ["WBT", "NinjaSCSI-3", "R1.0"] or some other string to
38 Because the NinjaSCSI driver requires some SCSI header files in Linux
40 some versioning problems.
47 [3] If you use this driver with Kernel 2.2, unpack pcmcia-cs in some directory
108 If you eject card when doing some operation for your SCSI device or suspend
109 your computer, you encount some *BAD* error like disk crash.
118 Please send me some reports(bug reports etc..) of this software.
|
| D | scsi-changer.txt | 19 First some words about how changers work: A changer has 2 (possibly
67 Grundig. I got some reports telling it works ok with tape autoloaders
68 (Exabyte, HP and DEC). Some People use this driver with amanda. It
87 If the module finds the changer, it prints some messages about the
89 /proc/devices. If not.... some changers use ID ? / LUN 0 for the
110 logfiles). If you email me some question because of a problem with the
138 should provide this information. But some devices don't ...
144 are some vendor-specific element types. Grundig for example
145 does this. Some jukeboxes have a printer to label fresh burned
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | msi.txt | 12 MSIs are distinguished by some combination of:
35 address by some master. An MSI controller may feature a number of doorbells.
87 compatible = "vendor-a,some-controller";
96 /* Each device has some unique ID */
104 /* Each device has some unique ID */
110 compatible = "vendor-c,some-device";
118 compatible = "vendor-c,some-device";
128 compatible = "vendor-c,some-device";
|
| /Documentation/admin-guide/laptops/ |
| D | sonypi.rst | 13 can be found in many Sony Vaio laptops. Some newer Sony laptops (seems to be
17 It will give access (through a user space utility) to some events those laptops
35 This driver supports also some ioctl commands for setting the LCD screen
36 brightness and querying the batteries charge information (some more
64 fnkeyinit: on some Vaios (C1VE, C1VR etc), the Fn key events don't
67 some Vaio models don't deal well with this option.
78 compat: uses some compatibility code for enabling the sonypi
85 some Vaio models where the hardware reuses values
139 - some users reported that the laptop speed is lower (dhrystone
148 events on some models.
[all …]
|
| /Documentation/devicetree/bindings/mtd/partitions/ |
| D | brcm,bcm947xx-cfe-partitions.txt | 6 without any on-flash partition table. On some devices their sizes and/or
15 containing some details, including a length.
20 3) Device manufacturer's data with some default values (e.g. SSIDs)
24 As mentioned earlier, role of some partitions may depend on extra configuration.
|
| /Documentation/vm/ |
| D | numa.rst | 20 of the system--although some components necessary for a stand-alone SMP system
22 connected together with some sort of system interconnect--e.g., a crossbar or
50 of the hardware platform, abstracting away some of the details for some
57 For some architectures, such as x86, Linux will "hide" any node representing a
63 In addition, for some architectures, again x86 is an example, Linux supports
81 Because some nodes contain multiple zones containing different types of
84 type on the same node. This is an important consideration because some zones,
99 as long as the task on whose behalf the kernel allocated some memory does not
129 Some kernel allocations do not want or cannot tolerate this allocation fallback
145 or some subsystems would fail to initialize if they attempted to allocated
|
| D | hwpoison.rst | 10 Upcoming Intel CPUs have support for recovering from some memory errors
25 that if the error cannot be handled for some reason it's safe to
32 possibly violating some of their assumptions. This is why this code
37 Some of the operations here are somewhat inefficient and have non
54 won't do that, but some very specialized ones might.
76 Note some pages are always handled as late kill.
120 some early filtering to avoid corrupted unintended pages in test suites.
164 Some portable hwpoison test programs in mce-test, see below.
|
| /Documentation/i2c/ |
| D | fault-codes.rst | 14 some cases, such as re-initializing (and maybe resetting). After such
29 some positive number indicating a non-fault return. The specific
44 transmit mode: some other master was transmitting different
48 atomic context, when some task is already using that I2C bus
49 to execute some other operation.
62 than allowed. This usually indicates some device (maybe the
63 SMBus adapter) needs some fault recovery (such as resetting),
130 timeouts, but it's normal for I2C adapters to impose some
|
| D | ten-bit-addresses.rst | 18 you can expect some problems along the way:
20 * Not all bus drivers support 10-bit addresses. Some don't because the
22 support for example), some don't because nobody bothered adding the
25 * Some optional features do not support 10-bit addresses. This is the
|
| /Documentation/devicetree/bindings/pinctrl/ |
| D | sprd,pinctrl.txt | 5 The first block comprises some global control registers, and each
7 to configure for some global common configuration, such as domain
27 The second block comprises some common registers which have unified
42 In some situation we need set the pin sleep mode and pin sleep related
50 Moreover we can not use the "sleep" state, since some systems (like:
56 The last block comprises some misc registers which also have unified
|
| /Documentation/admin-guide/ |
| D | svga.rst | 26 option of LILO (or some other boot loader you use) or by the "vidmode" utility
82 The mode list usually contains a few basic modes and some VESA modes. In
83 case your chipset has been detected, some chipset-specific modes are shown as
84 well (some of these might be missing or unusable on your machine as different
96 what happens then. The screen will be probably flashing wildly for some time and
98 all consistent video modes supported by your BIOS will appear (plus maybe some
155 eliminate some annoying bugs of certain VGA BIOSes (usually those used for
176 the machine hangs instead of displaying the menu), try to switch off some of
183 If you start Linux from M$-DOS, you might also use some DOS tools for
188 If you set some extended mode and there's one or more extra lines on the
[all …]
|
| /Documentation/driver-api/gpio/ |
| D | intro.rst | 37 System-on-Chip (SOC) processors heavily rely on GPIOs. In some cases, every
48 - Output values are writable (high=1, low=0). Some chips also have
53 - Input values are likewise readable (1, 0). Some chips support readback
66 through a serial bus normally can't. Some systems support both types.
104 Some GPIO controllers directly support open drain and open source outputs; many
113 (or some other device) controls the signal.
120 value (after the appropriate rise time passes), you know some other component is
|
| /Documentation/kbuild/ |
| D | Kconfig.recursion-issue-02 | 8 # The recursive limitations with Kconfig has some non intuitive implications on
12 # annotate those requirements, ie, some drivers use "depends on" while others
25 # have. Let's assume we have some CORE functionality, then the kernel has a
28 # CORE_BELL_A has some advanced feature CORE_BELL_A_ADVANCED which selects
|
| /Documentation/devicetree/bindings/mfd/ |
| D | cros-ec.txt | 24 - google,cros-ec-spi-pre-delay: Some implementations of the EC need a little
28 - google,cros-ec-spi-msg-delay: Some implementations of the EC require some
41 - google,has-vbc-nvram: Some implementations of the EC include a small
|
| /Documentation/accounting/ |
| D | psi.rst | 40 some avg10=0.00 avg60=0.00 avg300=0.00 total=0
44 some avg10=0.00 avg60=0.00 avg300=0.00 total=0
47 The "some" line indicates the share of time in which at least some
55 situation from a state where some tasks are stalled but the CPU is
82 <some|full> <stall amount in us> <time window in us>
84 For example writing "some 150000 1000000" into /proc/pressure/memory
132 const char trig[] = "some 150000 1000000";
|
| /Documentation/driver-api/ |
| D | device-io.rst | 31 memory, but as accesses to a device. Some architectures define devices
32 to be at a fixed address, but most have some method of discovering
62 Some devices (such as framebuffers) would like to use larger transfers than
79 of property cannot be hidden from driver writers in the API. In some
107 outstanding DMA writes from that bus, since for some devices the result of
112 these cases, although only some platforms will honor the relaxed
142 Some variants are provided for these functions. Some devices require
|
| /Documentation/PCI/ |
| D | msi-howto.rst | 17 to change your driver to use MSI or MSI-X and some basic diagnostics to
81 option enabled. This option is only available on some architectures,
82 and it may depend on some other options also being set. For example,
127 some platforms, MSI interrupts must all be targeted at the same set of CPUs
160 Some devices might not support using legacy line interrupts, in which case
205 Using 'lspci -v' (as root) may show some devices with "MSI", "Message
224 Some host chipsets simply don't support MSIs properly. If we're
227 Some boards don't include this information in the table and so we have
239 Some PCI bridges are not able to route MSIs between busses properly.
242 Some bridges allow you to enable MSIs by changing some bits in their
[all …]
|
| /Documentation/hwmon/ |
| D | userspace-tools.rst | 8 voltages, fans speed). They are often connected through an I2C bus, but some
32 3) load them and run "sensors" command, you should see some results.
39 If you want some graphical indicators of system health look for applications
|