Home
last modified time | relevance | path

Searched full:numbering (Results 1 – 25 of 202) sorted by relevance

123456789

/Linux-v5.10/Documentation/iio/
Dep93xx_adc.rst12 2. Channel numbering
15 Numbering scheme for channels 0..4 is defined in EP9301 and EP9302 datasheets.
16 EP9307, EP9312 and EP9312 have 3 channels more (total 8), but the numbering is
/Linux-v5.10/Documentation/devicetree/bindings/firmware/
Dnvidia,tegra186-bpmp.txt52 The BPMP firmware defines no single global name-/numbering-space for such
53 services. Put another way, the numbering scheme for I2C buses is distinct from
54 the numbering scheme for any other service the BPMP may provide (e.g. a future
/Linux-v5.10/kernel/irq/
DKconfig117 bool "Support sparse irq numbering" if MAY_HAVE_SPARSE_IRQ
120 Sparse irq numbering is useful for distro kernels that want
/Linux-v5.10/arch/alpha/include/uapi/asm/
Dioctl.h6 * The original linux ioctl numbering scheme was just a general
11 * ioctl numbering, and also trying to be compatible with OSF/1 in
/Linux-v5.10/include/uapi/linux/
Disst_if.h44 * Used to convert from Linux logical CPU to PUNIT CPU numbering scheme.
45 * The PUNIT CPU number is different than APIC ID based CPU numbering.
/Linux-v5.10/arch/x86/include/asm/
Dpci-functions.h3 * PCI BIOS function numbering for conventional PCI BIOS
/Linux-v5.10/Documentation/devicetree/bindings/sound/
Deukrea-tlv320.txt15 Note: The AUDMUX port numbering should start at 1, which is consistent with
Dimx-audio-sgtl5000.txt39 Note: The AUDMUX port numbering should start at 1, which is consistent with
Dimx-audio-es8328.txt37 Note: The AUDMUX port numbering should start at 1, which is consistent with
/Linux-v5.10/Documentation/userspace-api/media/v4l/
Ddev-raw-vbi.rst143 Don't forget that ITU line numbering starts at 1, not 0. VBI input
232 **Figure 4.2. ITU-R 525 line numbering (M/NTSC and M/PAL)**
240 **Figure 4.3. ITU-R 625 line numbering**
/Linux-v5.10/Documentation/devicetree/bindings/input/
Datmel,maxtouch.txt27 Note: the numbering of the GPIOs and the bit they start at varies between
/Linux-v5.10/arch/powerpc/perf/
Dhv-24x7-domains.h11 * domain have the same numbering (so far they do), but this
/Linux-v5.10/drivers/iio/adc/
Dep93xx_adc.c63 * Numbering scheme for channels 0..4 is defined in EP9301 and EP9302 datasheets.
64 * EP9307, EP9312 and EP9312 have 3 channels more (total 8), but the numbering is
/Linux-v5.10/Documentation/arm/samsung/
Dgpio.rst27 GPIO numbering is synchronised between the Samsung and gpiolib system.
/Linux-v5.10/arch/arc/include/asm/
Dkgdb.h33 /* This is the numbering of registers according to the GDB. See GDB's
/Linux-v5.10/arch/sh/include/mach-dreamcast/mach/
Dsysasic.h20 Event Status Registers. Because of the virtual IRQ numbering scheme, a
/Linux-v5.10/Documentation/devicetree/bindings/display/bridge/
Ddw_hdmi.txt32 in Documentation/devicetree/bindings/graph.txt. The numbering of the ports
/Linux-v5.10/arch/mips/sni/
Dirq.c45 * interrupts even if the hardware uses a different interrupt numbering.
/Linux-v5.10/arch/mips/cavium-octeon/executive/
Docteon-model.c207 * pass numbering. in octeon_model_get_string_buffer()
231 * pass numbering. in octeon_model_get_string_buffer()
252 * pass numbering. in octeon_model_get_string_buffer()
/Linux-v5.10/drivers/net/ethernet/freescale/fman/
Dfman_mac.h180 /* MAC ID; numbering of dTSEC and 1G-mEMAC:
182 * numbering of 10G-MAC (TGEC) and 10G-mEMAC:
/Linux-v5.10/Documentation/virt/kvm/devices/
Dmpic.rst53 The numbering is the same as the MPIC device tree binding -- based on
/Linux-v5.10/arch/nds32/include/asm/
Dnds32.h73 /* dispatched sub-entry exception handler numbering */
/Linux-v5.10/drivers/mmc/core/
DKconfig61 hardwired device numbering.
/Linux-v5.10/drivers/staging/media/atomisp/pci/runtime/isp_param/interface/
Dia_css_isp_param_types.h30 /* Explicit member numbering to avoid fish type checker bug */
/Linux-v5.10/Documentation/devicetree/bindings/dma/
Darm-pl08x.txt9 follows the PrimeCell standard numbering using the JEP106 vendor code 0x38

123456789