Searched full:those (Results 1 – 25 of 5093) sorted by relevance
12345678910>>...204
| /kernel/linux/linux-6.6/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…
|
| /kernel/linux/linux-6.6/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…
|
| /kernel/linux/linux-6.6/net/mac80211/ |
| D | Kconfig | 171 be selected on production systems as those messages
182 be selected on production systems as those messages
194 It should not be selected on production systems as those
207 It should not be selected on production systems as those
220 It should not be selected on production systems as those
233 It should not be selected on production systems as those
278 It should not be selected on production systems as those
|
| /kernel/linux/linux-5.10/net/mac80211/ |
| D | Kconfig | 171 be selected on production systems as those messages
182 be selected on production systems as those messages
194 It should not be selected on production systems as those
207 It should not be selected on production systems as those
220 It should not be selected on production systems as those
233 It should not be selected on production systems as those
278 It should not be selected on production systems as those
|
| /kernel/linux/linux-6.6/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
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-5.10/drivers/clk/sunxi/ |
| D | Kconfig | 25 Legacy clock driver for the A31 PRCM clocks. Those are
34 Those are usually needed for the PMIC communication,
41 Legacy clock driver for the A80 PRCM clocks. Those are
|
| /kernel/linux/linux-6.6/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
|
| /kernel/linux/linux-5.10/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 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 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 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
|
| /kernel/linux/linux-6.6/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
|
| /kernel/linux/linux-5.10/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
132 Other fixes will take longer, especially those relating to structure
134 is necessary to work out what the role of those members or parameters is
144 many of those comments are never pulled into the docs build. That makes
147 the documentation to bring those comments in can help the community derive
155 kerneldoc comments for internal use; those should not be pulled into the
250 who work with those files; they are understandably unenthusiastic about
256 trying to knit all of those documents together into a single whole has not
|
| /kernel/linux/linux-6.6/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
145 many of those comments are never pulled into the docs build. That makes
148 the documentation to bring those comments in can help the community derive
156 kerneldoc comments for internal use; those should not be pulled into the
251 who work with those files; they are understandably unenthusiastic about
257 trying to knit all of those documents together into a single whole has not
|
| /kernel/linux/linux-5.10/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.
131 The contents of each of those pin configuration child nodes is defined
|
| /kernel/linux/linux-5.10/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()
|
| /kernel/linux/linux-6.6/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()
|
| /kernel/linux/linux-6.6/Documentation/driver-api/gpio/ |
| D | legacy.rst | 49 - Most GPIOs can be accessed while holding spinlocks, but those accessed
99 Platforms define how they use those integers, and usually #define symbols
109 The numbers need not be contiguous; either of those platforms could also
165 Those don't need to sleep, and can safely be done from inside hard
183 platforms can read the value of output pins; those that can't should always
199 or SPI. Commands to read or write those GPIO values require waiting to
211 a threaded IRQ handler, and those accessors must be used instead of
282 configured prior to gpio_request() being called for those GPIOs, e.g. using
360 Those return either the corresponding number in the other namespace, or
454 to route a given GPIO to any one of several pins. (Yes, those examples all
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/timer/ |
| D | mediatek,mtk-timer.txt | 13 For those SoCs that use GPT
25 For those SoCs that use SYST
34 For those SoCs that use CPUX
|
| /kernel/linux/linux-6.6/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.
|
| /kernel/linux/linux-6.6/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
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-5.10/Documentation/driver-api/gpio/ |
| D | legacy.rst | 49 - Most GPIOs can be accessed while holding spinlocks, but those accessed
99 Platforms define how they use those integers, and usually #define symbols
109 The numbers need not be contiguous; either of those platforms could also
165 Those don't need to sleep, and can safely be done from inside hard
184 platforms can read the value of output pins; those that can't should always
200 or SPI. Commands to read or write those GPIO values require waiting to
220 a threaded IRQ handler, and those accessors must be used instead of
293 configured prior to gpio_request() being called for those GPIOs, e.g. using
393 Those return either the corresponding number in the other namespace, or
492 to route a given GPIO to any one of several pins. (Yes, those examples all
[all …]
|
12345678910>>...204