Searched full:those (Results 1 – 25 of 686) sorted by relevance
12345678910>>...28
| /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/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/devicetree/bindings/timer/ |
| D | mediatek,mtk-timer.txt | 12 For those SoCs that use GPT
23 For those SoCs that use SYST
|
| /Documentation/media/uapi/v4l/ |
| D | pixfmt-intro.rst | 48 listed below, however they are not the same as those used in the Windows
52 buffers. Those formats are identified by a separate set of FourCC codes
58 3-planar case. Those sub-buffers are referred to as "*planes*".
|
| D | pixfmt-meta-uvc.rst | 26 in those headers. See section "2.4.3.3 Video and Still Image Payload Headers" of
32 buffer is full, when they contain no useful information (e.g. those without the
|
| /Documentation/devicetree/bindings/sound/ |
| D | fsl-asoc-card.txt | 7 for Freescale SoCs (especially those released in recent years), most of them
16 Note: The card is initially designed for those sound cards who use AC'97, I2S
17 and PCM DAI formats. However, it'll be also possible to support those non
|
| /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/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/media/kapi/ |
| 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
|
| D | dtv-common.rst | 18 Those functions are responsible for handling the DVB device nodes.
25 Those routines implement ring buffers used to handle digital TV data and
|
| /Documentation/media/uapi/mediactl/ |
| D | media-controller-intro.rst | 36 increasingly high number of those parameters, drivers need to guess what
40 The media controller API aims at solving those problems.
|
| /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/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/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
|
| 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
|
| /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/devicetree/bindings/pinctrl/ |
| 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/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 …]
|
| /Documentation/driver-api/ |
| D | i2c.rst | 24 Those devices will be bound to a :c:type:`struct i2c_driver
36 i2c_adapter devices which don't support those I2C operations.
|
| /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,
87 all the quirks of those OS's. Certainly it would make more sense
94 that anybody would install those old operating systems
109 An old OS that doesn't know about those extensions would answer FALSE,
|
| /Documentation/devicetree/bindings/pci/ |
| D | plda,xpressrich3-axi.txt | 4 makes it compliant with the SBSA[1] standard published by ARM Ltd. For those
|
| /Documentation/devicetree/bindings/clock/ |
| D | exynos4-clock.txt | 46 subsystem. Registers for those clocks are located in the ISP power domain.
47 Because those registers are also located in a different memory region than
|
12345678910>>...28