Searched full:their (Results 1 – 25 of 3881) sorted by relevance
12345678910>>...156
| /Linux-v6.1/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
|
| /Linux-v6.1/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 …]
|
| /Linux-v6.1/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
|
| /Linux-v6.1/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
|
| /Linux-v6.1/include/drm/ |
| D | drm_gem_shmem_helper.h | 151 * should use it as their &drm_gem_object_funcs.free handler.
167 * use this function as their &drm_gem_object_funcs.print_info handler.
182 * use it as their &drm_gem_object_funcs.pin handler.
196 * use it as their &drm_gem_object_funcs.unpin handler.
210 * use it as their &drm_gem_object_funcs.get_sg_table handler.
228 * use it as their &drm_gem_object_funcs.vmap handler.
247 * use it as their &drm_gem_object_funcs.vunmap handler.
263 * 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.
181 * Drivers that come with their own implementation of
221 * Drivers that come with their own implementation of
|
| D | drm_modeset_helper_vtables.h | 39 * they wish. Drivers are not forced to use this code in their
85 * running. Most drivers ended up implementing this by calling their
100 * drivers ended up implementing this by calling their @dpms hook with
227 * move all their CRTC setup into the @atomic_enable callback.
276 * been shut off already using their own
278 * simple drivers can just add their own hooks and call it from this
408 * hook. If that sequence is too simple drivers can just add their own
429 * been shut off already using their own
431 * simple drivers can just add their own hooks and call it from this
611 * is running. Most drivers ended up implementing this by calling their
[all …]
|
| /Linux-v6.1/arch/arm/ |
| D | Kconfig.debug | 113 # These options are only for real kernel hackers who want to get their hands dirty.
144 their output to an UART or USART port on asm9260 based
202 their output to the USART1 port on SAMV7 based
259 their output to the third serial port on these devices.
289 their output to the first serial port on these devices. The
301 their output to the first serial port on these devices.
308 their output to the second serial port on these devices.
316 their output to the CNS3xxx UART0.
324 their output to UART1 serial port on DaVinci DA8XX devices.
332 their output to UART2 serial port on DaVinci DA8XX devices.
[all …]
|
| /Linux-v6.1/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 …]
|
| /Linux-v6.1/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
|
| /Linux-v6.1/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
|
| D | stable-api-nonsense.rst | 47 that describes kernel drivers that do not have their source code
125 running almost all USB devices at their maximum speed possible.
132 which have had to maintain their older USB interfaces over time. This
143 their work on their own time, asking programmers to do extra work for no
203 Robert Love, and Nishanth Aravamudan for their review and comments on
|
| D | 2.Process.rst | 67 As fixes make their way into the mainline, the patch rate will slow over
112 than one development cycle past their initial release. So, for example, the
130 long term kernel versions and their maintainers:
180 your patch may not be their highest priority. If your patch is
204 One of the largest mistakes made by kernel developers (or their employers)
228 Subsystem maintainers each manage their own version of the kernel source
236 the patches they have selected for merging from their repositories. If
266 want access to the changes in their integrated form before all of those
306 their way into linux-next some time before the merge window opens.
313 many sub-directories for drivers or filesystems that are on their way to
[all …]
|
| /Linux-v6.1/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.
|
| /Linux-v6.1/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
|
| /Linux-v6.1/Documentation/filesystems/ |
| D | idmappings.rst | 204 the same kernel id in their kernel idmapsets. For example, consider the
228 this question both idmappings need to contain the same kernel id in their
279 this question both idmappings need to contain the same userspace id in their
579 to use their home directories on different machines where they are assigned
581 on their machine at home and all files in their home directory will usually be
583 ``u1125``. This makes it rather difficult to interact with their home directory
584 on their work machine.
589 user switches from their home to their work machine. For really large sets of
879 Consider our previous example where a user has their home directory on portable
880 storage. At home they have id ``u1000`` and all files in their home directory
[all …]
|
| /Linux-v6.1/Documentation/devicetree/bindings/opp/ |
| D | opp-v2-base.yaml | 30 their DVFS state together, i.e. they share clock/voltage/current lines.
40 Their name isn't significant but their phandle can be used to reference an
55 to relate the values to their clocks or the order in which the clocks
73 relate the values to their power supplies or the order in which the supplies
100 values to their power supplies or the order in which the supplies need
115 values to their power supplies or the order in which the supplies need
|
| /Linux-v6.1/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.
|
| /Linux-v6.1/Documentation/scsi/ |
| D | BusLogic.rst | 29 collection of bus architectures by virtue of their MultiMaster ASIC technology.
43 analogous to the firmware on the MultiMaster Host Adapters. Thanks to their
53 tune driver performance and error recovery to their particular needs.
66 Mylex has been an excellent company to work with and I highly recommend their
68 opportunity to become a beta test site for their latest MultiMaster product,
71 Mylex received a degree and kind of testing that their own testing group cannot
75 directly with their technical staff, to understand more about the internal
76 workings of their products, and in turn to educate them about the needs and
84 problem and are running Linux, they will not tell you that your use of their
85 products is unsupported. Their latest product marketing literature even states
[all …]
|
| /Linux-v6.1/Documentation/driver-api/ |
| D | regulator.rst | 37 can enable and disable their output and some can also control their
68 When requesting regulators consumers use symbolic names for their
92 Some consumer devices may need to be able to dynamically configure their
94 operating voltage for their cards. This may be done while the regulator
|
| /Linux-v6.1/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:
|
| /Linux-v6.1/LICENSES/deprecated/ |
| D | GFDL-1.1 | 39 credit for their work, while not being considered responsible for
219 unaltered in their text and in their titles. Section numbers
229 of these sections as invariant. To do this, add their titles to the
250 give permission to use their names for publicity for or to assert or
301 with the Document, on account of their being thus compiled, if they
316 permission from their copyright holders, but you may include
332 License will not have their licenses terminated so long as such
364 with the Invariant Sections being LIST THEIR TITLES, with the
377 to permit their use in free software.
|
| /Linux-v6.1/Documentation/riscv/ |
| D | patch-acceptance.rst | 24 course, maintain their own Linux kernel trees that contain code for
28 their own custom extensions. These custom extensions aren't required
34 (Implementors, may, of course, maintain their own Linux kernel trees
|
| /Linux-v6.1/Documentation/devicetree/bindings/mfd/ |
| D | max77620.txt | 16 - #interrupt-cells: is <2> and their usage is compliant to the 2 cells
26 Optional subnodes and their properties:
64 and their child for FPS specific. The child node name for FPS are "fps0",
68 regulators, GPIOs and 32kHz clocks are provided in their respective
130 under their respective sub-system directories.
|
12345678910>>...156
