| /kernel/linux/linux-6.6/include/linux/ |
| D | rpmsg.h | 218 /* This shouldn't be possible */ in rpmsg_unregister_device()
227 /* This shouldn't be possible */ in __register_rpmsg_driver()
235 /* This shouldn't be possible */ in unregister_rpmsg_driver()
241 /* This shouldn't be possible */ in rpmsg_destroy_ept()
250 /* This shouldn't be possible */ in rpmsg_create_ept()
258 /* This shouldn't be possible */ in rpmsg_send()
267 /* This shouldn't be possible */ in rpmsg_sendto()
277 /* This shouldn't be possible */ in rpmsg_send_offchannel()
285 /* This shouldn't be possible */ in rpmsg_trysend()
294 /* This shouldn't be possible */ in rpmsg_trysendto()
[all …]
|
| /kernel/linux/linux-5.10/include/linux/ |
| D | rpmsg.h | 157 /* This shouldn't be possible */ in unregister_rpmsg_device()
164 /* This shouldn't be possible */ in __register_rpmsg_driver()
172 /* This shouldn't be possible */ in unregister_rpmsg_driver()
178 /* This shouldn't be possible */ in rpmsg_destroy_ept()
187 /* This shouldn't be possible */ in rpmsg_create_ept()
195 /* This shouldn't be possible */ in rpmsg_send()
204 /* This shouldn't be possible */ in rpmsg_sendto()
214 /* This shouldn't be possible */ in rpmsg_send_offchannel()
222 /* This shouldn't be possible */ in rpmsg_trysend()
231 /* This shouldn't be possible */ in rpmsg_trysendto()
[all …]
|
| /kernel/linux/linux-5.10/Documentation/userspace-api/media/v4l/ |
| D | ext-ctrls-flash.rst | 62 to the flash controller. Setting this control may not be possible in
94 this is a sensor, which makes it possible to synchronise the
103 control may not be possible in presence of some faults. See
120 if possible.
125 if possible. Setting this control may not be possible in presence of
131 possible.
140 and returns the chip to a usable state if possible.
171 which strobing the flash at full current will not be possible.The
184 after strobe during which another strobe will not be possible. This
|
| /kernel/linux/linux-6.6/Documentation/userspace-api/media/v4l/ |
| D | ext-ctrls-flash.rst | 62 to the flash controller. Setting this control may not be possible in
97 this is a sensor, which makes it possible to synchronise the
106 control may not be possible in presence of some faults. See
123 if possible.
128 if possible. Setting this control may not be possible in presence of
134 possible.
143 and returns the chip to a usable state if possible.
174 which strobing the flash at full current will not be possible.The
187 after strobe during which another strobe will not be possible. This
|
| D | ext-ctrls-codec.rst | 96 of possible VBI formats depends on the driver. The currently defined
122 MPEG Audio sampling frequency. Possible values are:
146 streams. Possible values are:
173 MPEG-1/2 Layer I bitrate. Possible values are:
218 MPEG-1/2 Layer II bitrate. Possible values are:
263 MPEG-1/2 Layer III bitrate. Possible values are:
311 AC-3 bitrate. Possible values are:
366 MPEG Audio mode. Possible values are:
393 in stereo. Layer III is not (yet) supported. Possible values are:
418 Audio Emphasis. Possible values are:
[all …]
|
| /kernel/linux/linux-6.6/Documentation/ABI/testing/ |
| D | sysfs-driver-ccp | 18 Possible values:
29 Possible values:
40 Possible values:
51 Possible values:
63 Possible values:
74 Possible values:
85 Possible values:
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/power/ |
| D | rockchip-io-domain.txt | 56 Possible supplies for PX30:
65 Possible supplies for PX30 pmu-domains:
69 Possible supplies for rk3188:
80 Possible supplies for rk3228:
86 Possible supplies for rk3288:
98 Possible supplies for rk3368:
107 Possible supplies for rk3368 pmu-domains:
111 Possible supplies for rk3399:
117 Possible supplies for rk3399 pmu-domains:
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/clock/ |
| D | stericsson,u8500-clks.yaml | 52 which PRCC block the consumer wants to use, possible values are 1, 2, 3,
54 wants, possible values are 0 thru 31.
66 block the consumer wants to use, possible values are 1, 2, 3, 5, 6. The
67 second cell indicates which clock inside the PRCC block it wants, possible
80 which PRCC block the consumer wants to use, possible values are 1, 2, 3
82 it wants to control, possible values are 0 thru 31.
122 possible values are 0 (CLKOUT1) and 1 (CLKOUT2).
124 possible values are 0 thru 7, see the defines for the different
|
| /kernel/linux/linux-6.6/tools/memory-model/ |
| D | lock.cat | 83 let all-possible-rfe-lf =
85 * Given an LF event r, compute the possible rfe edges for that event
89 let possible-rfe-lf r =
93 in map possible-rfe-lf (LF \ range(rfi-lf))
96 with rfe-lf from cross(all-possible-rfe-lf)
109 let all-possible-rf-ru =
110 let possible-rf-ru r =
114 in map possible-rf-ru RU
117 with rf-ru from cross(all-possible-rf-ru)
|
| /kernel/linux/linux-5.10/tools/memory-model/ |
| D | lock.cat | 83 let all-possible-rfe-lf =
85 * Given an LF event r, compute the possible rfe edges for that event
89 let possible-rfe-lf r =
93 in map possible-rfe-lf (LF \ range(rfi-lf))
96 with rfe-lf from cross(all-possible-rfe-lf)
109 let all-possible-rfe-ru =
110 let possible-rfe-ru r =
113 in map possible-rfe-ru RU
116 with rfe-ru from cross(all-possible-rfe-ru)
|
| /kernel/linux/linux-5.10/Documentation/kbuild/ |
| D | Kconfig.recursion-issue-01 | 13 # * What values are possible for CORE?
16 # that are possible for CORE. So for example if CORE_BELL_A_ADVANCED is 'y',
30 # what values are possible for CORE we ended up needing to address questions
31 # regarding possible values of CORE itself again. Answering the original
32 # question of what are the possible values of CORE would make the kconfig
|
| /kernel/linux/linux-6.6/Documentation/kbuild/ |
| D | Kconfig.recursion-issue-01 | 13 # * What values are possible for CORE?
16 # that are possible for CORE. So for example if CORE_BELL_A_ADVANCED is 'y',
30 # what values are possible for CORE we ended up needing to address questions
31 # regarding possible values of CORE itself again. Answering the original
32 # question of what are the possible values of CORE would make the kconfig
|
| /kernel/linux/linux-6.6/Documentation/userspace-api/media/dvb/ |
| D | frontend-stat-properties.rst | 39 frontend, but it was not possible to collect it (could be a
61 Possible scales for this metric are:
80 Possible scales for this metric are:
111 Possible scales for this metric are:
139 Possible scales for this metric are:
168 Possible scales for this metric are:
196 Possible scales for this metric are:
217 Possible scales for this metric are:
239 Possible scales for this metric are:
|
| D | fe_property_parameters.rst | 79 Most of the digital TV standards offers more than one possible
121 Possible values: ``1712000``, ``5000000``, ``6000000``, ``7000000``,
125 Terrestrial Standard Possible values for bandwidth
293 Possible values: 0, 1, -1 (AUTO)
307 Possible values: 0, 1, -1 (AUTO)
344 Possible values: 0 .. 41, -1 (AUTO)
360 Possible values: 0 .. ``DTV_ISDBT_SB_SEGMENT_COUNT`` - 1
377 Possible values: 1 .. 13
443 Possible values are: ``FEC_AUTO``, ``FEC_1_2``, ``FEC_2_3``, ``FEC_3_4``,
457 Possible values are: ``QAM_AUTO``, ``QPSK``, ``QAM_16``, ``QAM_64``, ``DQPSK``
[all …]
|
| /kernel/linux/linux-5.10/Documentation/userspace-api/media/dvb/ |
| D | frontend-stat-properties.rst | 39 frontend, but it was not possible to collect it (could be a
61 Possible scales for this metric are:
80 Possible scales for this metric are:
111 Possible scales for this metric are:
139 Possible scales for this metric are:
168 Possible scales for this metric are:
196 Possible scales for this metric are:
217 Possible scales for this metric are:
239 Possible scales for this metric are:
|
| D | fe_property_parameters.rst | 79 Most of the digital TV standards offers more than one possible
116 Possible values: ``1712000``, ``5000000``, ``6000000``, ``7000000``,
120 Terrestrial Standard Possible values for bandwidth
288 Possible values: 0, 1, -1 (AUTO)
302 Possible values: 0, 1, -1 (AUTO)
339 Possible values: 0 .. 41, -1 (AUTO)
355 Possible values: 0 .. ``DTV_ISDBT_SB_SEGMENT_COUNT`` - 1
372 Possible values: 1 .. 13
438 Possible values are: ``FEC_AUTO``, ``FEC_1_2``, ``FEC_2_3``, ``FEC_3_4``,
452 Possible values are: ``QAM_AUTO``, ``QPSK``, ``QAM_16``, ``QAM_64``, ``DQPSK``
[all …]
|
| /kernel/linux/linux-6.6/drivers/acpi/ |
| D | pci_link.c | 61 u32 possible[ACPI_PCI_LINK_MAX_POSSIBLE]; member
82 * set context (link) possible list from resource list
112 link->irq.possible[i] = p->interrupts[i]; in acpi_pci_link_check_possible()
138 link->irq.possible[i] = p->interrupts[i]; in acpi_pci_link_check_possible()
167 acpi_handle_debug(handle, "Found %d possible IRQs\n", in acpi_pci_link_get_possible()
411 * Note that PCI IRQ routers have a list of possible IRQs,
469 if (link->irq.possible[i] == irq) in acpi_irq_pci_sharing_penalty()
501 * reflect the possible and active irqs in the penalty table -- in acpi_irq_penalty_init()
510 if (link->irq.possible[i] < ACPI_MAX_ISA_IRQS) in acpi_irq_penalty_init()
512 possible[i]] += in acpi_irq_penalty_init()
[all …]
|
| /kernel/linux/linux-6.6/Documentation/networking/ |
| D | mpls-sysctl.rst | 12 possible to configure forwarding for label values equal to or
16 is possible and expected as the platform labels are locally
26 Possible values: 0 - 1048575
46 Possible values: 1 - 255
|
| D | ipv6.rst | 27 The possible values and their effects are:
38 it will not be possible to open an IPv6 socket.
49 The possible values and their effects are:
67 The possible values and their effects are:
|
| /kernel/linux/linux-5.10/Documentation/networking/ |
| D | mpls-sysctl.rst | 12 possible to configure forwarding for label values equal to or
16 is possible and expected as the platform labels are locally
26 Possible values: 0 - 1048575
46 Possible values: 1 - 255
|
| D | ipv6.rst | 27 The possible values and their effects are:
38 it will not be possible to open an IPv6 socket.
49 The possible values and their effects are:
67 The possible values and their effects are:
|
| /kernel/linux/linux-6.6/rust/alloc/ |
| D | README.md | 8 Please note that these files should be kept as close as possible to
24 upstream as possible and avoid as much divergence as possible, which
28 in-tree that would be as small and as close as possible to upstream.
|
| /kernel/linux/linux-6.6/include/linux/mtd/ |
| D | pfow.h | 38 /* command execution register, the only possible value is 0x01 */
48 /* They are possible values of PFOW command code register */
60 /* Defines possible value of PFOW command execution register */
63 /* Defines possible value of PFOW program/erase suspend register */
66 /* Possible values of PFOW device status register */
97 /* The superset of all possible error bits in DSR */
|
| /kernel/linux/linux-5.10/include/linux/mtd/ |
| D | pfow.h | 38 /* command execution register, the only possible value is 0x01 */
48 /* They are possible values of PFOW command code register */
60 /* Defines possible value of PFOW command execution register */
63 /* Defines possible value of PFOW program/erase suspend register */
66 /* Possible values of PFOW device status register */
97 /* The superset of all possible error bits in DSR */
|
| /kernel/linux/linux-5.10/drivers/acpi/ |
| D | pci_link.c | 61 u32 possible[ACPI_PCI_LINK_MAX_POSSIBLE]; member
82 * set context (link) possible list from resource list
111 link->irq.possible[i] = p->interrupts[i]; in acpi_pci_link_check_possible()
137 link->irq.possible[i] = p->interrupts[i]; in acpi_pci_link_check_possible()
166 "Found %d possible IRQs\n", in acpi_pci_link_get_possible()
415 * Note that PCI IRQ routers have a list of possible IRQs,
473 if (link->irq.possible[i] == irq) in acpi_irq_pci_sharing_penalty()
505 * reflect the possible and active irqs in the penalty table -- in acpi_irq_penalty_init()
514 if (link->irq.possible[i] < ACPI_MAX_ISA_IRQS) in acpi_irq_penalty_init()
516 possible[i]] += in acpi_irq_penalty_init()
[all …]
|