Searched full:functions (Results 1 – 25 of 861) sorted by relevance
12345678910>>...35
| /Documentation/devicetree/bindings/pinctrl/ |
| D | marvell,armada-37xx-pinctrl.txt | 30 Available groups and functions for the North bridge:
34 - functions jtag, gpio
38 - functions sdio, gpio
42 - functions emmc, gpio
46 - functions pwm, led, gpio
50 - functions pwm, led, gpio
54 - functions pwm, led, gpio
58 - functions pwm, led, gpio
62 - functions pmic, gpio
66 - functions pmic, gpio
[all …]
|
| /Documentation/core-api/ |
| D | genalloc.rst | 21 :functions: gen_pool_create
24 :functions: devm_gen_pool_create
42 :functions: gen_pool_destroy
53 :functions: gen_pool_add
56 :functions: gen_pool_add_owner
65 The functions for allocating memory from the pool (and putting it back)
69 :functions: gen_pool_alloc
72 :functions: gen_pool_dma_alloc
75 :functions: gen_pool_free_owner
87 how the allocation functions choose which specific piece of memory to
[all …]
|
| D | boot-time-mm.rst | 13 :c:func:`mem_init` functions.
16 functions and macros for memory allocations. The allocation request
30 Functions and structures
33 Here is the description of memblock data structures, functions and
36 descriptions for the internal functions can help to understand what
41 :functions:
|
| D | asm-annotations.rst | 13 assembly. The same as in C, such code is grouped into functions and
18 some functions as *global* in order to be visible outside of their translation
27 ``END`` used to mark the end of data or end of special functions with
29 only ends of *standard* functions.
45 missing frame pointer setup/destruction in functions. It can also
76 1. ``SYM_FUNC_*`` -- to annotate C-like functions. This means functions with
83 Checking tools like ``objtool`` should ensure such marked functions conform
84 to these rules. The tools can also easily annotate these functions with
87 2. ``SYM_CODE_*`` -- special functions called with special stack. Be it
89 functions.
[all …]
|
| /Documentation/usb/ |
| D | gadget_configfs.rst | 15 be connected to a USB Host to extend it with additional functions like a serial
20 functions, each function representing e.g. a serial connection or a SCSI disk.
22 Linux provides a number of functions for gadgets to use.
25 and which functions each configuration will provide.
100 Where function drivers support it, functions may allow symlinks to these custom
133 3. Creating the functions
136 The gadget will provide some functions, for each function its corresponding
139 $ mkdir functions/<name>.<instance name>
144 $ mkdir functions/ncm.usb0 # usb_f_ncm.ko gets loaded with request_module()
155 4. Associating the functions with their configurations
[all …]
|
| D | functionfs.rst | 12 that kernel level composite functions provide when they are added to
15 This in particular means that the composite initialisation functions
42 a gadget could use several FunctionFS functions. The idea is that
50 $ insmod g_ffs.ko idVendor=<ID> iSerialNumber=<string> functions=mtp,hid
59 If no "functions" module parameters is supplied, the driver accepts
62 When "functions" module parameter is supplied, only functions
63 with listed names are accepted. In particular, if the "functions"
65 is similar to when there is no "functions" at all; however,
69 filesystems have been mounted and USB descriptors of all functions
|
| /Documentation/crypto/ |
| D | api-kpp.rst | 5 :functions: kpp_request crypto_kpp kpp_alg kpp_secret
14 …:functions: crypto_alloc_kpp crypto_free_kpp crypto_kpp_set_secret crypto_kpp_generate_public_key …
20 …:functions: kpp_request_alloc kpp_request_free kpp_request_set_callback kpp_request_set_input kpp_…
22 ECDH Helper Functions
26 :doc: ECDH Helper Functions
29 :functions: ecdh crypto_ecdh_key_len crypto_ecdh_encode_key crypto_ecdh_decode_key
31 DH Helper Functions
35 :doc: DH Helper Functions
38 :functions: dh crypto_dh_key_len crypto_dh_encode_key crypto_dh_decode_key
|
| /Documentation/arch/s390/ |
| D | pci.rst | 48 Entries specific to zPCI functions and entries that hold zPCI information.
59 powered off until all virtual functions are removed with:
75 PCI function group ID, functions that share identical functionality
80 The virtual function number, from 1 to N for virtual functions,
81 0 for physical functions.
105 The more the segments are different, the more the functions are isolated.
113 * When not using multi-functions (norid is set, or the firmware does not
114 support multi-functions):
121 * When using multi-functions (norid parameter is not set),
122 zPCI functions are addressed differently:
[all …]
|
| /Documentation/driver-api/80211/ |
| D | cfg80211.rst | 15 :functions:
49 :functions:
103 :functions:
115 Utility functions
119 :doc: Utility functions
122 :functions:
138 :functions:
150 :functions:
162 :functions:
174 :functions:
|
| D | mac80211-advanced.rst | 18 :functions:
34 :functions:
55 :functions: ieee80211_beacon_loss
63 :functions: ieee80211_tx_queue_params
82 :functions:
104 :functions:
114 :functions:
126 :functions: ieee80211_scan_completed
148 :functions: ieee80211_ampdu_mlme_action
157 :functions:
[all …]
|
| /Documentation/trace/ |
| D | ftrace-uses.rst | 2 Using ftrace to hook to functions
16 beginning of functions in order to record and trace the flow of the kernel.
33 There are helper functions to help against recursion, and making sure
77 no longer being called by functions after the unregister_ftrace_function()
114 As functions can be called from anywhere, and it is possible that a function
116 recursion protection must be used. There are two helper functions that
209 If this is set, then the callback will only be called by functions
228 Filtering which functions to trace
231 If a callback is only to be called from specific functions, a filter must be
250 Filters denote which functions should be enabled when tracing is enabled.
[all …]
|
| /Documentation/gpu/ |
| D | vga-switcheroo.rst | 28 Public functions
38 :functions: vga_switcheroo_handler
41 :functions: vga_switcheroo_client_ops
47 :functions: vga_switcheroo_handler_flags_t
50 :functions: vga_switcheroo_client_id
53 :functions: vga_switcheroo_state
59 :functions: vgasr_priv
62 :functions: vga_switcheroo_client
94 Public functions
|
| /Documentation/PCI/endpoint/ |
| D | pci-ntb-howto.rst | 45 # ls /sys/kernel/config/pci_ep/functions
57 # mkdir functions/pci_epf_ntb/func1
65 # ls functions/pci_epf_ntb/func1
75 # cat functions/pci_epf_ntb/func1/vendorid
77 # cat functions/pci_epf_ntb/func1/interrupt_pin
88 # echo 0x104c > functions/pci_epf_ntb/func1/vendorid
89 # echo 0xb00d > functions/pci_epf_ntb/func1/deviceid
96 # ls functions/pci_epf_ntb/func1/pci_epf_ntb.0/
102 # echo 4 > functions/pci_epf_ntb/func1/pci_epf_ntb.0/db_count
103 # echo 128 > functions/pci_epf_ntb/func1/pci_epf_ntb.0/spad_count
[all …]
|
| D | pci-vntb-howto.rst | 41 # ls /sys/kernel/config/pci_ep/functions
53 # mkdir functions/pci_epf_vntb/func1
61 # ls functions/pci_epf_ntb/func1
71 # cat functions/pci_epf_vntb/func1/vendorid
73 # cat functions/pci_epf_vntb/func1/interrupt_pin
84 # echo 0x1957 > functions/pci_epf_vntb/func1/vendorid
85 # echo 0x0809 > functions/pci_epf_vntb/func1/deviceid
92 # ls functions/pci_epf_vntb/func1/pci_epf_vntb.0/
98 # echo 4 > functions/pci_epf_vntb/func1/pci_epf_vntb.0/db_count
99 # echo 128 > functions/pci_epf_vntb/func1/pci_epf_vntb.0/spad_count
[all …]
|
| /Documentation/driver-api/media/ |
| D | dtv-demux.rst | 29 The functions that implement the abstract interface demux should be defined
37 Whenever the functions of the demux API modify shared data, the
41 Note that functions called from a bottom half context must not sleep.
44 Linux Kernel calls the functions of a network device interface from a
51 This kernel-space API comprises the callback functions that deliver filtered
52 data to the demux client. Unlike the other DVB kABIs, these functions are
56 structure as in the other demux APIs, because the callback functions are
58 for the API client to provide several callback functions for receiving TS
61 The functions that implement the callback API need not be re-entrant: when
62 a demux driver calls one of these functions, the driver is not allowed to
[all …]
|
| /Documentation/driver-api/fpga/ |
| D | fpga-region.rst | 82 :functions: fpga_region
85 :functions: fpga_region_info
88 :functions: __fpga_region_register_full
91 :functions: __fpga_region_register
94 :functions: fpga_region_unregister
97 :functions: fpga_mgr_get
100 :functions: of_fpga_mgr_get
103 :functions: fpga_mgr_put
106 :functions: fpga_bridge_get_to_list
109 :functions: of_fpga_bridge_get_to_list
[all …]
|
| D | fpga-bridge.rst | 16 :functions: fpga_bridge
19 :functions: fpga_bridge_ops
22 :functions: __fpga_bridge_register
25 :functions: fpga_bridge_unregister
|
| D | fpga-mgr.rst | 7 The FPGA manager core exports a set of functions for programming an FPGA with
73 register functions, ``devm_fpga_mgr_register()`` or
74 ``devm_fpga_mgr_register_full()``. When these functions are used, the
144 :functions: fpga_mgr_states
147 :functions: fpga_manager
150 :functions: fpga_manager_ops
153 :functions: fpga_manager_info
156 :functions: __fpga_mgr_register_full
159 :functions: __fpga_mgr_register
162 :functions: __devm_fpga_mgr_register_full
[all …]
|
| /Documentation/livepatch/ |
| D | livepatch.rst | 20 functions without a system reboot.
53 Functions are there for a reason. They take some input parameters, acquire or
57 Many fixes do not change the semantic of the modified functions. For
61 the same way to the rest of the system. In this case, the functions might
65 ordering of locking in multiple functions at the same time. Or a patch
67 all the relevant functions. In this case, the affected unit
69 the functions at the same time. Also the switch must happen only
73 The theory about how to apply functions a safe way is rather complex.
98 tasks. If no affected functions are on the stack of a given task,
162 patch, which functions are (un)patched, and which functions the blocking tasks
[all …]
|
| /Documentation/power/ |
| D | opp.rst | 11 3. OPP Search Functions
12 4. OPP Availability Control Functions
13 5. OPP Data Retrieval Functions
48 OPP library provides a set of helper functions to organize and query the OPP
77 operational functions operate only on available opps:
82 which can then be used for dev_pm_opp_enable/disable functions to make an
86 get_opp_count if dev_pm_opp_enable/disable functions are invoked for a
99 OPPs dynamically using the dev_pm_opp_enable / disable functions.
105 with the dev_pm_opp_enable/disable functions. OPP library
128 3. OPP Search Functions
[all …]
|
| /Documentation/ABI/testing/ |
| D | configfs-usb-gadget-uvc | 1 What: /config/usb-gadget/gadget/functions/uvc.name
13 What: /config/usb-gadget/gadget/functions/uvc.name/control
27 What: /config/usb-gadget/gadget/functions/uvc.name/control/class
32 What: /config/usb-gadget/gadget/functions/uvc.name/control/class/ss
37 What: /config/usb-gadget/gadget/functions/uvc.name/control/class/fs
42 What: /config/usb-gadget/gadget/functions/uvc.name/control/terminal
47 What: /config/usb-gadget/gadget/functions/uvc.name/control/terminal/output
52 What: /config/usb-gadget/gadget/functions/uvc.name/control/terminal/output/default
69 What: /config/usb-gadget/gadget/functions/uvc.name/control/terminal/camera
74 What: /config/usb-gadget/gadget/functions/uvc.name/control/terminal/camera/default
[all …]
|
| /Documentation/bpf/ |
| D | bpf_licensing.rst | 37 eBPF helper functions is also GPLv2 licensed. Interpreters, JITs, helpers,
44 functions) under
68 When a kernel module is loaded, the linux kernel checks which functions it
76 helper functions.
80 compatible even if they don't use "GPL only" helper functions directly. The
82 kernel is done through EXPORT_SYMBOL_GPL kernel functions. In that sense LSM
83 and struct_ops BPF programs are implicitly calling "GPL only" functions.
84 The same restriction applies to BPF programs that call kernel functions
|
| /Documentation/arch/arm/omap/ |
| D | omap_pm.rst | 6 authors use these functions to communicate minimum latency or
32 five power management functions for driver code:
55 Further documentation for all OMAP PM interface functions can be
68 Driver usage of the OMAP PM functions
71 As the 'pdata' in the above examples indicates, these functions are
74 files to point to the corresponding OMAP PM functions:
78 not support these functions should leave these function pointers set
84 The most common usage of these functions will probably be to specify
113 Other specialized interface functions
116 The five functions listed above are intended to be usable by any
[all …]
|
| /Documentation/driver-api/firmware/ |
| D | request_firmware.rst | 21 :functions: request_firmware
26 :functions: firmware_request_nowarn
31 :functions: firmware_request_platform
36 :functions: request_firmware_direct
41 :functions: request_firmware_into_buf
55 :functions: request_firmware_nowait
69 :functions: firmware_request_cache
|
| /Documentation/driver-api/tty/ |
| D | tty_ldisc.rst | 37 Other Functions
64 Callers to the line discipline functions from the tty layer are required to
71 While these functions are slightly slower than the old code they should have
77 functions are called with the ldisc unavailable. Thus tty_ldisc_ref() will fail
78 in this situation if used within these functions. Ldisc and driver code
79 calling its own functions must be careful in this case.
81 Internal Functions
|
12345678910>>...35