| /Linux-v5.4/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 …]
|
| /Linux-v5.4/include/linux/mfd/ |
| D | tmio.h | 40 * Some controllers can support a 2-byte block size when the bus width
45 * Some controllers can support SDIO IRQ signalling.
49 /* Some features are only available or tested on R-Car Gen2 or later */
53 * Some controllers require waiting for the SD bus to become
54 * idle before writing to some registers.
61 * Some controllers have CMD12 automatically
66 /* Controller has some SDIO status bits which must be 1 */
70 * Some controllers have a 32-bit wide data port register
75 * Some controllers allows to set SDx actual clock
79 /* Some controllers have a CBSY bit */
[all …]
|
| /Linux-v5.4/include/linux/clk/ |
| D | at91_pmc.h | 37 #define AT91_CKGR_UCKR 0x1C /* UTMI Clock Register [some SAM9] */
47 #define AT91_PMC_MOSCRCEN (1 << 3) /* Main On-Chip RC Oscillator Enable [some SAM9] */
51 #define AT91_PMC_MOSCSEL (1 << 24) /* Main Oscillator Selection [some SAM9] */
52 #define AT91_PMC_CFDEN (1 << 25) /* Clock Failure Detector Enable [some SAM9] */
81 #define AT91_PMC_CSS_UPLL (3 << 0) /* [some SAM9 only] */
108 #define AT91SAM9_PMC_MDIV_6 (3 << 8) /* [some SAM9 only] */
109 #define AT91SAM9_PMC_MDIV_3 (3 << 8) /* [some SAM9 only] */
110 #define AT91_PMC_PDIV (1 << 12) /* Processor Clock Division [some SAM9 only] */
113 #define AT91_PMC_PLLADIV2 (1 << 12) /* PLLA divisor by 2 [some SAM9 only] */
118 #define AT91_PMC_USB 0x38 /* USB Clock Register [some SAM9 only] */
[all …]
|
| /Linux-v5.4/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 | 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
|
| 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.
|
| /Linux-v5.4/tools/perf/pmu-events/arch/x86/haswell/ |
| D | uncore.json | 7 "BriefDescription": "An external snoop misses in some processor core.",
8 "PublicDescription": "An external snoop misses in some processor core.",
19 … initiated by this Cbox due to processor core memory request which misses in some processor core.",
20 … initiated by this Cbox due to processor core memory request which misses in some processor core.",
31 …"BriefDescription": "A cross-core snoop resulted from L3 Eviction which misses in some processor c…
32 …"PublicDescription": "A cross-core snoop resulted from L3 Eviction which misses in some processor …
43 "BriefDescription": "An external snoop hits a non-modified line in some processor core.",
44 "PublicDescription": "An external snoop hits a non-modified line in some processor core.",
55 … Cbox due to processor core memory request which hits a non-modified line in some processor core.",
56 … Cbox due to processor core memory request which hits a non-modified line in some processor core.",
[all …]
|
| /Linux-v5.4/tools/perf/pmu-events/arch/x86/icelake/ |
| D | floating-point.json | 16 …omputational scalar double precision floating-point instructions retired; some instructions will c…
23 …omputational scalar double precision floating-point instructions retired; some instructions will c…
27 …omputational scalar single precision floating-point instructions retired; some instructions will c…
34 …omputational scalar single precision floating-point instructions retired; some instructions will c…
38 …onal 128-bit packed double precision floating-point instructions retired; some instructions will c…
45 …onal 128-bit packed double precision floating-point instructions retired; some instructions will c…
49 …onal 128-bit packed single precision floating-point instructions retired; some instructions will c…
56 …onal 128-bit packed single precision floating-point instructions retired; some instructions will c…
60 …onal 256-bit packed double precision floating-point instructions retired; some instructions will c…
67 …onal 256-bit packed double precision floating-point instructions retired; some instructions will c…
[all …]
|
| /Linux-v5.4/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 …]
|
| /Linux-v5.4/arch/arm/include/asm/ |
| D | dma.h | 65 * Some architectures may need to do allocate an interrupt
71 * Some architectures may need to do free an interrupt
77 * On some architectures, this may have other side effects like
84 * On some architectures, this may have other side effects like
96 * especially since some DMA architectures don't update the
104 * especially since some DMA architectures don't update the
114 * especially since some DMA architectures don't update the
122 * especially since some DMA architectures don't update the
|
| /Linux-v5.4/drivers/staging/iio/Documentation/ |
| D | overview.txt | 4 that in some sense are analog to digital converters (ADCs). As many
5 actual devices combine some ADCs with digital to analog converters
12 devices. In some cases there is considerable overlap between these and
33 * Hardware buffer support. Some recent sensors have included
41 applications it it useful to be able to capture data based on some
43 signal, a gpio line connected to some external system or an on
|
| /Linux-v5.4/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.
|
| /Linux-v5.4/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";
|
| /Linux-v5.4/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 …]
|
| /Linux-v5.4/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
|
| /Linux-v5.4/fs/affs/ |
| D | Changes | 3 things that can be used since quite some time. But
18 blocks (some very old SCSI drives).
81 - cleanup of some interfaces
118 - Added a few comments, fixed some typos (and
119 introduced some new ones), made the debug messages
150 - Removed some unnecessary locks as Bill
176 - Remove some more superfluous code left over from
179 - Fixed some oversights which were in patch 2.1.78.
203 - Fixed some oversights (version wasn't updated on some
211 effort. This also led to some code cleanup.
[all …]
|
| /Linux-v5.4/drivers/media/rc/keymaps/ |
| D | rc-imon-mce.c | 34 /* 0x800ff40b also KEY_NUMERIC_POUND on some receivers */
37 /* the OK and Enter buttons decode to the same value on some remotes
43 /* 0x800ff40a also KEY_NUMERIC_STAR on some receivers */
76 /* 0x800ff41d also KEY_BLUE on some receivers */
78 /* 0x800ff41c also KEY_PREVIOUS on some receivers */
86 /* 0x800ff424 also KEY_MENU on some receivers */
88 /* 0x800ff425 also KEY_GREEN on some receivers */
|
| /Linux-v5.4/tools/perf/pmu-events/arch/x86/cascadelakex/ |
| D | floating-point.json | 5 …omputational scalar double precision floating-point instructions retired; some instructions will c…
14 …omputational scalar single precision floating-point instructions retired; some instructions will c…
23 …onal 128-bit packed double precision floating-point instructions retired; some instructions will c…
32 …onal 128-bit packed single precision floating-point instructions retired; some instructions will c…
41 …onal 256-bit packed double precision floating-point instructions retired; some instructions will c…
50 …onal 256-bit packed single precision floating-point instructions retired; some instructions will c…
59 …onal 512-bit packed double precision floating-point instructions retired; some instructions will c…
68 …onal 512-bit packed single precision floating-point instructions retired; some instructions will c…
|
| /Linux-v5.4/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 …]
|
| /Linux-v5.4/tools/perf/Documentation/ |
| D | perf-list.txt | 70 some special cases
116 details. Some of them are referenced in the SEE ALSO section below.
141 Some PMUs are not associated with a core, but with a whole CPU socket.
170 like cycles and instructions and some software events.
173 Some event qualifiers, such as "any", are also root only.
185 Some PMUs control advanced hardware tracing capabilities, such as Intel PT,
192 Some pmu events listed by 'perf-list' will be displayed with '?' in them. For
223 ensure some events are always measured together as a group to minimize multiplexing
232 ref-cycles. Some special events have restrictions on which counter they
234 When too many events are specified in the group some of them will not
[all …]
|
| /Linux-v5.4/drivers/scsi/ufs/ |
| D | ufs_quirks.h | 39 * Some vendor's UFS device sends back to back NACs for the DL data frames
57 * If DL NAC error is seen multiple times with some vendor's UFS devices then
73 * It seems some UFS devices may keep drawing more than sleep current
81 * Some UFS devices require host PA_TACTIVATE to be lower than device
88 * some vendors.
97 * Some UFS devices require VS_DebugSaveConfigTime is 0x10,
|
| /Linux-v5.4/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
|
| /Linux-v5.4/drivers/net/ethernet/qlogic/qed/ |
| D | qed_ll2.h | 137 * @param cxt - pointer to the hw-function [opaque to some]
147 * @param cxt - pointer to the hw-function [opaque to some]
159 * @param cxt - pointer to the hw-function [opaque to some]
177 * @param cxt - pointer to the hw-function [opaque to some]
193 * @param cxt - pointer to the hw-function [opaque to some]
204 * @param cxt - pointer to the hw-function [opaque to some]
221 * @param cxt - pointer to the hw-function [opaque to some]
234 * @param cxt - pointer to the hw-function [opaque to some]
|
