Searched full:function (Results 1 – 25 of 1143) sorted by relevance
12345678910>>...46
| /Documentation/usb/ |
| D | gadget-testing.rst | 10 1. ACM function
11 2. ECM function
12 3. ECM subset function
13 4. EEM function
14 5. FFS function
15 6. HID function
16 7. LOOPBACK function
17 8. MASS STORAGE function
18 9. MIDI function
19 10. NCM function
[all …]
|
| /Documentation/core-api/ |
| D | debug-objects.rst | 70 This function is called whenever the initialization function of a real
76 it calls the fixup_init function of the object type description
77 structure if provided by the caller. The fixup function can correct the
88 object before leaving the function which allocated it. See next section.
93 This function is called whenever the initialization function of a real
99 it calls the fixup_init function of the object type description
100 structure if provided by the caller. The fixup function can correct the
111 calling debug_object_free() before the function which allocates the
117 This function is called whenever the activation function of a real
123 it calls the fixup_activate function of the object type description
[all …]
|
| D | timekeeping.rst | 16 .. c:function:: ktime_t ktime_get( void )
23 .. c:function:: ktime_t ktime_get_boottime( void )
31 .. c:function:: ktime_t ktime_get_real( void )
43 .. c:function:: ktime_t ktime_get_clocktai( void )
51 .. c:function:: ktime_t ktime_get_raw( void )
65 .. c:function:: u64 ktime_get_ns( void )
75 .. c:function:: void ktime_get_ts64( struct timespec64 * )
86 .. c:function:: time64_t ktime_get_seconds( void )
102 .. c:function:: ktime_t ktime_get_coarse( void )
107 .. c:function:: u64 ktime_get_coarse_ns( void )
[all …]
|
| /Documentation/devicetree/bindings/pinctrl/ |
| D | ste,abx500.txt | 23 function = "sysclkreq";
35 function = "sysclkreq";
47 function = "gpio";
59 function = "sysclkreq";
71 function = "pwmout";
83 function = "pwmout";
95 function = "pwmout";
108 function = "adi1";
124 function = "dmic";
140 function = "dmic";
[all …]
|
| D | lantiq,pinctrl-falcon.txt | 15 mux function to select on those group(s), and two pin configuration parameters:
22 other words, a subnode that lists a mux function but no pin configuration
25 information about e.g. the mux function.
29 Definition of mux function groups:
34 - lantiq,function: A string containing the name of the function to mux to the
35 group. Valid values for function names are listed below.
37 Valid values for group and function names:
68 lantiq,function = "asc";
72 lantiq,function = "ntr";
76 lantiq,function = "i2c";
[all …]
|
| D | marvell,mvebu-pinctrl.txt | 4 (mpp) to a specific function. For each SoC family there is a SoC specific
12 be used for a specific device or function. Each node requires one or more
13 mpp pins or group of pins and a mpp function common to all pins.
21 - marvell,function: string representing a function to mux to for all
22 marvell,pins given in this pin configuration node. The function has to be
24 valid pin/pin group names and available function names for each SoC.
44 marvell,function = "uart1";
|
| D | pinctrl-atlas7.txt | 15 function = "audio_ac97";
24 function = "sd2";
68 - function: A string containing the name of the function to mux to the
71 Valid values for group and function names can be found from looking at the
72 group and function arrays in driver files:
79 function = "sd0";
86 function = "sd1_m0";
93 function = "sd1_m1";
|
| D | brcm,nsp-pinmux.txt | 4 addition, certain pins can be muxed to GPIO function individually.
15 - function:
16 The mux function to select
19 The list of groups to select with a given function
36 function = "pwm";
41 function = "gpio_b";
46 function = "nand";
|
| D | renesas,rza1-pinctrl.txt | 8 function (port mode) or in alternate function mode.
9 Up to 8 different alternate function modes exist for each single pin.
37 function or a GPIO controller alternatively.
41 (or a single) pin in some desired alternate function mode.
43 A few alternate function require special pin configuration flags to be
44 supplied along with the alternate function configuration number.
45 The hardware reference manual specifies when a pin function requires
103 When a pin has to be configured in alternate function mode, use this
105 alternate function configuration number along with it.
107 alternate function they shall be specified as members of the same
[all …]
|
| D | fsl,imx-pinctrl.txt | 15 used for a specific device or function. This node represents both mux and config
16 of the pins in that group. The 'mux' selects the function mode(also named mux
46 1. We have pin function node defined under iomux controller node to represent
48 2. The pin configuration node intends to work on a specific function should
49 to be defined under that specific function node.
50 The function node's name should represent well about what function
52 3. The driver can use the function node's name and pin configuration node's
53 name describe the pin function and group hierarchy.
54 For example, Linux IMX pinctrl driver takes the function node's name
55 as the function name and pin configuration node's name as group name to
|
| D | berlin,pinctrl.txt | 10 configurations, one per function. Each subnode has the group name and
11 the muxing function used.
14 is called a 'function' in the pin-controller subsystem.
31 - function: a string describing the function used to mux the groups.
40 function = "uart0";
|
| D | renesas,rza2-pinctrl.txt | 6 function (port mode) or in alternate function mode.
7 Up to 8 different alternate function modes exist for each single pin.
44 (or a single) pin in some desired alternate function mode.
46 number and the desired function index. Use the RZA2_PINMUX macro located
54 When a pin has to be configured in alternate function mode, use this
56 alternate function configuration number along with it.
58 alternate function they shall be specified as members of the same
61 (port where it sits on and pin number) and alternate function identifier
|
| D | fsl,imx27-pinctrl.txt | 17 function + (direction << 2) + (gpio_oconf << 4) + (gpio_iconfa << 8) + (gpio_iconfb << 10)
19 function value is used to select the pin function.
21 0 - Primary function
22 1 - Alternate function
33 have any effect unless GPIO function is selected. A/B/C_IN are output
34 signals of function blocks A,B and C. Specific function blocks are
44 B. GPIO function should be selected if this is configured.
|
| /Documentation/PCI/endpoint/ |
| D | pci-endpoint.rst | 6 endpoint controller driver, endpoint function driver, and using configfs
7 interface to bind the function driver to the controller driver.
28 library, the Endpoint Function library, and the configfs layer to bind the
29 endpoint function with the endpoint controller.
35 in endpoint mode. It also provides APIs to be used by function driver/library
36 in order to implement a particular endpoint function.
68 In order to notify all the function devices that the EPC device to which
81 APIs for the PCI Endpoint Function Driver
85 by the PCI endpoint function driver.
89 The PCI endpoint function driver should use pci_epc_write_header() to
[all …]
|
| /Documentation/trace/ |
| D | ftrace-uses.rst | 17 But callbacks to the start of a function can have other use cases. Either
19 how to use ftrace to implement your own function callbacks.
26 The ability to add a callback to almost any function within the
40 To register a function callback, a ftrace_ops is required. This structure
41 is used to tell ftrace what function should be called as the callback
60 .. c:function:: register_ftrace_function(&ops);
64 .. c:function:: unregister_ftrace_function(&ops);
68 .. c:function:: #include <linux/ftrace.h>
82 The callback function
85 The prototype of the callback function is as follows (as of v4.14):
[all …]
|
| D | ftrace-design.rst | 2 Function Tracer Design
14 Here we will cover the architecture pieces that the common function tracing
49 Keep in mind that the ABI that is in effect inside of the mcount function is
54 mcount call (before/after function prologue). You might also want to look at
55 how glibc has implemented the mcount function for your architecture. It might
58 The mcount function should check the function pointer ftrace_trace_function
60 so return immediately. If it isn't, then call that function in the same way
61 the mcount function normally calls __mcount_internal -- the first argument is
63 size of the mcount call that is embedded in the function).
65 For example, if the function foo() calls bar(), when the bar() function calls
[all …]
|
| /Documentation/kbuild/ |
| D | kconfig-macro-language.rst | 80 You can consider the parameterized reference as a function. (more precisely,
81 "user-defined function" in contrast to "built-in function" listed below).
83 Useful functions must be expanded when they are used since the same function is
85 function is defined using the = assignment operator. The parameters are
89 internally. (In other words, "variable" is "function with zero argument".)
90 When we say "variable" in a broad sense, it includes "user-defined function".
96 Like Make, Kconfig provides several built-in functions. Every function takes a
99 In Make, every built-in function takes at least one argument. Kconfig allows
102 it after all. Let's say "built-in function" here to refer to natively supported
109 The "shell" function accepts a single argument that is expanded and passed
[all …]
|
| /Documentation/networking/dsa/ |
| D | dsa.rst | 109 - receive function is invoked
155 These slave network devices have custom net_device_ops and ethtool_ops function
165 ``ndo_start_xmit()`` function, since they contain the appropriate switch tag, the
228 function hooks should be invoked, information about the directly attached
236 - ``dsa_switch_ops``: structure referencing function pointers, see below for a
272 will not make us go through the switch tagging protocol transmit function, so
302 The PHY configuration is done by the ``dsa_slave_phy_setup()`` function and the
365 - ``setup``: setup function for the switch, this function is responsible for setting
367 interrupts, mutexes, locks etc.. This function is also expected to properly
372 platform should be disabled. Past this function, the switch is expected to be
[all …]
|
| /Documentation/media/uapi/v4l/ |
| D | func-select.rst | 32 .. c:function:: int select( int nfds, fd_set *readfds, fd_set *writefds, fd_set *exceptfds, struct …
57 With the :ref:`select() <func-select>` function applications can suspend
61 When streaming I/O has been negotiated this function waits until a
64 the outgoing queue of the driver the function returns immediately.
67 :c:func:`struct fd_set`. When the function timed out it returns
72 function succeeds, setting the bit of the file descriptor in ``readfds``
76 When use of the :ref:`read() <func-read>` function has been negotiated and the
77 driver does not capture yet, the :ref:`select() <func-select>` function starts
82 data is already available the :ref:`select() <func-select>` function returns
85 When use of the :ref:`write() <func-write>` function has been negotiated the
[all …]
|
| D | func-poll.rst | 30 .. c:function:: int poll( struct pollfd *ufds, unsigned int nfds, int timeout )
41 With the :ref:`poll() <func-poll>` function applications can suspend execution
45 When streaming I/O has been negotiated this function waits until a
48 function waits until the device is ready to accept a new buffer to be
51 (capture) or the incoming queue isn't full (display) the function
59 ``POLLWRNORM`` flags. When the function timed out it returns a value of
63 function succeeds, but sets the ``POLLERR`` flag in the ``revents``
67 :ref:`poll() <func-poll>` function succeeds and sets the ``POLLERR`` flag in
76 When use of the :ref:`read() <func-read>` function has been negotiated and the
77 driver does not capture yet, the :ref:`poll() <func-poll>` function starts
[all …]
|
| D | libv4l-introduction.rst | 123 Those functions operate just like the gcc function ``dup()`` and
129 .. c:function:: int v4l2_open(const char *file, int oflag, ...)
131 operates like the :c:func:`open() <v4l2-open>` function.
133 .. c:function:: int v4l2_close(int fd)
135 operates like the :c:func:`close() <v4l2-close>` function.
137 .. c:function:: int v4l2_dup(int fd)
139 operates like the libc ``dup()`` function, duplicating a file handler.
141 .. c:function:: int v4l2_ioctl (int fd, unsigned long int request, ...)
143 operates like the :c:func:`ioctl() <v4l2-ioctl>` function.
145 .. c:function:: int v4l2_read (int fd, void* buffer, size_t n)
[all …]
|
| /Documentation/sphinx/ |
| D | cdomain.py | 14 * Moved the *duplicate C object description* warnings for function
18 * Add option 'name' to the "c:function:" directive. With option 'name' the
19 ref-name of a function can be modified. E.g.::
21 .. c:function:: int ioctl( int fd, int request )
25 from 'ioctl' to 'VIDIOC_LOG_STATUS'. The function is referenced by::
30 * Handle signatures of function-like macros well. Don't try to deduce
31 arguments types of function-like macros.
72 u"""Handles signatures of function-like macros.
74 If the objtype is 'function' and the the signature ``sig`` is a
75 function-like macro, the name of the macro is returned. Otherwise
[all …]
|
| /Documentation/ |
| D | hwspinlock.txt | 58 be calling this function in order to reserve specific hwspinlock
68 This function provides a means for DT users of a hwspinlock module
72 The function returns a lock id number on success, -EPROBE_DEFER if
93 msecs). If the hwspinlock is already taken, the function will busy loop
95 Upon a successful return from this function, preemption is disabled so
102 The function will never sleep.
109 msecs). If the hwspinlock is already taken, the function will busy loop
111 Upon a successful return from this function, preemption and the local
117 The function will never sleep.
125 msecs). If the hwspinlock is already taken, the function will busy loop
[all …]
|
| /Documentation/virt/kvm/ |
| D | s390-diag.txt | 28 the function code, and bits 0-47 are ignored.
30 The supported DIAGNOSE function codes vary by the userspace used. For
31 DIAGNOSE function codes not specific to KVM, please refer to the
35 DIAGNOSE function code 'X'500' - KVM virtio functions
38 If the function code specifies 0x500, various virtio-related functions
46 the function's return code, which is either a return code or a subcode
77 DIAGNOSE function code 'X'501 - KVM breakpoint
80 If the function code specifies 0x501, breakpoint functions may be performed.
81 This function code is handled by userspace.
83 This diagnose function code has no subfunctions and uses no parameters.
|
| /Documentation/devicetree/bindings/leds/ |
| D | leds-cr0014114.txt | 14 - function :
37 function = "coin";
42 function = "coin";
47 function = "coin";
52 function = "bill";
57 function = "bill";
62 function = "bill";
|
12345678910>>...46