Searched full:those (Results 1 – 25 of 5069) sorted by relevance
12345678910>>...203
| /kernel/linux/linux-4.19/Documentation/laptops/ |
| D | sonypi.txt | 15 It will give access (through a user space utility) to some events those laptops
24 Those events (see linux/sonypi.h) can be polled using the character device node
50 statically linked into the kernel). Those options are:
112 In order to automatically load the sonypi module on use, you can put those
128 driver disables all APM management for those keys, by enabling the
130 you have one of those laptops with working Fn keys and want to
146 is a userspace utility to adjust the brightness on those models,
|
| D | sony-laptop.txt | 15 subsystem. See the logs of /proc/bus/input/devices to find out what those
44 You then read/write integer values from/to those files by using
79 /sys/class/rfkill. Check those starting with sony-* in
110 I HAVE NO IDEA WHAT THOSE METHODS DO.
112 The sony-laptop driver creates, for some of those methods (the most
121 those entries are for, by reading/writing random values from/to 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-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-4.19/net/mac80211/ |
| D | Kconfig | 186 be selected on production systems as those messages
197 be selected on production systems as those messages
209 It should not be selected on production systems as those
222 It should not be selected on production systems as those
235 It should not be selected on production systems as those
248 It should not be selected on production systems as those
293 It should not be selected on production systems as 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-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-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/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-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-4.19/Documentation/media/kapi/ |
| D | dtv-frontend.rst | 110 signal strength, S/N and UCB. Those are there to provide backward
112 API. Implementing those callbacks are optional. Those callbacks may be
234 available when the main carrier is detected. On those hardware, CNR
245 - Those counters measure the number of bits and bit errors errors after
249 - Due to its nature, those statistics depend on full coding lock
254 - Those counters measure the number of bits and bit errors errors before
260 - Due to its nature, those statistics depend on inner coding lock (e. g.
264 - Those counters measure the number of blocks and block errors errors after
268 - Due to its nature, those statistics depend on full coding lock
386 On those devices, the driver need to ensure that it won't be reading from
|
| /kernel/linux/linux-4.19/arch/arm/include/asm/ |
| D | cpufeature.h | 21 * Currently, only a few of those are suitable for automatic module loading
22 * (which is the primary use case of this facility) and those happen to be all
23 * covered by HWCAP2. So let's only cover those via the cpu_feature()
|
| /kernel/linux/linux-4.19/Documentation/acpi/ |
| D | scan_handlers.txt | 10 and the hierarchy of those struct acpi_device objects reflects the namespace
12 struct acpi_device objects and analogously for their children). Those struct
15 parsing code (although their role is analogous to the role of those objects).
30 Those additional configuration tasks usually depend on the type of the hardware
|
| /kernel/linux/linux-4.19/scripts/ |
| D | check_00index.sh | 52 echo -e "- Should remove those entries:\n\t$obsolete\n"
58 echo -e "- Should document those directories:\n\t$dir\n"
64 echo -e "- Should document those files:\n\t$file"
|
| /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-4.19/drivers/gpu/drm/i915/ |
| D | i915_scheduler.h | 29 * @priority will be executed before those with a lower @priority
57 struct list_head signalers_list; /* those before us, we depend upon */
58 struct list_head waiters_list; /* those after us, they depend upon us */
|
| /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 …]
|
| /kernel/linux/linux-4.19/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 …]
|
| /kernel/linux/linux-4.19/certs/ |
| D | Kconfig | 26 userspace may only add extra keys if those keys can be verified by
42 those are no longer used. You will need to set this option instead.
65 those keys are not blacklisted and are vouched for by a key built
|
| /kernel/linux/linux-4.19/Documentation/fb/ |
| D | tridentfb.txt | 6 those from the TGUI series 9440/96XX and with Cyber in their names
7 those from the Image series and with Cyber in their names
8 those with Blade in their names (Blade3D,CyberBlade...)
|
| /kernel/linux/linux-5.10/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*".
|
| /kernel/linux/linux-4.19/Documentation/media/uapi/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*".
|
| /kernel/linux/linux-5.10/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.
163 which has been posted by those with more experience. Even code written by
|
| /kernel/linux/linux-4.19/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.
163 which has been posted by those with more experience. Even code written by
|
12345678910>>...203