/Linux-v5.4/include/linux/ |
D | rpmsg.h | 147 /* This shouldn't be possible */ in unregister_rpmsg_device() 154 /* This shouldn't be possible */ in __register_rpmsg_driver() 162 /* This shouldn't be possible */ in unregister_rpmsg_driver() 168 /* This shouldn't be possible */ in rpmsg_destroy_ept() 177 /* This shouldn't be possible */ in rpmsg_create_ept() 185 /* This shouldn't be possible */ in rpmsg_send() 194 /* This shouldn't be possible */ in rpmsg_sendto() 204 /* This shouldn't be possible */ in rpmsg_send_offchannel() 212 /* This shouldn't be possible */ in rpmsg_trysend() 221 /* This shouldn't be possible */ in rpmsg_trysendto() [all …]
|
D | isa.h | 63 * max_num_isa_dev() - Maximum possible number registered of an ISA device 66 * The highest base address possible for an ISA device is 0x3FF; this results in 67 * 1024 possible base addresses. Dividing the number of possible base addresses
|
/Linux-v5.4/Documentation/media/uapi/v4l/ |
D | ext-ctrls-flash.rst | 69 to the flash controller. Setting this control may not be possible in 101 this is a sensor, which makes it possible to synchronises the 110 control may not be possible in presence of some faults. See 127 if possible. 132 if possible. Setting this control may not be possible in presence of 138 possible. 147 and returns the chip to a usable state if possible. 178 which strobing the flash at full current will not be possible.The 191 after strobe during which another strobe will not be possible. This
|
D | vidioc-g-selection.rst | 80 choose a crop/compose rectangle as close as possible to the requested 96 capture/output window or TV display. The closest possible values of 106 3. Keep center of adjusted rectangle as close as possible to the 109 4. Keep width and height as close as possible to original ones. 111 5. Keep horizontal and vertical offset as close as possible to original 191 It is not possible to adjust struct :c:type:`v4l2_rect` 199 It is not possible to apply change of the selection rectangle at the
|
D | ext-ctrls-codec.rst | 103 of possible VBI formats depends on the driver. The currently defined 129 MPEG Audio sampling frequency. Possible values are: 153 streams. Possible values are: 180 MPEG-1/2 Layer I bitrate. Possible values are: 225 MPEG-1/2 Layer II bitrate. Possible values are: 270 MPEG-1/2 Layer III bitrate. Possible values are: 318 AC-3 bitrate. Possible values are: 373 MPEG Audio mode. Possible values are: 400 in stereo. Layer III is not (yet) supported. Possible values are: 425 Audio Emphasis. Possible values are: [all …]
|
/Linux-v5.4/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:
|
/Linux-v5.4/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)
|
/Linux-v5.4/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
|
/Linux-v5.4/Documentation/scsi/ |
D | link_power_management_policy.txt | 2 There are 3 possible options: 7 least possible power when possible. This may 16 when possible, but do not enter the lowest power
|
D | aic7xxx.txt | 44 for all possible target/lun combinations. 164 and our per-softc lock. This was only possible on RH9, 200 Possible Values: This option is a flag 205 Possible Values: 0x0000 = no debugging, 0xffff = full debugging 217 Possible Values: This option is a toggle 230 Possible Values: This option is a toggle 236 Possible Values: This option is a flag 241 Possible Values: This option is a flag 247 Possible Values: This option is a flag 253 Possible Values: This option is a flag [all …]
|
D | aic79xx.txt | 111 possible. 225 Possible Values: This option is a flag 233 Possible Values: 0x0000 = no debugging, 0xffff = full debugging 239 Possible Values: This option is a flag 244 Possible Values: This option is a flag 250 Possible Values: This option is a flag 256 Possible Values: This option is a flag 264 Possible Values: 1 - 253 286 Possible Values: 1 - 253 311 Possible Values: 0x0000 - 0xffff [all …]
|
/Linux-v5.4/Documentation/media/uapi/dvb/ |
D | frontend-stat-properties.rst | 46 frontend, but it was not possible to collect it (could be a 68 Possible scales for this metric are: 87 Possible scales for this metric are: 118 Possible scales for this metric are: 146 Possible scales for this metric are: 175 Possible scales for this metric are: 203 Possible scales for this metric are: 224 Possible scales for this metric are: 246 Possible scales for this metric are:
|
D | fe_property_parameters.rst | 86 Most of the digital TV standards offers more than one possible 123 Possible values: ``1712000``, ``5000000``, ``6000000``, ``7000000``, 127 Terrestrial Standard Possible values for bandwidth 295 Possible values: 0, 1, -1 (AUTO) 309 Possible values: 0, 1, -1 (AUTO) 346 Possible values: 0 .. 41, -1 (AUTO) 362 Possible values: 0 .. ``DTV_ISDBT_SB_SEGMENT_COUNT`` - 1 379 Possible values: 1 .. 13 445 Possible values are: ``FEC_AUTO``, ``FEC_1_2``, ``FEC_2_3``, ``FEC_3_4``, 459 Possible values are: ``QAM_AUTO``, ``QPSK``, ``QAM_16``, ``QAM_64``, ``DQPSK`` [all …]
|
/Linux-v5.4/Documentation/networking/ |
D | mpls-sysctl.txt | 5 possible to configure forwarding for label values equal to or 9 is possible and expected as the platform labels are locally 19 Possible values: 0 - 1048575 38 Possible values: 1 - 255
|
D | ipv6.txt | 21 The possible values and their effects are: 32 it will not be possible to open an IPv6 socket. 43 The possible values and their effects are: 61 The possible values and their effects are:
|
/Linux-v5.4/Documentation/devicetree/bindings/phy/ |
D | brcm,brcmstb-usb-phy.txt | 11 the type of the PHY. Possible values are: 19 Possible values are: 0 (Don't invert), 1 (Invert) 21 Possible values are: 0 (Don't invert), 1 (Invert) 26 Possible values are: "host", "peripheral ", "drd" or "typec-pd"
|
/Linux-v5.4/drivers/acpi/ |
D | pci_link.c | 63 u32 possible[ACPI_PCI_LINK_MAX_POSSIBLE]; member 84 * set context (link) possible list from resource list 113 link->irq.possible[i] = p->interrupts[i]; in acpi_pci_link_check_possible() 139 link->irq.possible[i] = p->interrupts[i]; in acpi_pci_link_check_possible() 168 "Found %d possible IRQs\n", in acpi_pci_link_get_possible() 417 * Note that PCI IRQ routers have a list of possible IRQs, 475 if (link->irq.possible[i] == irq) in acpi_irq_pci_sharing_penalty() 507 * reflect the possible and active irqs in the penalty table -- in acpi_irq_penalty_init() 516 if (link->irq.possible[i] < ACPI_MAX_ISA_IRQS) in acpi_irq_penalty_init() 518 possible[i]] += in acpi_irq_penalty_init() [all …]
|
/Linux-v5.4/Documentation/devicetree/bindings/clock/ |
D | ux500.txt | 19 wants to use, possible values are 1, 2, 3, 5, 6. The second 21 possible values are 0 thru 31. 25 wants to use, possible values are 1, 2, 3, 5, 6. The second 27 possible values are 0 thru 31.
|
/Linux-v5.4/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 */
|
/Linux-v5.4/Documentation/ABI/testing/ |
D | sysfs-class-scsi_host | 23 stack for a performance advantage when possible. A value of 39 There are four possible options: 42 least possible power when possible. This may sacrifice some 51 when possible, but do not enter the lowest power state, thus
|
D | sysfs-class-net | 6 Indicates the name assignment type. Possible values are: 17 Indicates the address assignment type. Possible values are: 117 Indicates whether the interface is in dormant state. Possible 132 Indicates the interface latest or current duplex value. Possible 146 include/uapi/linux/if.h for a list of all possible values and 185 to determine the interface usability. Possible values: 216 Possible values are: 263 include/uapi/linux/if_arp.h for all possible values.
|
D | sysfs-class-net-grcan | 9 Possible values: 0 or 1. See the GRCAN chapter of the GRLIB IP 21 Possible values: 0 or 1. See the GRCAN chapter of the GRLIB IP 31 Configuration of which physical interface to be used. Possible
|
/Linux-v5.4/Documentation/devicetree/bindings/pinctrl/ |
D | fsl,imx27-pinctrl.txt | 20 Possible values: 27 Possible values: 36 Possible values: 45 Possible values:
|
/Linux-v5.4/Documentation/filesystems/ |
D | virtiofs.rst | 20 Although it is possible to use existing network file systems for some of these 27 possible with network file systems. 54 FUSE client may choose which request to transfer, making it possible to 56 it is not possible to change the order of requests that have been enqueued.
|
/Linux-v5.4/drivers/staging/iio/Documentation/ |
D | ring.txt | 23 as much buffer functionality as possible. Note almost all of these 27 If possible, push data to the buffer. 30 If possible, get the most recent scan from the buffer (without removal).
|