Searched full:numbers (Results 1 – 25 of 2001) sorted by relevance
12345678910>>...81
| /Linux-v5.10/Documentation/core-api/irq/ |
| D | irq-domain.rst | 10 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
91 map are fixed time lookup for IRQ numbers, and irq_descs are only
110 The irq_domain maintains a radix tree map from hwirq numbers to Linux
155 for IRQ numbers that are passed to struct device registrations. In that
[all …]
|
| /Linux-v5.10/arch/mips/include/asm/vr41xx/ |
| D | irq.h | 5 * Interrupt numbers for NEC VR4100 series.
17 * CPU core Interrupt Numbers
31 * SYINT1 Interrupt Numbers
52 * SYSINT2 Interrupt Numbers
71 * GIU Interrupt Numbers
78 * VRC4173 Interrupt Numbers
|
| /Linux-v5.10/arch/arm/mach-omap1/include/mach/ |
| D | irqs.h | 19 * IRQ numbers for interrupt handler 1
21 * NOTE: See also the OMAP-1510 and 1610 specific IRQ numbers below
47 * OMAP-1510 specific IRQ numbers for interrupt handler 1
61 * OMAP-1610 specific IRQ numbers for interrupt handler 1
75 * OMAP-7xx specific IRQ numbers for interrupt handler 1
97 * IRQ numbers for interrupt handler 2
99 * NOTE: See also the OMAP-1510 and 1610 specific IRQ numbers below
128 * OMAP-1510 specific IRQ numbers for interrupt handler 2
134 * OMAP-1610 specific IRQ numbers for interrupt handler 2
172 * OMAP-7xx specific IRQ numbers for interrupt handler 2
|
| /Linux-v5.10/arch/mips/include/asm/mach-rc32434/ |
| D | irq.h | 18 #define GROUP0_IRQ_BASE 8 /* GRP2 IRQ numbers start here */
19 /* GRP3 IRQ numbers start here */
21 /* GRP4 IRQ numbers start here */
23 /* GRP5 IRQ numbers start here */
|
| /Linux-v5.10/arch/powerpc/platforms/cell/ |
| D | interrupt.h | 6 * Mapping of IIC pending bits into per-node interrupt numbers.
8 * Interrupt numbers are in the range 0...0x1ff where the top bit
18 * defined by bit numbers in IIC_SR
61 /* Base numbers for the external interrupts */
67 /* Base numbers for the IIC_ISR interrupts */
|
| /Linux-v5.10/Documentation/process/ |
| D | magic-number.rst | 3 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
156 Note that there are also defined special per-driver magic numbers in sound
158 OSS sound drivers have their magic numbers constructed from the soundcard PCI
161 HFS is another larger user of magic numbers - you can find them in
|
| /Linux-v5.10/fs/ |
| D | char_dev.c | 192 * register_chrdev_region() - register a range of device numbers
193 * @from: the first in the desired range of device numbers; must include
195 * @count: the number of consecutive device numbers required
226 * alloc_chrdev_region() - register a range of char device numbers
228 * @baseminor: first of the requested range of minor numbers
229 * @count: the number of minor numbers required
232 * Allocates a range of char device numbers. The major number will be
250 * @baseminor: first of the requested range of minor numbers
251 * @count: the number of minor numbers required
303 * unregister_chrdev_region() - unregister a range of device numbers
[all …]
|
| /Linux-v5.10/Documentation/usb/ |
| D | functionfs.rst | 18 to worry about endpoints, interfaces or strings numbers but
20 only one (endpoints and strings numbers starting from one and
21 interface numbers starting from zero). The FunctionFS changes
22 them as needed also handling situation when numbers differ in
28 numbers and changing of the configuration (which means that
|
| /Linux-v5.10/include/uapi/linux/ |
| D | serial_core.h | 48 * ARM specific type numbers. These are not currently guaranteed
61 /* Sparc type numbers. */
79 /* Parisc type numbers. */
85 /* Macintosh Zilog type numbers */
106 /* MPC52xx (and MPC512x) type numbers */
159 /* MN10300 on-chip UART numbers */
228 /* ST ASC type numbers */
|
| D | if_pppol2tp.h | 79 * SENDSEQ - 0 => don't send packets with sequence numbers
80 * 1 => send packets with sequence numbers
81 * RECVSEQ - 0 => receive packet sequence numbers are optional
82 * 1 => drop receive packets without sequence numbers
|
| /Linux-v5.10/arch/powerpc/boot/dts/ |
| D | currituck.dts | 149 * We are de-swizzling here because the numbers are actually for
151 * to avoid putting a node for it in the tree, so the numbers
152 * below are basically de-swizzled numbers.
186 * We are de-swizzling here because the numbers are actually for
188 * to avoid putting a node for it in the tree, so the numbers
189 * below are basically de-swizzled numbers.
223 * We are de-swizzling here because the numbers are actually for
225 * to avoid putting a node for it in the tree, so the numbers
226 * below are basically de-swizzled numbers.
|
| D | akebono.dts | 277 * We are de-swizzling here because the numbers are actually for
279 * to avoid putting a node for it in the tree, so the numbers
280 * below are basically de-swizzled numbers.
317 * We are de-swizzling here because the numbers are actually for
319 * to avoid putting a node for it in the tree, so the numbers
320 * below are basically de-swizzled numbers.
357 * We are de-swizzling here because the numbers are actually for
359 * to avoid putting a node for it in the tree, so the numbers
360 * below are basically de-swizzled numbers.
397 * We are de-swizzling here because the numbers are actually for
[all …]
|
| D | redwood.dts | 265 * We are de-swizzling here because the numbers are actually for
267 * to avoid putting a node for it in the tree, so the numbers
268 * below are basically de-swizzled numbers.
306 * We are de-swizzling here because the numbers are actually for
308 * to avoid putting a node for it in the tree, so the numbers
309 * below are basically de-swizzled numbers.
347 * We are de-swizzling here because the numbers are actually for
349 * to avoid putting a node for it in the tree, so the numbers
350 * below are basically de-swizzled numbers.
|
| /Linux-v5.10/arch/ia64/include/uapi/asm/ |
| D | break.h | 6 * IA-64 Linux break numbers.
13 * OS-specific debug break numbers:
19 * OS-specific break numbers:
|
| /Linux-v5.10/Documentation/ABI/testing/ |
| D | sysfs-class-stm | 6 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
|
| /Linux-v5.10/sound/ |
| D | Kconfig | 16 bool "Preclaim OSS device numbers"
21 numbers if any OSS support (native or emulation) is enabled
24 module aliases when one of the device numbers is opened. With
26 device numbers and opening a missing device will generate only the
|
| /Linux-v5.10/include/asm-generic/ |
| D | gpio.h | 18 * While the GPIO programming interface defines valid GPIO numbers
36 * "valid" GPIO numbers are nonnegative and may be passed to
37 * setup routines like gpio_request(). only some valid numbers
40 * Invalid GPIO numbers are useful for indicating no-such-GPIO in
145 /* only non-negative numbers are valid */ in gpio_is_valid()
|
| /Linux-v5.10/security/tomoyo/ |
| D | common.h | 68 /* Index numbers for "struct tomoyo_condition". */
137 /* Index numbers for stat(). */
147 /* Index numbers for operation mode. */
159 /* Index numbers for entry type. */
175 /* Index numbers for domain's attributes. */
189 /* Index numbers for audit type. */
199 /* Index numbers for group entries. */
207 /* Index numbers for type of numeric values. */
215 /* Index numbers for domain transition control keywords. */
227 /* Index numbers for Access Controls. */
[all …]
|
| /Linux-v5.10/net/l2tp/ |
| D | l2tp_core.h | 18 /* Random numbers used for internal consistency checks of tunnel and session structures */
49 unsigned int recv_seq:1; /* expect receive packets with sequence numbers? */
50 unsigned int send_seq:1; /* send packets with sequence numbers? */
52 * LAC enables sequence numbers under LNS control.
95 unsigned int recv_seq:1; /* expect receive packets with sequence numbers? */
96 unsigned int send_seq:1; /* send packets with sequence numbers? */
98 * LAC enables sequence numbers under LNS control.
109 * reordering, if data sequence numbers are enabled for the session.
|
| /Linux-v5.10/tools/power/cpupower/utils/helpers/ |
| D | bitmask.c | 83 * When parsing bitmask lists, only allow numbers, separated by one
95 * The mask term just scanned was ok if and only if either the numbers
97 * the input past the numbers was one of the allowed next characters.
183 * Parses a comma-separated list of numbers and ranges of numbers,
264 * Output format is a comma-separated list of decimal numbers and
266 * decimal numbers, the smallest and largest bit numbers set in
|
| /Linux-v5.10/arch/alpha/include/uapi/asm/ |
| D | ioctl.h | 7 * "anything goes" setup, where more or less random numbers were
13 * it's so painful recognizing both the new and the old numbers..
33 * And this turns out useful to catch old ioctl numbers in header
47 /* used to create numbers */
|
| /Linux-v5.10/Documentation/driver-api/gpio/ |
| D | legacy.rst | 95 reserves "negative" numbers for other purposes like marking signals as
102 numbers passed to them from that setup code, using platform_data to hold
106 So for example one platform uses numbers 32-159 for GPIOs; while another
107 uses numbers 0..63 with one set of GPIO controllers, 64-79 with another
109 The numbers need not be contiguous; either of those platforms could also
110 use numbers 2000-2063 to identify GPIOs in a bank of I2C GPIO expanders.
120 or free GPIOs (see below). Other numbers may also be rejected; for
125 of GPIO numbers, and whether new controllers can be added at runtime. Such issues
126 can affect things including whether adjacent GPIO numbers are both valid.
257 Passing invalid GPIO numbers to gpio_request() will fail, as will requesting
[all …]
|
| /Linux-v5.10/Documentation/filesystems/ |
| D | tmpfs.rst | 103 NodeList format is a comma-separated list of decimal numbers and ranges,
104 a range being two hyphen-separated decimal numbers, the smallest and
105 largest node numbers in the range. For example, mpol=bind:0-3,5,7,9-15
154 numbers:
157 inode64 Use 64-bit inode numbers
158 inode32 Use 32-bit inode numbers
164 but risks glibc failing with EOVERFLOW once 33-bit inode numbers are reached -
|
| /Linux-v5.10/drivers/acpi/acpica/ |
| D | hwpci.c | 4 * Module Name: hwpci - Obtain PCI bus, device, and function numbers
64 * The PCI hardware dynamically configures PCI bus numbers
68 * the Bus/Device/Function numbers in the pci_id with the actual
104 /* Walk the list, updating the PCI device/function/bus numbers */ in acpi_hw_derive_pci_id()
224 * and bus numbers. bus_number is only important for PCI bridges. in acpi_hw_process_pci_list()
226 * function, and bus numbers that are discovered, and assign them in acpi_hw_process_pci_list()
289 * _ADR (contains PCI device and function numbers), and for PCI
340 * Get the bus numbers from PCI Config space: in acpi_hw_get_pci_device_info()
|
| /Linux-v5.10/arch/mips/include/asm/octeon/ |
| D | cvmx-coremask.h | 16 * The core numbers used in this file are the same value as what is found in
19 * For the CN78XX and other multi-node environments the core numbers are not
20 * contiguous. The core numbers for the CN78XX are as follows:
|
12345678910>>...81
