Searched full:functions (Results 1 – 25 of 711) sorted by relevance
12345678910>>...29
| /Documentation/driver-api/80211/ |
| D | cfg80211.rst | 15 :functions: ieee80211_channel_flags 18 :functions: ieee80211_channel 21 :functions: ieee80211_rate_flags 24 :functions: ieee80211_rate 27 :functions: ieee80211_sta_ht_cap 30 :functions: ieee80211_supported_band 33 :functions: cfg80211_signal_type 36 :functions: wiphy_params_flags 39 :functions: wiphy_flags 42 :functions: wiphy [all …]
|
| D | mac80211.rst | 33 :functions: ieee80211_hw 36 :functions: ieee80211_hw_flags 39 :functions: SET_IEEE80211_DEV 42 :functions: SET_IEEE80211_PERM_ADDR 45 :functions: ieee80211_ops 48 :functions: ieee80211_alloc_hw 51 :functions: ieee80211_register_hw 54 :functions: ieee80211_unregister_hw 57 :functions: ieee80211_free_hw 68 :functions: ieee80211_conf [all …]
|
| D | mac80211-advanced.rst | 18 :functions: ieee80211_get_tx_led_name 21 :functions: ieee80211_get_rx_led_name 24 :functions: ieee80211_get_assoc_led_name 27 :functions: ieee80211_get_radio_led_name 30 :functions: ieee80211_tpt_blink 33 :functions: ieee80211_tpt_led_trigger_flags 36 :functions: ieee80211_create_tpt_led_trigger 45 :functions: set_key_cmd 48 :functions: ieee80211_key_conf 51 :functions: ieee80211_key_flags [all …]
|
| /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, gpio 50 - functions pwm, gpio 54 - functions pwm, gpio 58 - functions pwm, 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_virt 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 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 | kernel-api.rst | 6 List Management Functions 12 Basic C Library Functions 16 the C Library. Some of the functions have been found generally useful 17 and they are listed below. The behaviour of these functions may vary 28 :functions: kstrtol 31 :functions: kstrtoul 49 :functions: kstrdup kstrdup_const kstrndup kmemdup kmemdup_nul memdup_user 52 Basic Kernel Library Functions 55 The Linux kernel provides more basic utility functions. 112 :functions: textsearch_find textsearch_next \ [all …]
|
| /Documentation/ABI/testing/ |
| D | configfs-usb-gadget-uvc | 1 What: /config/usb-gadget/gadget/functions/uvc.name 10 What: /config/usb-gadget/gadget/functions/uvc.name/control 19 What: /config/usb-gadget/gadget/functions/uvc.name/control/class 24 What: /config/usb-gadget/gadget/functions/uvc.name/control/class/ss 29 What: /config/usb-gadget/gadget/functions/uvc.name/control/class/fs 34 What: /config/usb-gadget/gadget/functions/uvc.name/control/terminal 39 What: /config/usb-gadget/gadget/functions/uvc.name/control/terminal/output 44 What: /config/usb-gadget/gadget/functions/uvc.name/control/terminal/output/default 58 What: /config/usb-gadget/gadget/functions/uvc.name/control/terminal/camera 63 What: /config/usb-gadget/gadget/functions/uvc.name/control/terminal/camera/default [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. 123 3. Creating the functions 126 The gadget will provide some functions, for each function its corresponding 129 $ mkdir functions/<name>.<instance name> 134 $ mkdir functions/ncm.usb0 # usb_f_ncm.ko gets loaded with request_module() 145 4. Associating the functions with their configurations 149 configurations specified and a number of functions available. What remains [all …]
|
| D | functionfs.rst | 9 that kernel level composite functions provide when they are added to 12 This in particular means that the composite initialisation functions 37 a gadget could use several FunctionFS functions. The idea is that 45 $ insmod g_ffs.ko idVendor=<ID> iSerialNumber=<string> functions=mtp,hid 54 If no "functions" module parameters is supplied, the driver accepts 57 When "functions" module parameter is supplied, only functions 58 with listed names are accepted. In particular, if the "functions" 60 is similar to when there is no "functions" at all; however, 64 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
|
| D | api-skcipher.rst | 8 :functions: crypto_alg ablkcipher_alg blkcipher_alg cipher_alg compress_alg 17 …:functions: crypto_alloc_skcipher crypto_free_skcipher crypto_has_skcipher crypto_skcipher_ivsize … 26 …:functions: crypto_skcipher_reqsize skcipher_request_set_tfm skcipher_request_alloc skcipher_reque… 35 …:functions: crypto_alloc_cipher crypto_free_cipher crypto_has_cipher crypto_cipher_blocksize crypt… 44 …:functions: crypto_free_ablkcipher crypto_has_ablkcipher crypto_ablkcipher_ivsize crypto_ablkciphe… 53 …:functions: crypto_ablkcipher_reqsize ablkcipher_request_set_tfm ablkcipher_request_alloc ablkciph… 62 …:functions: crypto_alloc_blkcipher crypto_free_blkcipher crypto_has_blkcipher crypto_blkcipher_nam…
|
| D | crypto_engine.rst | 37 providing functions for the following: 39 * ``prepare_crypt_hardware``: Called once before any prepare functions are 42 * ``unprepare_crypt_hardware``: Called once after all unprepare functions have 55 Note that these functions access the crypto_async_request structure 76 At the end of the request process, a call to one of the following functions is needed:
|
| D | api-digest.rst | 8 :functions: hash_alg_common ahash_alg shash_alg 17 …:functions: crypto_alloc_ahash crypto_free_ahash crypto_ahash_init crypto_ahash_digestsize crypto_… 26 …:functions: ahash_request_set_tfm ahash_request_alloc ahash_request_free ahash_request_set_callbac… 35 …:functions: crypto_alloc_shash crypto_free_shash crypto_shash_blocksize crypto_shash_digestsize cr…
|
| /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. 77 no longer being called by functions after the unregister_ftrace_function() 146 itself or any nested functions that those functions call. 163 If this is set, then the callback will only be called by functions 174 Filtering which functions to trace 177 If a callback is only to be called from specific functions, a filter must be 196 Filters denote which functions should be enabled when tracing is enabled. 197 If @buf is NULL and reset is set, all functions will be enabled for tracing. 199 The @buf can also be a glob expression to enable all functions that [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
|
| D | i915.rst | 35 :functions: intel_irq_init intel_irq_init_hw intel_hpd_init 38 :functions: intel_runtime_pm_disable_interrupts 41 :functions: intel_runtime_pm_enable_interrupts 184 :functions: intel_dp_set_drrs_state 187 :functions: intel_edp_drrs_enable 190 :functions: intel_edp_drrs_disable 193 :functions: intel_edp_drrs_invalidate 196 :functions: intel_edp_drrs_flush 199 :functions: intel_dp_drrs_init 332 This section documents the interface functions for evicting buffer [all …]
|
| /Documentation/driver-api/fpga/ |
| D | fpga-bridge.rst | 14 :functions: fpga_bridge 17 :functions: fpga_bridge_ops 20 :functions: devm_fpga_bridge_create 23 :functions: fpga_bridge_register 26 :functions: fpga_bridge_unregister
|
| D | fpga-region.rst | 76 :functions: fpga_region 79 :functions: devm_fpga_region_create 82 :functions: fpga_region_register 85 :functions: fpga_region_unregister 88 :functions: fpga_mgr_get 91 :functions: of_fpga_mgr_get 94 :functions: fpga_mgr_put 97 :functions: fpga_bridge_get_to_list 100 :functions: of_fpga_bridge_get_to_list 103 :functions: fpga_bridges_put
|
| /Documentation/media/kapi/ |
| 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/livepatch/ |
| D | livepatch.rst | 13 4.1. New functions 33 functions without a system reboot. 66 Functions are there for a reason. They take some input parameters, get or 70 Many fixes do not change the semantic of the modified functions. For 74 the same way to the rest of the system. In this case, the functions might 78 ordering of locking in multiple functions at the same time. Or a patch 80 all the relevant functions. In this case, the affected unit 82 the functions at the same time. Also the switch must happen only 86 The theory about how to apply functions a safe way is rather complex. 111 tasks. If no affected functions are on the stack of a given task, [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: 81 be used for dev_pm_opp_enable/disable functions to make an opp available as required. 84 get_opp_count if dev_pm_opp_enable/disable functions are invoked for a device, the 97 OPPs dynamically using the dev_pm_opp_enable / disable functions. 103 with the dev_pm_opp_enable/disable functions. OPP library internally stores 126 3. OPP Search Functions [all …]
|
| /Documentation/driver-api/firmware/ |
| D | other_interfaces.rst | 30 :functions: stratix10_svc_command_code 33 :functions: stratix10_svc_client_msg 36 :functions: stratix10_svc_command_config_type 39 :functions: stratix10_svc_cb_data 42 :functions: stratix10_svc_client
|
| /Documentation/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/ |
| D | device-io.rst | 38 suitable for passing to the accessor functions described below, you 58 The functions are named readb(), readw(), readl(), readq(), 64 :c:func:`memcpy_fromio()` and :c:func:`memset_io()` functions are 68 The read and write functions are defined to be ordered. That is the 73 While the basic functions are defined to be synchronous with respect to 113 semantics. Using the relaxed read functions will provide significant 136 Accesses to this space are provided through a set of functions which 138 long. These functions are :c:func:`inb()`, :c:func:`inw()`, 142 Some variants are provided for these functions. Some devices require 146 :c:func:`outs()` functions copy bytes, words or longs to the given [all …]
|
12345678910>>...29