Searched full:those (Results 1 – 25 of 847) sorted by relevance
12345678910>>...34
| /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
|
| /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*".
|
| D | metafmt-uvc.rst | 19 in those headers. See section "2.4.3.3 Video and Still Image Payload Headers" of
25 buffer is full, when they contain no useful information (e.g. those without the
|
| /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.
|
| D | pinctrl-vt8500.txt | 24 more of the mux functions to select on those pin(s), and pull-up/down
25 configuration. Each subnode only affects those parameters that are explicitly
|
| /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
|
| /Documentation/userspace-api/media/mediactl/ |
| D | media-controller-intro.rst | 29 increasingly high number of those parameters, drivers need to guess what
33 The media controller API aims at solving those problems.
|
| /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
|
| /Documentation/ABI/testing/ |
| D | sysfs-bus-iio-isl29501 | 36 From those two curves, a and b coefficients shall be
42 Those values must be integer in [0; 8355840] range.
|
| /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
|
| D | dtv-common.rst | 9 Those functions are responsible for handling the DVB device nodes.
16 Those routines implement ring buffers used to handle digital TV data and
|
| /Documentation/fb/ |
| D | tridentfb.rst | 10 those from the TGUI series 9440/96XX and with Cyber in their names
11 those from the Image series and with Cyber in their names
12 those with Blade in their names (Blade3D,CyberBlade...)
|
| /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:
|
| /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
|
| /Documentation/hwmon/ |
| D | adc128d818.rst | 48 addresses 0x35 to 0x37. Those addresses are not scanned. You have to instantiate
49 the driver explicitly if the chip is configured for any of those addresses in
|
| /Documentation/driver-api/media/drivers/ |
| D | saa7134-devel.rst | 19 - saa7130 - low-price chip, doesn't have mute, that is why all those
24 - saa7133/35 - saa7135 is probably a marketing decision, since all those
|
| /Documentation/arch/arm/sa1100/ |
| D | serial_uart.rst | 14 > serial devices", so you will have a range of minors on those majors (the
31 You must create those inodes in /dev on the root filesystem used
|
| /Documentation/netlabel/ |
| D | introduction.rst | 23 security attributes and those on the host are required then the protocol
24 engine will handle those tasks as well. Other kernel subsystems should
|
| /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
|
| /Documentation/core-api/ |
| D | dma-attributes.rst | 15 those that do not will simply ignore the attribute and exhibit default
25 those that do not will simply ignore the attribute and exhibit default
43 DMA_ATTR_NO_KERNEL_MAPPING, those that do not will simply ignore the
119 So, this provides a way for drivers to avoid those error messages on calls
|
| /Documentation/admin-guide/ |
| D | lockup-watchdogs.rst | 73 from protecting the user code on those cores from the kernel.
75 when those cores do enter the kernel, by default we will not be
78 that we will continue to detect lockups properly on those cores.
|
| /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
|
| /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
|
| /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>>...34