| /linux/drivers/clk/qcom/ |
| H A 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/Documentation/process/ |
| H A 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
|
| H A 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
|
| H A 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
|
| H A D | embargoed-hardware-issues.rst | 66 confidentiality by their employment contract. Linux Foundation IT
149 via their employer, they cannot enter individual non-disclosure agreements
150 in their role as Linux kernel developers. They will, however, agree to
209 and the disclosing party is requested to acknowledge their participation.
229 To allow the affected silicon vendors to work with their internal teams and
237 have and maintain their own documented security process for any
238 patches shared with their response team that is consistent with
242 their industry partners and to their internal teams under the
265 required for all involved parties to develop, test, and prepare their
|
| /linux/Documentation/admin-guide/blockdev/drbd/ |
| H A 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/include/drm/ |
| H A D | drm_gem_shmem_helper.h | 142 * should use it as their &drm_gem_object_funcs.free handler.
158 * use this function as their &drm_gem_object_funcs.print_info handler.
173 * use it as their &drm_gem_object_funcs.pin handler.
187 * use it as their &drm_gem_object_funcs.unpin handler.
201 * use it as their &drm_gem_object_funcs.get_sg_table handler.
219 * use it as their &drm_gem_object_funcs.vmap handler.
238 * use it as their &drm_gem_object_funcs.vunmap handler.
254 * use it as their &drm_gem_object_funcs.mmap handler.
|
| H A 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
|
| /linux/drivers/media/test-drivers/vidtv/ |
| H A 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/drivers/video/fbdev/core/ |
| H A D | Kconfig | 49 filling. This is used by drivers that don't provide their own
57 This is used by drivers that don't provide their own (accelerated)
65 blitting. This is used by drivers that don't provide their own
81 filling. This is used by drivers that don't provide their own
89 This is used by drivers that don't provide their own (accelerated)
97 blitting. This is used by drivers that don't provide their own
|
| /linux/Documentation/networking/devlink/ |
| H A 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/Documentation/power/regulator/ |
| H A 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/fs/bcachefs/ |
| H A D | mean_and_variance.c | 65 * @s: mean and variance number of samples and their sums
94 * @s: mean and variance number of samples and their sums
104 * @s: mean and variance number of samples and their sums
137 * @s: mean and variance number of samples and their sums
149 * @s: mean and variance number of samples and their sums
162 * @s: mean and variance number of samples and their sums
|
| /linux/arch/arm/ |
| H A D | Kconfig.debug | 110 # These options are only for real kernel hackers who want to get their hands dirty.
141 their output to an UART or USART port on asm9260 based
199 their output to the USART1 port on SAMV7 based
256 their output to the third serial port on these devices.
286 their output to the first serial port on these devices. The
298 their output to the first serial port on these devices.
305 their output to the second serial port on these devices.
313 their output to UART1 serial port on DaVinci DA8XX devices.
321 their output to UART2 serial port on DaVinci DA8XX devices.
328 their output to the serial port in the DC21285 (Footbridge).
[all …]
|
| /linux/include/linux/ |
| H A D | irqchip.h | 28 * the association between their DT compatible string and their
67 * the association between their version and their initialization function.
|
| /linux/Documentation/usb/ |
| H A 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/Documentation/filesystems/ |
| H A D | idmappings.rst | 205 the same kernel id in their kernel idmapsets. For example, consider the
229 this question both idmappings need to contain the same kernel id in their
280 this question both idmappings need to contain the same userspace id in their
591 to use their home directories on different machines where they are assigned
593 on their machine at home and all files in their home directory will usually be
595 ``u1125``. This makes it rather difficult to interact with their home directory
596 on their work machine.
601 user switches from their home to their work machine. For really large sets of
958 Consider our previous example where a user has their home directory on portable
959 storage. At home they have id ``u1000`` and all files in their home directory
[all …]
|
| /linux/Documentation/devicetree/bindings/opp/ |
| H A 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
71 relate the values to their power supplies or the order in which the supplies
98 values to their power supplies or the order in which the supplies need
113 values to their power supplies or the order in which the supplies need
|
| /linux/Documentation/scsi/ |
| H A 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/Documentation/arch/mips/ |
| H A 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/LICENSES/deprecated/ |
| H A 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/Documentation/driver-api/ |
| H A 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/Documentation/networking/ |
| H A 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/Documentation/devicetree/bindings/mfd/ |
| H A 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.
|
| /linux/kernel/rcu/ |
| H A D | sync.c | 51 * readers back onto their fastpaths (after a grace period). If both
55 * can again use their fastpaths.
97 * tells readers to stay off their fastpaths. A later call to
147 * now allow readers to make use of their fastpaths after a grace period
150 * they can once again use their fastpaths.
|