/linux-5.19.10/Documentation/userspace-api/media/dvb/ |
D | frontend-property-satellite-systems.rst | 6 Properties used on satellite delivery systems 12 DVB-S delivery system 49 DVB-S2 delivery system 71 Turbo code delivery system 82 ISDB-S delivery system
|
D | fe-type-t.rst | 80 used to contain ``fe_type_t`` field to indicate the delivery systems, 83 is deprecated, as it can report just one delivery system, but some 84 devices support multiple delivery systems. Please use 87 On devices that support multiple delivery systems, struct
|
D | frontend-property-cable-systems.rst | 6 Properties used on cable delivery systems 12 DVB-C delivery system 50 DVB-C Annex B delivery system
|
D | frontend-property-terrestrial-systems.rst | 6 Properties used on terrestrial delivery systems 12 DVB-T delivery system 51 DVB-T2 delivery system 95 ISDB-T delivery system 184 ATSC delivery system 209 ATSC-MH delivery system 262 DTMB delivery system
|
D | fe_property_parameters.rst | 51 #. For satellite delivery systems, the frequency is in kHz. 53 #. For cable and terrestrial delivery systems, the frequency is in 56 #. On most delivery systems, the frequency is the center frequency 74 Specifies the frontend modulation type for delivery systems that 83 supported by each delivery system, as currently defined by specs. 114 Should be set only for terrestrial delivery systems. 140 #. On Satellite and Cable delivery systems, the bandwidth depends on 175 Used on cable and satellite delivery systems. 185 Used on cable and satellite delivery systems. 195 Used on satellite delivery systems. [all …]
|
D | dvbproperty.rst | 18 ATSC delivery systems grouped there. The problem is that, as the second 32 with supports all digital TV delivery systems. 43 3. Nowadays, most frontends support multiple delivery systems. 45 the multiple delivery systems supported by a frontend.
|
D | dvb-frontend-parameters.rst | 13 per-system parameters. However, as newer delivery systems required more 19 existing delivery systems, and to add newer delivery systems.
|
D | frontend.rst | 9 The Digital TV frontend API was designed to support three groups of delivery 11 delivery systems are supported:
|
D | legacy_dvb_apis.rst | 11 The DVBv3 frontend API has issues with new delivery systems, including
|
D | frontend-stat-properties.rst | 12 For most delivery systems, ``dtv_property.stat.len`` will be 1 if the 16 It should be noted, however, that new OFDM delivery systems like ISDB 22 So, in order to be consistent with other delivery systems, the first
|
D | fe-get-property.rst | 40 depends on the delivery system and on the device:
|
/linux-5.19.10/arch/ia64/kernel/ |
D | iosapic.c | 552 register_intr (unsigned int gsi, int irq, unsigned char delivery, in register_intr() argument 597 iosapic_intr_info[irq].dmode = delivery; in register_intr() 862 unsigned char delivery; in iosapic_register_platform_intr() local 875 delivery = IOSAPIC_PMI; in iosapic_register_platform_intr() 882 delivery = IOSAPIC_INIT; in iosapic_register_platform_intr() 887 delivery = IOSAPIC_FIXED; in iosapic_register_platform_intr() 896 register_intr(gsi, irq, delivery, polarity, trigger); in iosapic_register_platform_intr()
|
/linux-5.19.10/net/sctp/ |
D | Kconfig | 26 -- sequenced delivery of user messages within multiple streams, 27 with an option for order-of-arrival delivery of individual user
|
/linux-5.19.10/Documentation/ia64/ |
D | irq-redir.rst | 24 Set the delivery mode of interrupt 41 to fixed and route the 30 delivery mode (redirectable)::
|
/linux-5.19.10/net/rds/ |
D | Kconfig | 8 sequenced delivery of datagrams over Infiniband or TCP.
|
/linux-5.19.10/Documentation/ABI/testing/ |
D | sysfs-class-fc_host | 21 These files contain the number of delivery related errors
|
D | sysfs-class-typec | 208 of showing the result of Discover Identity USB power delivery 210 delivery is supported, for example when USB power delivery 276 of showing the result of Discover Identity USB power delivery 278 delivery is supported, for example when USB power delivery
|
D | sysfs-class-fc_remote_ports | 21 These files contain the number of delivery related errors
|
/linux-5.19.10/arch/arm64/boot/dts/qcom/ |
D | msm8996-v3.0.dtsi | 15 * when it comes to voltage delivery to.. once again
|
/linux-5.19.10/Documentation/virt/kvm/x86/ |
D | msr.rst | 215 present in CPUID. Bit 3 enables interrupt based delivery of 'page ready' 220 #PF exception. During delivery of these events APF CR2 register contains 245 ready' APF delivery needs to be written to before enabling APF mechanism 251 bit 3 (interrupt based delivery) is not set APF events are not delivered. 360 Bits 0-7: APIC vector for delivery of 'page ready' APF events. 363 Interrupt vector for asynchnonous 'page ready' notifications delivery.
|
/linux-5.19.10/Documentation/devicetree/bindings/usb/ |
D | richtek,rt1719.yaml | 16 delivery protocol to allow up to 100W of power. The BMC PD block enables full
|
/linux-5.19.10/Documentation/devicetree/bindings/hwmon/ |
D | maxim,max20730.yaml | 18 compact, high efficiency power-delivery solutions with high-precision
|
/linux-5.19.10/Documentation/devicetree/bindings/connector/ |
D | usb-connector.yaml | 99 delivery support. 114 description: Set this property if the Type-C connector has no power delivery support. 118 # delivery support. 309 # power delivery support and enables drp.
|
/linux-5.19.10/Documentation/devicetree/bindings/arm/ |
D | microchip,sparx5.yaml | 18 enabling delivery of differentiated services, and security through
|
/linux-5.19.10/security/smack/ |
D | Kconfig | 51 receiving process. If this option is selected, the delivery
|