Searched full:conventions (Results 1 – 25 of 113) sorted by relevance
12345
| /Linux-v5.10/drivers/staging/comedi/drivers/ni_routing/ |
| D | README | 100 easier, the naming conventions used in the [board-name].c file are
101 similar to the naming conventions as presented by NI-MAX.
136 conventions.
171 Various naming conventions and relations:
173 These are various notes that help to relate the naming conventions used in the
174 NI-STC with those naming conventions used here.
|
| /Linux-v5.10/include/linux/ |
| D | fsl_devices.h | 23 * Some conventions on how we handle peripherals on Freescale chips
39 * naming conventions:
|
| /Linux-v5.10/Documentation/x86/ |
| D | entry_64.rst | 45 have different calling conventions. The syscall and sysenter
46 instructions have their own peculiar calling conventions. Some of
|
| /Linux-v5.10/include/asm-generic/ |
| D | syscalls.h | 9 * Calling conventions for these system calls can differ, so
|
| /Linux-v5.10/arch/x86/entry/ |
| D | thunk_64.S | 12 /* rdi: arg1 ... normal C conventions. rax is saved/restored. */
|
| /Linux-v5.10/Documentation/devicetree/bindings/openrisc/opencores/ |
| D | or1ksim.txt | 5 platform essentially follows the conventions of the OpenRISC architecture
|
| /Linux-v5.10/Documentation/arm/nwfpe/ |
| D | notes.rst | 9 will point it out. The ARM calling conventions require floating point
|
| /Linux-v5.10/Documentation/devicetree/bindings/pinctrl/ |
| D | nvidia,tegra124-dpaux-padctl.txt | 17 Child nodes contain the pinmux configurations following the conventions
|
| D | nvidia,tegra124-xusb-padctl.txt | 36 Child nodes contain the pinmux configurations following the conventions from
|
| /Linux-v5.10/arch/sparc/net/ |
| D | bpf_jit_32.h | 5 /* Conventions:
|
| /Linux-v5.10/Documentation/ |
| D | asm-annotations.rst | 76 standard C calling conventions. For example, on x86, this means that the
105 conventions -- global and local. Like in C, they both align the functions to
|
| /Linux-v5.10/include/acpi/platform/ |
| D | acintel.h | 28 * Calling conventions:
|
| /Linux-v5.10/Documentation/crypto/ |
| D | intro.rst | 71 all the same naming conventions of crypto_alloc\*.
|
| /Linux-v5.10/Documentation/driver-api/ |
| D | ioctl.rst | 20 conventions around defining them.
23 ioctl commands that follow modern conventions: ``_IO``, ``_IOR``,
|
| /Linux-v5.10/drivers/media/i2c/ |
| D | tvp7002_reg.h | 14 /* Naming conventions
|
| /Linux-v5.10/arch/powerpc/include/asm/ |
| D | dcr-native.h | 75 /* R/W of indirect DCRs make use of standard naming conventions for DCRs */
|
| /Linux-v5.10/Documentation/filesystems/ |
| D | porting.rst | 598 calling conventions for ->follow_link() have changed. Instead of returning
608 calling conventions for ->put_link() have changed. It gets inode instead of
763 ->atomic_open() calling conventions have changed. Gone is ``int *opened``,
777 users. Calling conventions: on success a reference to new struct file
|
| /Linux-v5.10/Documentation/userspace-api/ |
| D | seccomp_filter.rst | 179 architecture that supports multiple system call invocation conventions,
181 the numbers in the different calling conventions overlap, then checks in
|
| /Linux-v5.10/arch/ia64/kernel/ |
| D | sys_ia64.c | 4 * conventions on different platforms.
|
| /Linux-v5.10/Documentation/driver-api/gpio/ |
| D | legacy.rst | 5 This provides an overview of GPIO access conventions on Linux.
58 GPIO conventions
486 What do these conventions omit?
488 One of the biggest things these conventions omit is pin multiplexing, since
|
| /Linux-v5.10/arch/x86/include/asm/ |
| D | set_memory.h | 64 * set_memory_* function for more details on conventions.
|
| /Linux-v5.10/arch/m68k/include/asm/ |
| D | bootstd.h | 34 /* Calling conventions compatible to (uC)linux/68k
|
| /Linux-v5.10/Documentation/driver-api/usb/ |
| D | callbacks.rst | 58 Calling conventions
|
| /Linux-v5.10/Documentation/devicetree/bindings/mtd/ |
| D | partition.txt | 31 on platforms which have strong conventions about which portions of a flash are
|
| /Linux-v5.10/Documentation/i2c/ |
| D | fault-codes.rst | 5 This is a summary of the most important conventions for use of fault
|
12345
