Searched full:those (Results 1 – 25 of 4116) sorted by relevance
12345678910>>...165
| /linux-6.12.1/tools/perf/pmu-events/arch/arm64/arm/neoverse-v1/ |
| D | tlb.json | 20 …sed by memory operations from both data and instruction fetch, except for those caused by TLB main…
24 …"PublicDescription": "Counts level 2 TLB accesses except those caused by TLB maintenance operation…
52 …by memory read operations from both data and instruction fetch except for those caused by TLB main…
56 …y memory write operations from both data and instruction fetch except for those caused by TLB main…
60 …by memory read operations from both data and instruction fetch except for those caused by TLB main…
64 …y memory write operations from both data and instruction fetch except for those caused by TLB main…
|
| D | memory.json | 4 …those accesses are issued due to load or store operations. This event counts memory accesses no ma…
16 … transactions that are issued by the bus interface, then the event counts those smaller transactio…
20 … transactions that are issued by the bus interface, then the event counts those smaller transactio…
|
| /linux-6.12.1/tools/perf/pmu-events/arch/arm64/arm/neoverse-n1/ |
| D | tlb.json | 20 …sed by memory operations from both data and instruction fetch, except for those caused by TLB main…
24 …"PublicDescription": "Counts level 2 TLB accesses except those caused by TLB maintenance operation…
52 …by memory read operations from both data and instruction fetch except for those caused by TLB main…
56 …y memory write operations from both data and instruction fetch except for those caused by TLB main…
60 …by memory read operations from both data and instruction fetch except for those caused by TLB main…
64 …y memory write operations from both data and instruction fetch except for those caused by TLB main…
|
| D | memory.json | 4 …those accesses are issued due to load or store operations. This event counts memory accesses no ma…
16 … transactions that are issued by the bus interface, then the event counts those smaller transactio…
20 … transactions that are issued by the bus interface, then the event counts those smaller transactio…
|
| /linux-6.12.1/tools/perf/pmu-events/arch/arm64/arm/neoverse-n2-v2/ |
| D | tlb.json | 20 …sed by memory operations from both data and instruction fetch, except for those caused by TLB main…
24 …"PublicDescription": "Counts level 2 TLB accesses except those caused by TLB maintenance operation…
52 …by memory read operations from both data and instruction fetch except for those caused by TLB main…
56 …y memory write operations from both data and instruction fetch except for those caused by TLB main…
60 …by memory read operations from both data and instruction fetch except for those caused by TLB main…
64 …y memory write operations from both data and instruction fetch except for those caused by TLB main…
|
| D | memory.json | 4 …those accesses are issued due to load or store operations. This event counts memory accesses no ma…
16 … transactions that are issued by the bus interface, then the event counts those smaller transactio…
20 … transactions that are issued by the bus interface, then the event counts those smaller transactio…
|
| /linux-6.12.1/net/mac80211/ |
| D | Kconfig | 181 be selected on production systems as those messages
192 be selected on production systems as those messages
204 It should not be selected on production systems as those
217 It should not be selected on production systems as those
230 It should not be selected on production systems as those
243 It should not be selected on production systems as those
288 It should not be selected on production systems as those
|
| /linux-6.12.1/Documentation/admin-guide/laptops/ |
| D | sonypi.rst | 17 It will give access (through a user space utility) to some events those laptops
27 Those events (see linux/sonypi.h) can be polled using the character device node
53 statically linked into the kernel). Those options are:
118 In order to automatically load the sonypi module on use, you can put those
134 driver disables all APM management for those keys, by enabling the
136 you have one of those laptops with working Fn keys and want to
152 is a userspace utility to adjust the brightness on those models,
|
| D | sony-laptop.rst | 18 subsystem. See the logs of /proc/bus/input/devices to find out what those
50 You then read/write integer values from/to those files by using
105 /sys/class/rfkill. Check those starting with sony-* in::
140 **I HAVE NO IDEA WHAT THOSE METHODS DO.**
142 The sony-laptop driver creates, for some of those methods (the most
151 those entries are for, by reading/writing random values from/to those
|
| /linux-6.12.1/drivers/clk/sunxi/ |
| D | Kconfig | 24 Legacy clock driver for the A31 PRCM clocks. Those are
32 Those are usually needed for the PMIC communication,
39 Legacy clock driver for the A80 PRCM clocks. Those are
|
| /linux-6.12.1/Documentation/driver-api/media/ |
| D | dtv-frontend.rst | 112 signal strength, S/N and UCB. Those are there to provide backward
114 API. Implementing those callbacks are optional. Those callbacks may be
236 available when the main carrier is detected. On those hardware, CNR
247 - Those counters measure the number of bits and bit errors after
251 - Due to its nature, those statistics depend on full coding lock
256 - Those counters measure the number of bits and bit errors before
262 - Due to its nature, those statistics depend on inner coding lock (e. g.
266 - Those counters measure the number of blocks and block errors after
270 - Due to its nature, those statistics depend on full coding lock
388 On those devices, the driver need to ensure that it won't be reading from
|
| /linux-6.12.1/Documentation/doc-guide/ |
| D | contributing.rst | 44 problem; making those warnings go away requires understanding the problem
52 documentation tree is often not the right one to actually carry those
133 Other fixes will take longer, especially those relating to structure
135 is necessary to work out what the role of those members or parameters is
149 many of those comments are never pulled into the docs build. That makes
152 the documentation to bring those comments in can help the community derive
160 kerneldoc comments for internal use; those should not be pulled into the
255 who work with those files; they are understandably unenthusiastic about
261 trying to knit all of those documents together into a single whole has not
|
| /linux-6.12.1/arch/arm/include/asm/ |
| D | cpufeature.h | 18 * Currently, only a few of those are suitable for automatic module loading
19 * (which is the primary use case of this facility) and those happen to be all
20 * covered by HWCAP2. So let's only cover those via the cpu_feature()
|
| /linux-6.12.1/Documentation/process/ |
| D | 7.AdvancedTopics.rst | 24 especially as the volume of those patches grows. Git also has its rough
57 developers can get an account on kernel.org, but those are not easy to come
86 for those developers. So a simple rule of thumb applies here: history
90 So, once you push a set of changes to your publicly-available server, those
147 sure that you have remembered to push those changes to the public server.
164 which has been posted by those with more experience. Even code written by
173 then call for opinions of other reviewers or maintainers. Often those in
|
| D | 1.Intro.rst | 64 those products attractive to Linux users. Embedded systems vendors, who
95 being helpful to those who are trying to learn, has little time for those
98 It is hoped that those who read this document will be able to avoid that
102 better; the following text should help you - or those who work for you -
200 determined by the courts. But the uncertainty which haunts those modules
264 answers, but one should bear in mind that the people answering those
|
| /linux-6.12.1/Documentation/userspace-api/ |
| D | mseal.rst | 61 number of supported VMAs. In those cases, partial updates to the given
62 memory range could happen. However, those cases should be rare.
143 ksys_shmdt() in shm.c. The lifetimes of those mapping are not tied to
144 the lifetime of the process. If those memories are sealed from userspace,
171 to RO memory, which is, in a way, by design. And those could be blocked
174 Those cases are:
|
| /linux-6.12.1/Documentation/devicetree/bindings/pinctrl/ |
| D | pinctrl-bindings.txt | 17 states. The number and names of those states is defined by the client device's
21 for client device device tree nodes to map those state names to the pin
22 configuration used by those states.
39 those names to the integer IDs.
|
| /linux-6.12.1/Documentation/driver-api/acpi/ |
| D | scan_handlers.rst | 16 and the hierarchy of those struct acpi_device objects reflects the namespace
18 struct acpi_device objects and analogously for their children). Those struct
21 parsing code (although their role is analogous to the role of those objects).
36 Those additional configuration tasks usually depend on the type of the hardware
|
| /linux-6.12.1/Documentation/core-api/ |
| D | dma-api.rst | 68 size and dma_handle must all be the same as those passed into
227 transfer memory ownership. Returns %false if those calls can be skipped.
328 must be identical to those passed in (and returned) by the mapping
421 must be the same as those and passed in to the scatter/gather mapping
451 as those passed into the sg mapping API. With the sync_single API,
453 those passed into the single mapping API to do a partial sync.
500 is identical to those of the corresponding function
578 dev, size, dma_handle and dir must all be the same as those passed into
588 dev and size must be the same as those passed into dma_alloc_pages().
608 dev, size, dma_handle and dir must all be the same as those passed into
[all …]
|
| /linux-6.12.1/Documentation/userspace-api/media/v4l/ |
| D | pixfmt-intro.rst | 41 listed below, however they are not the same as those used in the Windows
45 buffers. Those formats are identified by a separate set of FourCC codes
51 3-planar case. Those sub-buffers are referred to as "*planes*".
|
| /linux-6.12.1/Documentation/devicetree/bindings/i2c/ |
| D | nvidia,tegra20-i2c.yaml | 53 similar to those found on Tegra114 but also contain several hardware
58 similar to those found on Tegra124.
74 similar to those found on Tegra210.
79 similar to those found on Tegra186. However, these controllers have
|
| /linux-6.12.1/Documentation/usb/ |
| D | ehci.rst | 40 but those changes haven't needed to really change the basic "usbcore"
80 controller. This driver doesn't need to know anything about those
134 The contents of those files can help identify driver problems.
145 Those hubs report some failures, such as disconnections, differently when
162 and at most 13 of those fit into one USB 2.0 microframe. Eight USB 2.0
224 Interrupt and ISO transfer performance issues. Those periodic
|
| /linux-6.12.1/Documentation/maintainer/ |
| D | rebasing-and-merging.rst | 10 ways to use those features. This document looks in particular at the use
12 those tools incorrectly, but avoiding problems is not actually all that
73 between release points; basing development on one of those points
111 the mainline. The best practices to follow differ in those two situations.
191 merge has been done. Take a moment to do it right; people will read those
203 commits for one development cycle so that those changes have time to
|
| /linux-6.12.1/Documentation/mm/ |
| D | unevictable-lru.rst | 43 * Those owned by ramfs.
45 * Those owned by tmpfs with the noswap mount option.
47 * Those mapped into SHM_LOCK'd shared memory regions.
49 * Those mapped into VM_LOCKED [mlock()ed] VMAs.
195 "cull" such folios that it encounters: that is, it diverts those folios to the
306 mark those pages as mlocked as they are faulted.
373 any "special" VMAs. So, those VMAs will be ignored for munlock.
389 those cases its mlock_count field is unusable and must be assumed to be 0: so
414 before mlocking any pages already present, if one of those pages were migrated
454 /proc/meminfo's Unevictable and Mlocked amounts do not include those parts
[all …]
|
| /linux-6.12.1/Documentation/firmware-guide/acpi/ |
| D | osi.rst | 22 Linux runs on two groups of machines -- those that are tested by the OEM
23 to be compatible with Linux, and those that were never tested with Linux,
84 all the quirks of those OS's. Certainly it would make more sense
91 that anybody would install those old operating systems
106 An old OS that doesn't know about those extensions would answer FALSE,
|
12345678910>>...165