Searched full:conventions (Results 1 – 25 of 39) sorted by relevance
12
| /Documentation/devicetree/bindings/openrisc/opencores/ |
| D | or1ksim.txt | 5 platform essentially follows the conventions of the OpenRISC architecture
|
| /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
|
| /Documentation/arm/nwfpe/ |
| D | notes.rst | 9 will point it out. The ARM calling conventions require floating point
|
| D | netwinder-fpe.rst | 9 instructions. It follows the conventions in the ARM manual.
|
| /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
|
| /Documentation/crypto/ |
| D | intro.rst | 71 all the same naming conventions of crypto_alloc\*.
|
| /Documentation/devicetree/bindings/mtd/ |
| D | partition.txt | 31 on platforms which have strong conventions about which portions of a flash are
|
| /Documentation/driver-api/usb/ |
| D | callbacks.rst | 58 Calling conventions
|
| D | gadget.rst | 215 detection of capabilities, through naming conventions for endpoints.
220 conventions), to eliminate some of the most common reasons for
|
| /Documentation/i2c/ |
| D | fault-codes.rst | 5 This is a summary of the most important conventions for use of fault
|
| /Documentation/arm/ |
| D | microchip.rst | 193 Naming conventions and best practice:
|
| /Documentation/driver-api/gpio/ |
| D | intro.rst | 86 to have different conventions about what "active" means. Such decisions should
|
| 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
|
| /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
|
| /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
|
| /Documentation/driver-api/ |
| D | pwm.rst | 133 signal conventions in the PWM framework. By definition, normal polarity
|
| /Documentation/process/ |
| D | deprecated.rst | 6 Deprecated Interfaces, Language Features, Attributes, and Conventions
|
| D | 5.Posting.rst | 9 of conventions and procedures which are used in the posting of patches;
|
| /Documentation/media/uapi/v4l/ |
| D | colorspaces.rst | 157 mix of different standards also led to very confusing naming conventions
|
| /Documentation/devicetree/bindings/powerpc/fsl/ |
| D | mpc5200.txt | 7 Naming conventions
|
| /Documentation/driver-api/driver-model/ |
| D | platform.rst | 40 and shutdown notifications using the standard conventions::
|
| /Documentation/devicetree/bindings/arm/ |
| D | cpus.yaml | 27 This document follows the conventions described in the Devicetree
|
| /Documentation/admin-guide/ |
| D | devices.rst | 173 conventions include several historical warts; some of these are
|
| /Documentation/ia64/ |
| D | fsys.rst | 129 must be preserved, in accordance to the normal calling conventions.
|
12