Home
last modified time | relevance | path

Searched full:numbers (Results 1 – 25 of 441) sorted by relevance

12345678910>>...18

/Documentation/ABI/testing/
Dsysfs-class-stm6 Shows first and last available to software master numbers on
21 Reads as 0 if master numbers in the STP stream produced by
22 this stm device will match the master numbers assigned by
Dconfigfs-stp-policy39 Write two numbers: the first master and the last master number.
46 Write two numbers: the first channel and the last channel
/Documentation/core-api/irq/
Dirq-domain.rst10 IRQ numbers.
19 hardware interrupt numbers: whereas in the past, IRQ numbers could
25 interrupt numbers, called hardware irq's, from Linux IRQ numbers.
28 irq numbers, but they don't provide any support for reverse mapping of
32 The irq_domain library adds mapping between hwirq and IRQ numbers on
38 structure to hwirq numbers (Device Tree and ACPI GSI so far), and can
51 between hwirq and IRQ numbers. Mappings are added to the irq_domain
104 map are fixed time lookup for IRQ numbers, and irq_descs are only
123 The irq_domain maintains a radix tree map from hwirq numbers to Linux
171 for IRQ numbers that are passed to struct device registrations. In that
[all …]
/Documentation/staging/
Dmagic-number.rst3 Linux magic numbers
6 This file is a registry of magic numbers which are in use. When you
8 file, since it is best if the magic numbers used by various structures
12 numbers. This allows you to check at run time whether (a) a structure
19 The way to use magic numbers is to declare them at the beginning of
54 but it is possible that some new magic numbers will sneak into the
/Documentation/usb/
Dfunctionfs.rst21 to worry about endpoints, interfaces or strings numbers but
23 only one (endpoints and strings numbers starting from one and
24 interface numbers starting from zero). The FunctionFS changes
25 them as needed also handling situation when numbers differ in
33 numbers and changing of the configuration (which means that
/Documentation/devicetree/bindings/soc/fsl/cpm_qe/qe/
Dfirmware.txt15 as an array of two 32-bit numbers.
17 It is an array of 8 32-bit numbers.
/Documentation/process/
Dcve.rst5 Common Vulnerabilities and Exposure (CVE®) numbers were developed as an
8 regards to the kernel project, and CVE numbers were very often assigned
32 for CVE number assignments and have CVE numbers automatically assigned
40 assign CVE numbers to any bugfix that they identify. This
107 large numbers of assigned CVEs are not relevant for their systems.
/Documentation/arch/powerpc/
Dvcpudispatch_stats.rst23 a vcpu as represented by the first field, followed by 8 numbers.
29 The next 4 numbers represent vcpu dispatch dispersions:
39 The final 3 numbers represent statistics in relation to the home node of
Dassociativity.rst31 The “ibm,associativity” property contains a list of one or more numbers (domainID)
34 The “ibm,associativity-reference-points” property contains a list of one or more numbers
59 "ibm,numa-lookup-index-table" property contains a list of one or more numbers representing
71 "ibm,numa-distance-table" property contains a list of one or more numbers representing the NUMA
/Documentation/devicetree/bindings/misc/
Daspeed,ast2400-cvic.yaml17 but with different numbers.
43 A list of interrupt numbers that can be used as software interrupts from
/Documentation/devicetree/bindings/sound/
Domap-mcbsp.txt12 - interrupts: Interrupt numbers for the McBSP port, as an array in case the
17 - interrupt-names: Array of strings associated with the interrupt numbers
/Documentation/devicetree/bindings/usb/
Dtwlxxxx-usb.txt5 - interrupts : Two interrupt numbers to the cpu should be specified. First
25 - interrupts : The interrupt numbers to the cpu should be specified. First
/Documentation/i2c/muxes/
Di2c-mux-gpio.rst69 If you don't know the absolute GPIO pin numbers at registration time,
71 numbers, and the i2c-mux-gpio driver will do the work for you,
85 GPIO pin numbers at registration time, this is even the only option.
/Documentation/devicetree/bindings/bus/
Dbrcm,bus-axi.txt12 BCM47xx/BCM53xx ARM SoCs. To assign IRQ numbers to the cores, provide
19 detected (e.g. IRQ numbers). Also some of the cores may be responsible
/Documentation/arch/arm/sa1100/
Dserial_uart.rst5 The SA1100 serial port had its major/minor numbers officially assigned::
13 > Okay. Note that device numbers 204 and 205 are used for "low density
/Documentation/devicetree/bindings/reset/
Dnxp,lpc1850-rgu.txt14 See table below for valid peripheral reset numbers. Numbers not
/Documentation/devicetree/bindings/firmware/
Dcznic,turris-omnia-mcu.yaml35 The interrupt numbers correspond sequentially to GPIO numbers, taking the
/Documentation/devicetree/bindings/pci/
Daardvark-pci.txt20 define the mapping of the PCIe interface to interrupt numbers.
21 - bus-range: PCI bus numbers covered
Dmobiveil-pcie.txt27 - bus-range: PCI bus numbers covered
36 PCI interface to interrupt numbers.
/Documentation/devicetree/bindings/input/
Dnvidia,tegra20-kbc.txt11 array of pin numbers which is used as rows.
13 array of pin numbers which is used as column.
/Documentation/filesystems/
Docfs2-online-filecheck.rst51 mounted. The file above would accept inode numbers. This could be used to
66 <INO> lists the inode numbers.
68 <ERROR> says what kind of errors was found. For the detailed error numbers,
/Documentation/security/tpm/
Dtpm_vtpm_proxy.rst26 device with the appropriate major and minor numbers while the file descriptor
36 as well as the major and minor numbers of the character device that was created.
/Documentation/ABI/stable/
Dsyscalls9 documentation for details on the syscall numbers that are to be
/Documentation/devicetree/bindings/gpio/
Dnuvoton,sgpio.yaml51 The numbers of GPIO's exposed. GPIO lines are only for GPI.
58 The numbers of GPIO's exposed. GPIO lines are only for GPO.
/Documentation/devicetree/bindings/display/ti/
Dti,omap5-dss.txt77 - lanes: list of pin numbers for the DSI lanes: CLK+, CLK-, DATA0+, DATA0-,
99 - lanes: list of 8 pin numbers for the HDMI lanes: CLK+, CLK-, D0+, D0-,

12345678910>>...18