Searched full:their (Results 1 – 25 of 7280) sorted by relevance
12345678910>>...292
| /kernel/linux/linux-5.10/drivers/clk/qcom/ |
| D | clk-regmap.c | 18 * Clocks that use regmap for their register I/O can set the
19 * enable_reg and enable_mask fields in their struct clk_regmap and then use
20 * this as their is_enabled operation, saving some code.
44 * Clocks that use regmap for their register I/O can set the
45 * enable_reg and enable_mask fields in their struct clk_regmap and then use
46 * this as their enable() operation, saving some code.
68 * Clocks that use regmap for their register I/O can set the
69 * enable_reg and enable_mask fields in their struct clk_regmap and then use
70 * this as their disable() operation, saving some code.
92 * Clocks that use regmap for their register I/O should register their
|
| /kernel/linux/linux-6.6/drivers/clk/qcom/ |
| D | clk-regmap.c | 18 * Clocks that use regmap for their register I/O can set the
19 * enable_reg and enable_mask fields in their struct clk_regmap and then use
20 * this as their is_enabled operation, saving some code.
44 * Clocks that use regmap for their register I/O can set the
45 * enable_reg and enable_mask fields in their struct clk_regmap and then use
46 * this as their enable() operation, saving some code.
68 * Clocks that use regmap for their register I/O can set the
69 * enable_reg and enable_mask fields in their struct clk_regmap and then use
70 * this as their disable() operation, saving some code.
93 * Clocks that use regmap for their register I/O should register their
|
| /kernel/linux/linux-5.10/drivers/regulator/ |
| D | helpers.c | 23 * Regulators that use regmap for their register I/O can set the
24 * enable_reg and enable_mask fields in their descriptor and then use
25 * this as their is_enabled operation, saving some code.
55 * Regulators that use regmap for their register I/O can set the
56 * enable_reg and enable_mask fields in their descriptor and then use
57 * this as their enable() operation, saving some code.
81 * Regulators that use regmap for their register I/O can set the
82 * enable_reg and enable_mask fields in their descriptor and then use
83 * this as their disable() operation, saving some code.
124 * Regulators that use regmap for their register I/O and use pickable
[all …]
|
| /kernel/linux/linux-6.6/Documentation/process/ |
| D | contribution-maturity-model.rst | 16 maintainers as part of their job, so they can grow into becoming
29 The TAB urges organizations to continuously evaluate their Open Source
34 publish their evaluations and plans to improve their engagement with the
48 kernel, either as part of their job responsibilities or on their own
55 part of their job responsibilities.
57 conferences as a part of their job.
65 authored by engineers from other companies) as part of their job
72 * Organizations will regularly report metrics of their open source
91 * Software Engineers are encouraged to spend a portion of their work
|
| D | 1.Intro.rst | 10 and the kinds of frustrations that developers and their employers can
63 vendors want to ensure that Linux supports their products well, making
67 other software vendors who base their products on Linux have a clear
70 better suit their needs.
121 learning how to work with the kernel community and get their code into the
169 to implement changes which make the kernel work better for their needs.
196 a result, their distribution is a violation of the GNU General Public
212 will have to upgrade your module separately every time they upgrade their
249 be obtained (or their code removed from the kernel). So, in particular,
256 off" on their code, stating that the code can be distributed with the
|
| D | 6.Followthrough.rst | 9 developers can make is to conclude that their work is now done. In truth,
47 - Similarly, code reviewers are not trying to promote their employers'
49 be working on the kernel years from now, but they understand that their
52 trying to create discomfort for their employers' competitors.
63 making. Do not let their form of expression or your own pride keep that
67 thank them, and describe how you will answer their questions.
129 default. Subsystem trees typically feed linux-next as well, making their
161 how many people will build your code into their kernels. And, of course,
186 development community remembers developers who lose interest in their code
|
| /kernel/linux/linux-6.6/drivers/regulator/ |
| D | helpers.c | 24 * Regulators that use regmap for their register I/O can set the
25 * enable_reg and enable_mask fields in their descriptor and then use
26 * this as their is_enabled operation, saving some code.
56 * Regulators that use regmap for their register I/O can set the
57 * enable_reg and enable_mask fields in their descriptor and then use
58 * this as their enable() operation, saving some code.
82 * Regulators that use regmap for their register I/O can set the
83 * enable_reg and enable_mask fields in their descriptor and then use
84 * this as their disable() operation, saving some code.
126 * Regulators that use regmap for their register I/O and use pickable
[all …]
|
| /kernel/linux/linux-6.6/Documentation/admin-guide/blockdev/drbd/ |
| D | data-structure-v9.rst | 30 In this table, horizontally, devices can be accessed from resources by their
32 their volume number. Objects in the vertical direction are connected by double
33 linked lists. There are back pointers from peer_devices to their connections a
34 devices, and from connections and devices to their resource.
37 devices can be accessed by their minor device number via the drbd_devices idr.
41 devices and connections; their lifetime is determined by the lifetime of the
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/blockdev/drbd/ |
| D | data-structure-v9.rst | 30 In this table, horizontally, devices can be accessed from resources by their
32 their volume number. Objects in the vertical direction are connected by double
33 linked lists. There are back pointers from peer_devices to their connections a
34 devices, and from connections and devices to their resource.
37 devices can be accessed by their minor device number via the drbd_devices idr.
41 devices and connections; their lifetime is determined by the lifetime of the
|
| /kernel/linux/linux-5.10/arch/arm/ |
| D | Kconfig.debug | 102 # These options are only for real kernel hackers who want to get their hands dirty.
133 their output to an UART or USART port on asm9260 based
191 their output to the USART1 port on SAMV7 based
220 their output to the third serial port on these devices.
250 their output to the first serial port on these devices. The
262 their output to the first serial port on these devices.
269 their output to the second serial port on these devices.
277 their output to the CNS3xxx UART0.
285 their output to UART1 serial port on DaVinci DA8XX devices.
293 their output to UART2 serial port on DaVinci DA8XX devices.
[all …]
|
| /kernel/linux/linux-6.6/drivers/media/test-drivers/vidtv/ |
| D | vidtv_channel.h | 10 * Their services will be concatenated to populate the SDT.
11 * Their programs will be concatenated to populate the PAT
12 * Their events will be concatenated to populate the EIT
35 * Their services will be concatenated to populate the SDT.
36 * Their programs will be concatenated to populate the PAT
|
| /kernel/linux/linux-5.10/drivers/media/test-drivers/vidtv/ |
| D | vidtv_channel.h | 10 * Their services will be concatenated to populate the SDT.
11 * Their programs will be concatenated to populate the PAT
12 * Their events will be concatenated to populate the EIT
35 * Their services will be concatenated to populate the SDT.
36 * Their programs will be concatenated to populate the PAT
|
| /kernel/linux/linux-6.6/include/drm/ |
| D | drm_gem_shmem_helper.h | 139 * should use it as their &drm_gem_object_funcs.free handler.
155 * use this function as their &drm_gem_object_funcs.print_info handler.
170 * use it as their &drm_gem_object_funcs.pin handler.
184 * use it as their &drm_gem_object_funcs.unpin handler.
198 * use it as their &drm_gem_object_funcs.get_sg_table handler.
216 * use it as their &drm_gem_object_funcs.vmap handler.
235 * use it as their &drm_gem_object_funcs.vunmap handler.
251 * use it as their &drm_gem_object_funcs.mmap handler.
|
| D | drm_gem_dma_helper.h | 56 * should use it as their &drm_gem_object_funcs.free handler.
72 * should use this function as their &drm_gem_object_funcs.print_info handler.
87 * use it as their &drm_gem_object_funcs.get_sg_table handler.
105 * use it as their &drm_gem_object_funcs.vmap handler.
124 * use it as their &drm_gem_object_funcs.mmap handler.
178 * Drivers that come with their own implementation of
215 * Drivers that come with their own implementation of
|
| /kernel/linux/linux-6.6/drivers/video/fbdev/core/ |
| D | Kconfig | 50 filling. This is used by drivers that don't provide their own
58 This is used by drivers that don't provide their own (accelerated)
66 blitting. This is used by drivers that don't provide their own
82 filling. This is used by drivers that don't provide their own
90 This is used by drivers that don't provide their own (accelerated)
98 blitting. This is used by drivers that don't provide their own
|
| /kernel/linux/linux-5.10/include/linux/ |
| D | irqchip.h | 21 * the association between their DT compatible string and their
55 * the association between their version and their initialization function.
|
| /kernel/linux/linux-5.10/Documentation/networking/devlink/ |
| D | devlink-trap.rst | 31 The ``devlink-trap`` mechanism allows capable device drivers to register their
125 Such traps can be shared by multiple device drivers and their description must
185 routed and their destination IP is the loopback address (i.e., 127.0.0.0/8
190 routed and their source IP is multicast (i.e., 224.0.0.0/8 and ff::/8)
194 routed and their source IP is the loopback address (i.e., 127.0.0.0/8 and ::1/128)
198 routed and their IP header is corrupted: wrong checksum, wrong IP version
203 routed and their source IP is limited broadcast (i.e., 255.255.255.255/32)
207 be routed and their IPv6 multicast destination IP has a reserved scope
212 be routed and their IPv6 multicast destination IP has an interface-local scope
247 - Traps NVE packets that the device decided to drop because their overlay
[all …]
|
| /kernel/linux/linux-6.6/Documentation/networking/devlink/ |
| D | devlink-trap.rst | 31 The ``devlink-trap`` mechanism allows capable device drivers to register their
125 Such traps can be shared by multiple device drivers and their description must
185 routed and their destination IP is the loopback address (i.e., 127.0.0.0/8
190 routed and their source IP is multicast (i.e., 224.0.0.0/8 and ff::/8)
194 routed and their source IP is the loopback address (i.e., 127.0.0.0/8 and ::1/128)
198 routed and their IP header is corrupted: wrong checksum, wrong IP version
203 routed and their source IP is limited broadcast (i.e., 255.255.255.255/32)
207 be routed and their IPv6 multicast destination IP has a reserved scope
212 be routed and their IPv6 multicast destination IP has an interface-local scope
247 - Traps NVE packets that the device decided to drop because their overlay
[all …]
|
| /kernel/linux/linux-5.10/Documentation/power/regulator/ |
| D | consumer.rst | 75 Some consumer drivers need to be able to dynamically change their supply
80 Consumers can control their supply voltage by calling::
106 Some consumer drivers need to be able to dynamically change their supply
111 Consumers can control their supply current limit by calling::
138 their supply regulator to be more efficient when the consumers operating state
145 Consumer drivers can request a change in their supply regulator operating mode
166 operating mode depending on their operating point. This can be achieved by
192 Regulators use the kernel notifier framework to send event to their interested
|
| /kernel/linux/linux-6.6/Documentation/power/regulator/ |
| D | consumer.rst | 75 Some consumer drivers need to be able to dynamically change their supply
80 Consumers can control their supply voltage by calling::
106 Some consumer drivers need to be able to dynamically change their supply
111 Consumers can control their supply current limit by calling::
138 their supply regulator to be more efficient when the consumers operating state
145 Consumer drivers can request a change in their supply regulator operating mode
166 operating mode depending on their operating point. This can be achieved by
192 Regulators use the kernel notifier framework to send event to their interested
|
| /kernel/linux/linux-6.6/include/linux/ |
| D | irqchip.h | 28 * the association between their DT compatible string and their
67 * the association between their version and their initialization function.
|
| /kernel/linux/linux-5.10/Documentation/process/ |
| D | 1.Intro.rst | 10 and the kinds of frustrations that developers and their employers can
63 vendors want to ensure that Linux supports their products well, making
67 other software vendors who base their products on Linux have a clear
70 better suit their needs.
121 learning how to work with the kernel community and get their code into the
169 to implement changes which make the kernel work better for their needs.
196 a result, their distribution is a violation of the GNU General Public
212 will have to upgrade your module separately every time they upgrade their
249 be obtained (or their code removed from the kernel). So, in particular,
256 off" on their code, stating that the code can be distributed with the
|
| D | 6.Followthrough.rst | 9 developers can make is to conclude that their work is now done. In truth,
47 - Similarly, code reviewers are not trying to promote their employers'
49 be working on the kernel years from now, but they understand that their
52 trying to create discomfort for their employers' competitors.
56 making. Do not let their form of expression or your own pride keep that
60 thank them, and describe how you will answer their questions.
122 default. Subsystem trees typically feed linux-next as well, making their
154 how many people will build your code into their kernels. And, of course,
179 development community remembers developers who lose interest in their code
|
| /kernel/linux/linux-6.6/Documentation/usb/ |
| D | CREDITS | 48 - USAR Systems provided us with one of their excellent USB
55 - Thanks to Intel Corporation for their precious help.
64 - Due to their support to us, Keytronic can be sure that they
83 - Thanks to Y-E Data, Inc. for donating their FlashBuster-U
99 Logitech customers to enjoy support in their favorite
164 - All the people at the USB Implementors Forum for their
|
| /kernel/linux/linux-5.10/Documentation/usb/ |
| D | CREDITS | 48 - USAR Systems provided us with one of their excellent USB
55 - Thanks to Intel Corporation for their precious help.
64 - Due to their support to us, Keytronic can be sure that they
83 - Thanks to Y-E Data, Inc. for donating their FlashBuster-U
99 Logitech customers to enjoy support in their favorite
164 - All the people at the USB Implementors Forum for their
|
12345678910>>...292