| /linux/samples/rust/ |
| H A D | rust_minimal.rs | 16 numbers: KVec<i32>, field
24 let mut numbers = KVec::new(); in init() localVariable
25 numbers.push(72, GFP_KERNEL)?; in init()
26 numbers.push(108, GFP_KERNEL)?; in init()
27 numbers.push(200, GFP_KERNEL)?; in init()
29 Ok(RustMinimal { numbers }) in init()
35 pr_info!("My numbers are {:?}\n", self.numbers); in drop()
|
| /linux/Documentation/core-api/irq/ |
| H A D | irq-domain.rst | 10 IRQ numbers.
18 So in the past, IRQ numbers could be chosen so that they match the
22 correspondence to hardware interrupt numbers.
25 interrupt numbers, called hardware IRQs, from Linux IRQ numbers.
28 IRQ numbers, but they don't provide any support for reverse mapping of
32 The irq_domain library adds a mapping between hwirq and IRQ numbers on
38 irq_fwspec to hwirq numbers (Device Tree, non-DT firmware node, ACPI
47 numbers for a given interrupt domain. The domain structure is
68 between hwirq and IRQ numbers. Mappings are added to the irq_domain
120 map are fixed time lookup for IRQ numbers, and irq_descs are only
[all …]
|
| /linux/arch/arm/mach-omap1/ |
| H A D | irqs.h | 17 * IRQ numbers for interrupt handler 1
19 * NOTE: See also the OMAP-1510 and 1610 specific IRQ numbers below
45 * OMAP-1510 specific IRQ numbers for interrupt handler 1
59 * OMAP-1610 specific IRQ numbers for interrupt handler 1
73 * OMAP-7xx specific IRQ numbers for interrupt handler 1
95 * IRQ numbers for interrupt handler 2
97 * NOTE: See also the OMAP-1510 and 1610 specific IRQ numbers below
126 * OMAP-1510 specific IRQ numbers for interrupt handler 2
132 * OMAP-1610 specific IRQ numbers for interrupt handler 2
170 * OMAP-7xx specific IRQ numbers for interrupt handler 2
|
| /linux/arch/mips/include/asm/mach-rc32434/ |
| H A 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/Documentation/staging/ |
| H A 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
|
| /linux/fs/ |
| H A 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/arch/powerpc/boot/dts/ |
| H A 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.
|
| H A 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 …]
|
| H A 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/include/uapi/linux/ |
| H A D | serial_core.h | 36 * ARM specific type numbers. These are not currently guaranteed
49 /* Sparc type numbers. */
70 /* Parisc type numbers. */
76 /* Macintosh Zilog type numbers */
91 /* MPC52xx (and MPC512x) type numbers */
183 /* ST ASC type numbers */
|
| H A 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/sound/ |
| H A 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/Documentation/ABI/testing/ |
| H A 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/Documentation/usb/ |
| H A D | functionfs.rst | 21 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
|
| /linux/tools/power/cpupower/utils/helpers/ |
| H A 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/arch/alpha/include/uapi/asm/ |
| H A 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/Documentation/driver-api/cxl/platform/acpi/ |
| H A D | srat.rst | 51 bridge. With the association, latency and bandwidth numbers can be retrieved
68 Proximity Domain List for the related latency or bandwidth numbers. Those
69 performance numbers are tied to a CXL host bridge via the Device Handle.
71 numbers for the whole CXL path access coordinates calculation.
|
| /linux/fs/smb/client/ |
| H A D | export.c | 20 * server inode numbers instead of locally generated temporary ones).
21 * Although cifs inodes do not use generation numbers (have generation number
24 * could be improved by using a new routine which expects 64 bit inode numbers
|
| /linux/Documentation/process/ |
| H A D | cve.rst | 5 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.
|
| /linux/rust/kernel/ |
| H A D | error.rs | 269 /// let mut numbers = KVec::new();
271 /// match numbers.push(72, GFP_KERNEL) {
280 /// match numbers.push(108, GFP_KERNEL) {
289 /// match numbers.push(200, GFP_KERNEL) {
308 /// let mut numbers = KVec::new();
310 /// if let Err(e) = numbers.push(72, GFP_KERNEL) {
315 /// if let Err(e) = numbers.push(108, GFP_KERNEL) {
320 /// if let Err(e) = numbers.push(200, GFP_KERNEL) {
338 /// let mut numbers = KVec::new();
340 /// numbers.push(72, GFP_KERNEL)?;
[all …]
|
| /linux/kernel/gcov/ |
| H A D | base.c | 58 * Number format defined by gcc: numbers are recorded in the 32 bit
81 * Number format defined by gcc: numbers are recorded in the 32 bit
83 * file. 64 bit numbers are stored as two 32 bit numbers, the low part
|
| /linux/lib/math/tests/ |
| H A D | gcd_kunit.c | 18 { 17, 13, 1, "Coprime numbers" },
19 { 101, 103, 1, "Coprime numbers" },
23 { 36, 36, 36, "GCD of identical numbers" },
|
| /linux/drivers/acpi/acpica/ |
| H A 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/arch/x86/entry/ |
| H A D | syscall_64.c | 56 * Convert negative numbers to very high and thus out of range in do_syscall_x64()
57 * numbers for comparisons. in do_syscall_x64()
72 * Adjust the starting offset of the table, and convert numbers in do_syscall_x32()
74 * numbers for comparisons. in do_syscall_x32()
|
| /linux/include/linux/ |
| H A D | gpio.h | 31 * "valid" GPIO numbers are nonnegative and may be passed to
32 * setup routines like gpio_request(). Only some valid numbers
35 * Invalid GPIO numbers are useful for indicating no-such-GPIO in
40 /* only non-negative numbers are valid */ in gpio_is_valid()
|