Searched full:numbers (Results 1 – 25 of 380) sorted by relevance
12345678910>>...16
| /Documentation/ |
| D | IRQ-domain.txt | 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 …]
|
| /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
|
| D | procfs-concurrent_time | 6 numbers for each uid, broken down by the total number of cores that were
14 numbers for each uid, broken down based on the cpufreq policy
|
| D | configfs-stp-policy | 39 Write two numbers: the first master and the last master number.
46 Write two numbers: the first channel and the last channel
|
| /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
|
| /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
157 Note that there are also defined special per-driver magic numbers in sound
159 OSS sound drivers have their magic numbers constructed from the soundcard PCI
162 HFS is another larger user of magic numbers - you can find them in
|
| /Documentation/devicetree/bindings/soc/fsl/cpm_qe/qe/ |
| D | firmware.txt | 15 as an array of two 32-bit numbers.
17 It is an array of 8 32-bit numbers.
|
| /Documentation/devicetree/bindings/misc/ |
| D | aspeed,cvic.txt | 10 different numbers.
24 - copro-sw-interrupts: List of interrupt numbers that can be used as
|
| /Documentation/powerpc/ |
| D | vcpudispatch_stats.txt | 20 a vcpu as represented by the first field, followed by 8 numbers.
25 The next 4 numbers represent vcpu dispatch dispersions:
34 The final 3 numbers represent statistics in relation to the home node of
|
| /Documentation/devicetree/bindings/usb/ |
| D | twlxxxx-usb.txt | 5 - interrupts : Two interrupt numbers to the cpu should be specified. First
25 - interrupts : The interrupt numbers to the cpu should be specified. First
|
| /Documentation/devicetree/bindings/sound/ |
| D | omap-mcbsp.txt | 12 - 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/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 …]
|
| /Documentation/i2c/muxes/ |
| D | i2c-mux-gpio.rst | 69 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/ |
| D | brcm,bus-axi.txt | 12 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/arm/sa1100/ |
| D | serial_uart.rst | 5 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/ |
| D | nxp,lpc1850-rgu.txt | 14 See table below for valid peripheral reset numbers. Numbers not
|
| /Documentation/devicetree/bindings/pci/ |
| D | altera-pcie.txt | 21 mapping of the PCIe interface to interrupt numbers.
26 - bus-range: PCI bus numbers covered
|
| D | aardvark-pci.txt | 20 define the mapping of the PCIe interface to interrupt numbers.
21 - bus-range: PCI bus numbers covered
|
| D | mobiveil-pcie.txt | 27 - bus-range: PCI bus numbers covered
36 PCI interface to interrupt numbers.
|
| /Documentation/filesystems/ |
| D | ocfs2-online-filecheck.txt | 48 mounted. The file above would accept inode numbers. This could be used to
62 <INO> lists the inode numbers.
64 <ERROR> says what kind of errors was found. For the detailed error numbers,
|
| /Documentation/devicetree/bindings/input/ |
| D | nvidia,tegra20-kbc.txt | 11 array of pin numbers which is used as rows.
13 array of pin numbers which is used as column.
|
| /Documentation/ABI/stable/ |
| D | syscalls | 9 documentation for details on the syscall numbers that are to be
|
| /Documentation/security/tpm/ |
| D | tpm_vtpm_proxy.rst | 26 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/devicetree/bindings/power/supply/ |
| D | tps65217_charger.txt | 5 -interrupts: TPS65217 interrupt numbers for the AC and USB charger input change.
|
| /Documentation/devicetree/bindings/display/ti/ |
| D | ti,omap5-dss.txt | 77 - 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>>...16