| /kernel/linux/linux-4.19/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-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-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-4.19/drivers/regulator/ |
| D | helpers.c | 27 * Regulators that use regmap for their register I/O can set the
28 * enable_reg and enable_mask fields in their descriptor and then use
29 * this as their is_enabled operation, saving some code.
59 * Regulators that use regmap for their register I/O can set the
60 * enable_reg and enable_mask fields in their descriptor and then use
61 * this as their enable() operation, saving some code.
85 * Regulators that use regmap for their register I/O can set the
86 * enable_reg and enable_mask fields in their descriptor and then use
87 * this as their disable() operation, saving some code.
111 * Regulators that use regmap for their register I/O can set the
[all …]
|
| /kernel/linux/linux-4.19/Documentation/blockdev/drbd/ |
| D | data-structure-v9.txt | 26 In this table, horizontally, devices can be accessed from resources by their
28 their volume number. Objects in the vertical direction are connected by double
29 linked lists. There are back pointers from peer_devices to their connections a
30 devices, and from connections and devices to their resource.
33 devices can be accessed by their minor device number via the drbd_devices idr.
37 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-4.19/arch/arm/ |
| D | Kconfig.debug | 95 # These options are only for real kernel hackers who want to get their hands dirty.
126 their output to an UART or USART port on asm9260 based
184 their output to the USART1 port on SAMV7 based
213 their output to the third serial port on these devices.
243 their output to the first serial port on these devices. The
255 their output to the first serial port on these devices.
262 their output to the second serial port on these devices.
270 their output to the CNS3xxx UART0.
278 their output to UART1 serial port on DaVinci DA8XX devices.
286 their output to UART2 serial port on DaVinci DA8XX devices.
[all …]
|
| /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-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-4.19/include/linux/ |
| D | irqchip.h | 19 * the association between their DT compatible string and their
31 * the association between their version and their initialization function.
|
| /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-4.19/Documentation/power/regulator/ |
| D | consumer.txt | 70 Some consumer drivers need to be able to dynamically change their supply
75 Consumers can control their supply voltage by calling :-
100 Some consumer drivers need to be able to dynamically change their supply
105 Consumers can control their supply current limit by calling :-
130 their supply regulator to be more efficient when the consumers operating state
137 Consumer drivers can request a change in their supply regulator operating mode
157 operating mode depending on their operating point. This can be achieved by
182 Regulators use the kernel notifier framework to send event to their interested
|
| /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-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-4.19/Documentation/process/ |
| D | 1.Intro.rst | 8 and the kinds of frustrations that developers and their employers can
61 vendors want to ensure that Linux supports their products well, making
65 other software vendors who base their products on Linux have a clear
68 better suit their needs.
119 learning how to work with the kernel community and get their code into the
167 to implement changes which make the kernel work better for their needs.
194 a result, their distribution is a violation of the GNU General Public
210 will have to upgrade your module separately every time they upgrade their
247 be obtained (or their code removed from the kernel). So, in particular,
254 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-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
|
| /kernel/linux/linux-4.19/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-4.19/Documentation/scsi/ |
| D | BusLogic.txt | 21 collection of bus architectures by virtue of their MultiMaster ASIC technology.
35 analogous to the firmware on the MultiMaster Host Adapters. Thanks to their
45 tune driver performance and error recovery to their particular needs.
58 Mylex has been an excellent company to work with and I highly recommend their
60 opportunity to become a beta test site for their latest MultiMaster product,
63 Mylex received a degree and kind of testing that their own testing group cannot
67 directly with their technical staff, to understand more about the internal
68 workings of their products, and in turn to educate them about the needs and
76 problem and are running Linux, they will not tell you that your use of their
77 products is unsupported. Their latest product marketing literature even states
[all …]
|
| /kernel/linux/linux-5.10/Documentation/mips/ |
| D | ingenic-tcu.rst | 19 different clocks (pclk, ext, rtc), gated, and reclocked, through their TCSR register.
22 format in their register space.
44 - on older SoCs (JZ4740 and below), channel 0 and channel 1 have their
68 drivers access their registers through the same regmap.
|
| /kernel/linux/linux-4.19/Documentation/networking/ |
| D | ipv6.txt | 21 The possible values and their effects are:
43 The possible values and their effects are:
61 The possible values and their effects are:
|
| /kernel/linux/linux-5.10/Documentation/networking/ |
| D | ipv6.rst | 27 The possible values and their effects are:
49 The possible values and their effects are:
67 The possible values and their effects are:
|
| /kernel/linux/linux-4.19/drivers/usb/core/ |
| D | generic.c | 68 * similar errors in their descriptors. If the next test in usb_choose_configuration()
94 * Some hubs have errors in their descriptor, claiming in usb_choose_configuration()
205 /* Normal USB devices suspend through their upstream port. in generic_suspend()
207 * so we have to shut down their downstream HC-to-USB in generic_suspend()
231 /* Normal USB devices resume/reset through their upstream port. in generic_resume()
233 * so we have to start up their downstream HC-to-USB in generic_resume()
|