Home
last modified time | relevance | path

Searched refs:functions (Results 1 – 200 of 684) sorted by relevance

1234

/linux-4.1.27/drivers/pinctrl/berlin/
Dberlin.c32 struct berlin_pinctrl_function *functions; member
121 return pctrl->functions[function].name; in berlin_pinmux_get_function_name()
131 *groups = pctrl->functions[function].groups; in berlin_pinmux_get_function_groups()
132 *num_groups = pctrl->functions[function].ngroups; in berlin_pinmux_get_function_groups()
142 struct berlin_desc_function *function = group->functions; in berlin_pinctrl_find_function_by_name()
160 struct berlin_pinctrl_function *func = pctrl->functions + function; in berlin_pinmux_set()
187 struct berlin_pinctrl_function *function = pctrl->functions; in berlin_pinctrl_add_function()
221 pctrl->functions = devm_kzalloc(&pdev->dev, in berlin_pinctrl_build_state()
222 max_functions * sizeof(*pctrl->functions), in berlin_pinctrl_build_state()
224 if (!pctrl->functions) in berlin_pinctrl_build_state()
[all …]
Dberlin.h26 struct berlin_desc_function *functions; member
46 .functions = (struct berlin_desc_function[]){ \
/linux-4.1.27/Documentation/usb/
Dgadget_configfs.txt17 be connected to a USB Host to extend it with additional functions like a serial
22 functions, each function representing e.g. a serial connection or a SCSI disk.
24 Linux provides a number of functions for gadgets to use.
27 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 …]
Dfunctionfs.txt7 that kernel level composite functions provide when they are added to
10 This in particular means that the composite initialisation functions
35 a gadget could use several FunctionFS functions. The idea is that
43 $ insmod g_ffs.ko idVendor=<ID> iSerialNumber=<string> functions=mtp,hid
52 If no "functions" module parameters is supplied, the driver accepts
55 When "functions" module parameter is supplied, only functions
56 with listed names are accepted. In particular, if the "functions"
58 is similar to when there is no "functions" at all; however,
62 filesystems have been mounted and USB descriptors of all functions
Dgadget-testing.txt1 This file summarizes information on basic testing of USB functions
73 and after creating the functions/ecm.<instance name> they contain default
106 and after creating the functions/ecm.<instance name> they contain default
139 and after creating the functions/eem.<instance name> they contain default
265 $ mkdir functions/mass_storage.0/partition.5
397 and after creating the functions/ncm.<instance name> they contain default
521 and after creating the functions/rndis.<instance name> they contain default
691 # mkdir functions/uvc.usb0/control/header/h
692 # cd functions/uvc.usb0/control/header/h
695 # mkdir -p functions/uvc.usb0/streaming/uncompressed/u/360p
[all …]
Dgadget_multi.txt11 USB Mass Storage functions.
30 side. All the functions are handled by respective drivers developed
85 functions will obviously change interface numbers for each of the
91 provided functions one should change gadget's vendor and/or product ID
/linux-4.1.27/kernel/gcov/
Dgcc_4_7.c89 struct gcov_fn_info **functions; member
186 ci_ptr = info->functions[fi_idx]->ctrs; in gcov_info_reset()
227 dci_ptr = dst->functions[fi_idx]->ctrs; in gcov_info_add()
228 sci_ptr = src->functions[fi_idx]->ctrs; in gcov_info_add()
267 dup->functions = NULL; in gcov_info_dup()
273 dup->functions = kcalloc(info->n_functions, in gcov_info_dup()
275 if (!dup->functions) in gcov_info_dup()
283 dup->functions[fi_idx] = kzalloc(fi_size, GFP_KERNEL); in gcov_info_dup()
284 if (!dup->functions[fi_idx]) in gcov_info_dup()
287 *(dup->functions[fi_idx]) = *(info->functions[fi_idx]); in gcov_info_dup()
[all …]
Dgcc_3_4.c78 const struct gcov_fn_info *functions; member
230 ((char *) info->functions + fn * get_fn_size(info)); in get_fn_info()
260 dup->functions = kmemdup(info->functions, info->n_functions * in gcov_info_dup()
262 if (!dup->functions) in gcov_info_dup()
294 kfree(info->functions); in gcov_info_free()
/linux-4.1.27/Documentation/ABI/testing/
Dconfigfs-usb-gadget-uvc1 What: /config/usb-gadget/gadget/functions/uvc.name
10 What: /config/usb-gadget/gadget/functions/uvc.name/control
15 What: /config/usb-gadget/gadget/functions/uvc.name/control/class
20 What: /config/usb-gadget/gadget/functions/uvc.name/control/class/ss
25 What: /config/usb-gadget/gadget/functions/uvc.name/control/class/fs
30 What: /config/usb-gadget/gadget/functions/uvc.name/control/terminal
35 What: /config/usb-gadget/gadget/functions/uvc.name/control/terminal/output
40 What: /config/usb-gadget/gadget/functions/uvc.name/control/terminal/output/default
54 What: /config/usb-gadget/gadget/functions/uvc.name/control/terminal/camera
59 What: /config/usb-gadget/gadget/functions/uvc.name/control/terminal/camera/default
[all …]
Dconfigfs-usb-gadget59 What: /config/usb-gadget/gadget/functions
63 This group contains functions available to this USB gadget.
65 What: /config/usb-gadget/gadget/functions/<func>.<inst>/interface.<n>
78 What: /config/usb-gadget/gadget/functions/<func>.<inst>/interface.<n>/<property>
Dconfigfs-usb-gadget-mass-storage1 What: /config/usb-gadget/gadget/functions/mass_storage.name
14 What: /config/usb-gadget/gadget/functions/mass_storage.name/lun.name
Dconfigfs-usb-gadget-loopback1 What: /config/usb-gadget/gadget/functions/Loopback.name
Dconfigfs-usb-gadget-printer1 What: /config/usb-gadget/gadget/functions/printer.name
Dconfigfs-usb-gadget-phonet1 What: /config/usb-gadget/gadget/functions/phonet.name
Dconfigfs-usb-gadget-sourcesink1 What: /config/usb-gadget/gadget/functions/SourceSink.name
Dconfigfs-usb-gadget-acm1 What: /config/usb-gadget/gadget/functions/acm.name
Dconfigfs-usb-gadget-serial1 What: /config/usb-gadget/gadget/functions/gser.name
Dconfigfs-usb-gadget-obex1 What: /config/usb-gadget/gadget/functions/obex.name
Dconfigfs-usb-gadget-uac21 What: /config/usb-gadget/gadget/functions/uac2.name
Dconfigfs-usb-gadget-ffs1 What: /config/usb-gadget/gadget/functions/ffs.name
Dconfigfs-usb-gadget-hid1 What: /config/usb-gadget/gadget/functions/hid.name
Dconfigfs-usb-gadget-uac11 What: /config/usb-gadget/gadget/functions/uac1.name
Dconfigfs-usb-gadget-midi1 What: /config/usb-gadget/gadget/functions/midi.name
Dconfigfs-usb-gadget-ecm1 What: /config/usb-gadget/gadget/functions/ecm.name
Dconfigfs-usb-gadget-ncm1 What: /config/usb-gadget/gadget/functions/ncm.name
Dconfigfs-usb-gadget-subset1 What: /config/usb-gadget/gadget/functions/geth.name
Dconfigfs-usb-gadget-rndis1 What: /config/usb-gadget/gadget/functions/rndis.name
Dconfigfs-usb-gadget-eem1 What: /config/usb-gadget/gadget/functions/eem.name
Dsysfs-kernel-livepatch17 object (vmlinux or a module) in which it patched functions.
/linux-4.1.27/drivers/gpu/drm/radeon/
Dradeon_atpx_handler.c29 struct radeon_atpx_functions functions; member
146 atpx->functions.power_cntl = true; in radeon_atpx_validate()
148 if (atpx->functions.px_params) { in radeon_atpx_validate()
173 atpx->functions.i2c_mux_cntl = true; in radeon_atpx_validate()
174 atpx->functions.disp_mux_cntl = true; in radeon_atpx_validate()
180 atpx->functions.disp_mux_cntl = true; in radeon_atpx_validate()
224 radeon_atpx_parse_functions(&atpx->functions, output.function_bits); in radeon_atpx_verify_interface()
247 if (atpx->functions.power_cntl) { in radeon_atpx_set_discrete_state()
279 if (atpx->functions.disp_mux_cntl) { in radeon_atpx_switch_disp_mux()
311 if (atpx->functions.i2c_mux_cntl) { in radeon_atpx_switch_i2c_mux()
[all …]
Dradeon_acpi.c228 radeon_atif_parse_functions(&atif->functions, output.function_bits); in radeon_atif_verify_interface()
513 radeon_atcs_parse_functions(&atcs->functions, output.function_bits); in radeon_atcs_verify_interface()
533 if (atcs->functions.pcie_perf_req && atcs->functions.pcie_dev_rdy) in radeon_acpi_is_pcie_performance_request_supported()
559 if (!atcs->functions.pcie_dev_rdy) in radeon_acpi_pcie_notify_device_ready()
599 if (!atcs->functions.pcie_perf_req) in radeon_acpi_pcie_performance_request()
754 if (atif->functions.sbios_requests && !atif->functions.system_params) { in radeon_acpi_init()
759 atif->functions.system_params = true; in radeon_acpi_init()
762 if (atif->functions.system_params) { in radeon_acpi_init()
/linux-4.1.27/Documentation/
Dsgi-ioc4.txt4 First, even though the IOC4 performs multiple functions, such as an
8 standpoint is that all these functions share a single IRQ, and
12 functions, meaning that there's no clear "owning" device driver.
23 the PCI resources that are shared between the IOC4 functions.
25 This driver also provides registration functions that the other
39 remove functions.
45 probe, and remove functions.
Dkernel-doc-nano-HOWTO.txt8 but consistent and extractable documentation of the functions and
10 a consistent style for documenting functions and their parameters,
22 In order to provide good documentation of kernel functions and data
26 We definitely need kernel-doc formatted documentation for functions
30 functions externally visible to other kernel files (not marked
116 form of block comments above functions. The components of this system
136 and external functions.
137 It invokes kernel-doc, giving it the list of functions that
276 Beside functions you can also write documentation for structs, unions,
311 instead of being kernel-doc for functions, structures, unions,
[all …]
Dvme_api.txt111 required. These functions should be passed the pointer to the resource provided
132 Once a master window has been assigned the following functions can be used to
147 These functions return 0 on success or an error code should the call fail.
153 The following functions can be used to read from and write to configured master
154 windows. These functions return the number of bytes copied:
170 This functions by reading the offset, applying the mask. If the bits selected in
187 Once a slave window has been assigned the following functions can be used to
202 These functions return 0 on success or an error code should the call fail.
209 buffers which will be accessible by the VME bridge. These functions do not have
239 The following functions are provided to create and destroy DMA lists. Execution
[all …]
Dunshare.txt93 changes to copy_* functions utilized by clone/fork system call.
183 versions. Helper functions of clone (copy_*) could not be used
201 Therefore code from copy_* functions that allocated and duplicated
202 current context structure was moved into new dup_* functions. Now,
203 copy_* functions call dup_* functions to allocate and duplicate
221 a) Reorganization of existing copy_* functions
223 c) unshare helper functions for each different process context
226 7.1) Reorganization of copy_* functions
232 These dup_* functions allocated and duplicated the appropriate
233 context structure. The reorganized copy_* functions invoked
[all …]
DSM501.txt8 asynchronous serial ports, audio functions, and a dual display video interface.
9 The device may be connected by PCI or local bus with varying functions enabled.
40 as this is by-far the most resource-sensitive of the on-chip functions.
51 functions, which are transient and thus their location is less critical
Dpadata.txt39 There are functions for enabling and disabling the instance:
44 These functions are setting or clearing the "PADATA_INIT" flag;
45 if that flag is not set, other functions will refuse to work.
51 The list of CPUs to be used can be adjusted with these functions:
69 To simply add or remove one CPU from a certain cpumask the functions
109 parallel() and serial() functions should be provided. Those functions will
DCodingStyle35 benefit of warning you when you're nesting your functions too deep.
116 However, there is one special case, namely functions: they have the
126 (a) K&R are _right_ and (b) K&R are right. Besides, functions are
183 somewhat like functions (and are usually used with parentheses in Linux,
253 have descriptive names, as do global functions. If you have a function
294 the proper accessor functions.
296 NOTE! Opaqueness and "accessor functions" are not good in themselves.
362 maximum limits all the more closely. Use helper functions with
374 In source files, separate functions with one blank line. If the function is
389 Chapter 7: Centralized exiting of functions
[all …]
Dio-mapping.txt1 The io_mapping functions in linux/io-mapping.h provide an abstraction for
65 The initial implementation of these functions uses existing mapping
71 map_atomic and map functions add the requested offset to the base of the
Dpnp.txt101 The following functions are available from the Plug and Play Layer:
145 The following are PnP protocol related functions:
197 2.) Optionally define probe and remove functions. It may make sense not to
198 define these functions if the driver already has a reliable method of detecting
238 A series of compatibility functions have been created to make it easy to convert
Dparport-lowlevel.txt6 Described here are the following functions:
8 Global functions:
33 Port functions (can be overridden by low-level drivers):
68 into global functions and port functions.
70 The global functions are mostly for communicating between the device
73 'generic' functions for doing standard things that will work on any
76 The port functions are provided by the low-level drivers, although the
78 The port functions can be split into three groups: SPP, EPP, and ECP.
80 SPP (Standard Parallel Port) functions modify so-called 'SPP'
86 EPP (Enhanced Parallel Port) functions are provided for reading and
[all …]
Dirqflags-tracing.txt31 trace_hardirqs_off()/trace_hardirqs_on() functions. The lock validator
38 lockdep complaint in the irq-flags-tracing functions arch support is
Dassoc_array.txt12 - Manipulation functions.
13 - Access functions.
91 The insertion and deletion functions produce an 'edit script' that can later be
99 after an RCU grace period has passed - thus allowing access functions to
106 There are two functions for dealing with the script:
112 This will perform the edit functions, interpolating various write barriers
125 These functions are guaranteed not to fail.
131 Various functions take a table of operations:
185 There are a number of functions for manipulating an associative array:
301 There are two functions for accessing an associative array:
Dpinctrl.txt187 determine the total number of legal selectors, then it will call the other functions
367 When GPIO-specific functions in the pin control subsystem are called, these
370 pin controller handling the matching range is found, GPIO-specific functions
396 PINMUX, also known as padmux, ballmux, alternate functions or mission modes
399 functions, depending on the application. By "application" in this context
473 pin control driver knows the possible functions. In the example above you can
474 identify three pinmux functions, one for spi, one for i2c and one for mmc.
478 for the three available functions.
494 for a certain set of pins. The knowledge of the functions and pin groups
571 Pinmux drivers are required to supply a few callback functions, some are
[all …]
Dgdb-kernel-debugging.txt143 List of commands and functions
146 The number of commands and convenience functions may evolve over the time,
160 function <function-name>" for convenience functions.
Dkprobes.txt43 There are also register_/unregister_*probes() functions for batch
44 registration/unregistration of a group of *probes. These functions
280 that there are some functions where kprobes cannot probe. Probing
281 (trapping) such functions can cause a recursive trap (e.g. double
283 Kprobes manages such functions as a blacklist.
328 and "unregister_*probes" functions for (un)registering arrays of probes.
329 Here are terse, mini-man-page specifications for these functions and
460 If the functions find an incorrect probe (ex. an unregistered probe),
479 of the array entries before using these functions.
491 If the functions find some incorrect probes (ex. unregistered
[all …]
Dclk.txt56 api itself defines several driver-facing functions which operate on
178 Implement the above functions using container_of:
275 functions are allowed in atomic context.
279 functions are not allowed in atomic context.
291 framework functions from within its implementation of clock operations. This
Dpreempt-locking.txt49 Note, some FPU functions are already explicitly preempt safe. For example,
76 The functions are nestable. In other words, you can call preempt_disable
90 small, atomic code that you wrote and which calls no complex functions.
Drbtree.txt52 users are expected to write their own tree search and insert functions
53 which call the provided rbtree functions. Locking is also left up to the
167 Four functions are provided for iterating through an rbtree's contents in
182 The iterator functions return a pointer to the embedded struct rb_node, from
202 functions with the user provided augmentation callback when inserting
221 rb_erase(). rb_erase_augmented() calls back into user provided functions
/linux-4.1.27/lib/
DKconfig66 tristate "CRC-CCITT functions"
69 modules require CRC-CCITT functions, but a module built outside
71 functions require M here.
74 tristate "CRC16 functions"
77 modules require CRC16 functions, but a module built outside
79 functions require M here.
91 tristate "CRC ITU-T V.41 functions"
94 modules require CRC ITU-T V.41 functions, but a module built outside
96 functions require M here.
99 tristate "CRC32/CRC32c functions"
[all …]
/linux-4.1.27/tools/perf/Documentation/
Dperf-script-perl.txt91 to every event as arguments but are available as library functions.
126 The rest of the script can contain handler functions and support
127 functions in any order.
129 Aside from the event handler functions discussed above, every script
130 can implement a set of optional functions:
164 built-in perf script Perl modules and their associated functions.
169 The following sections describe the functions and variables available
170 via the various Perf::Trace::* Perl modules. To use the functions and
177 These functions provide some essential functions to user scripts.
179 The *flag_str* and *symbol_str* functions provide human-readable
[all …]
Dperf-script-python.txt28 provides more details on each step and lists the library functions
125 # be retrieved using Python functions of the form common_*(context).
126 # See the perf-script-python Documentation for the list of available functions.
165 Following that are a couple generated functions, trace_begin() and
170 Following those are the 'event handler' functions generated one for
171 every event in the 'perf record' output. The handler functions take
177 The final couple of functions are, like the begin and end functions,
211 trace_unhandled() functions, which we won't be using. That leaves us
487 to every event as arguments but are available as library functions.
525 The rest of the script can contain handler functions and support
[all …]
/linux-4.1.27/drivers/s390/crypto/
Dzcrypt_cex4.c79 if (ap_test_bit(&ap_dev->functions, AP_FUNC_ACCEL)) { in zcrypt_cex4_probe()
92 if (ap_test_bit(&ap_dev->functions, AP_FUNC_MEX4K) && in zcrypt_cex4_probe()
93 ap_test_bit(&ap_dev->functions, AP_FUNC_CRT4K)) { in zcrypt_cex4_probe()
107 } else if (ap_test_bit(&ap_dev->functions, AP_FUNC_COPRO)) { in zcrypt_cex4_probe()
125 } else if (ap_test_bit(&ap_dev->functions, AP_FUNC_EP11)) { in zcrypt_cex4_probe()
Dzcrypt_cex2a.c114 if (ap_test_bit(&ap_dev->functions, AP_FUNC_MEX4K) && in zcrypt_cex2a_probe()
115 ap_test_bit(&ap_dev->functions, AP_FUNC_CRT4K)) { in zcrypt_cex2a_probe()
Dap_bus.c263 __ap_query_functions(ap_qid_t qid, unsigned int *functions) in __ap_query_functions() argument
277 *functions = (unsigned int)(reg2 >> 32); in __ap_query_functions()
310 static int ap_query_functions(ap_qid_t qid, unsigned int *functions) in ap_query_functions() argument
314 status = __ap_query_functions(qid, functions); in ap_query_functions()
338 status = __ap_query_functions(qid, functions); in ap_query_functions()
744 return snprintf(buf, PAGE_SIZE, "0x%08X\n", ap_dev->functions); in ap_functions_show()
1484 ap_dev->functions = device_functions; in ap_scan_bus()
1486 ap_dev->functions = 0u; in ap_scan_bus()
/linux-4.1.27/Documentation/arm/OMAP/
Domap_pm6 authors use these functions to communicate minimum latency or
32 five power management functions for driver code:
50 Further documentation for all OMAP PM interface functions can be
63 Driver usage of the OMAP PM functions
66 As the 'pdata' in the above examples indicates, these functions are
69 files to point to the corresponding OMAP PM functions:
72 not support these functions should leave these function pointers set
78 The most common usage of these functions will probably be to specify
107 Other specialized interface functions
110 The five functions listed above are intended to be usable by any
[all …]
/linux-4.1.27/Documentation/power/
Dopp.txt42 OPP library provides a set of helper functions to organize and query the OPP
69 operational functions operate only on available opps:
73 be used for dev_pm_opp_enable/disable functions to make an opp available as required.
76 get_opp_count if dev_pm_opp_enable/disable functions are invoked for a device, the
84 OPP library uses RCU for exclusivity. RCU allows the query functions to operate
94 RCU locking mechanisms. These functions should *NOT* be called under RCU locks
95 and other contexts that prevent blocking functions in RCU or mutex operations
105 OPPs dynamically using the dev_pm_opp_enable / disable functions.
110 with the dev_pm_opp_enable/disable functions. OPP library internally stores
134 frequency back to the corresponding OPP, OPP library provides handy functions
[all …]
Druntime_pm.txt26 * A set of helper functions defined in drivers/base/power/runtime.c that can be
29 device drivers are encouraged to use these functions.
32 fields of 'struct dev_pm_info' and the core helper functions provided for
76 not block or sleep, but it also means that the synchronous helper functions
102 the helper functions described in Section 4 for the device until its status
104 special helper functions for this purpose).
129 fatal error and will refuse to run the helper functions described in Section
131 'suspended' (by means of special helper functions provided by the PM core
157 The helper functions provided by the PM core, described in Section 4, guarantee
182 Additionally, the helper functions provided by the PM core obey the following
[all …]
Dsuspend-and-cpuhotplug.txt146 _cpu_up() functions. They differ in the arguments passed to these functions,
149 the non-boot CPUs are offlined or onlined, the _cpu_*() functions are called
154 Important files and functions/entry points:
190 functions such as collect_cpu_info()).
252 the _cpu_down() and _cpu_up() functions is *always* 0.
/linux-4.1.27/tools/perf/scripts/perl/Perf-Trace-Util/
DREADME4 This module contains utility functions for use with perf script.
8 'used', while Util.pm contains useful but optional utility functions
14 want to add new Perl functions that end up accessing C data in the
15 perf executable, you add desciptions of the new functions here.
18 $context, to all handler functions.
/linux-4.1.27/Documentation/blackfin/
Dbfin-gpio-notes.txt23 multi-functions. They can be configured as peripheral, or just as GPIO,
45 The request functions will record the function state for a certain pin,
46 the free functions will clear its function state.
50 These functions are wrapped by other functions, most of the users need not
/linux-4.1.27/Documentation/networking/
Dvxge.txt22 The functions share a 10GbE link and the pci-e bus, but hardly anything else
34 ii) Multi function mode (up to 17 functions)
37 - Single Root mode: v1.0 (up to 17 functions)
38 - Multi-Root mode: v1.0 (up to 17 functions)
71 Specifies maximum device functions to be enabled.
Dphy.txt41 1) read and write functions must be implemented. Their prototypes are:
47 number. These functions are guaranteed not to be called from interrupt
60 exit functions are used to register the driver.
85 4) The PAL serves only as a library of functions, with the network device
86 manually calling functions to update status, and configure the PHY
166 accessed without the state-machine running, and most of these functions are
167 descended from functions which did not interact with a complex state-machine.
171 Here is a brief rundown of the functions:
209 Ethtool convenience functions.
281 functions if at all possible: genphy_read_status and
[all …]
Datm.txt1 In order to use anything but the most primitive functions of ATM,
Dstmmac.txt285 o stmmac_mdio.c: to provide mdio functions;
292 o dwmac1000_core.c: dwmac GiGa core functions;
293 o dwmac1000_dma.c: dma functions for the GMAC chip;
296 o dwmac100_dma.c: dma functions for the dwmac 100 chip;
298 o dwmac_lib.c: generic DMA functions;
299 o enh_desc.c: functions for handling enhanced descriptors;
300 o norm_desc.c: functions for handling normal descriptors;
301 o chain_mode.c/ring_mode.c:: functions to manage RING/CHAINED modes;
Dcdc_mbim.txt16 behaviour for NCM 1.0 backwards compatible MBIM functions (an
26 This parameter sets the system policy for NCM/MBIM functions. Such
27 functions will be handled by either the cdc_ncm driver or the cdc_mbim
29 makes the cdc_mbim driver ignore these functions and lets the cdc_ncm
34 functions bound to the "wrong" driver
40 MBIM functions are inactive when unmanaged. The cdc_mbim driver only
Dmultiqueue.txt16 alloc_netdev_mq() functions to allocate the subqueues for the device. The
23 netif_{start|stop|wake}_subqueue() functions to manage each queue while the
Dfib_trie.txt94 The route manipulation functions. Should conform pretty closely to the
95 corresponding functions in fib_hash.
111 However, the functions are somewhat separated for other possible locking
/linux-4.1.27/drivers/pinctrl/freescale/
Dpinctrl-mxs.c182 return d->soc->functions[function].name; in mxs_pinctrl_get_func_name()
192 *groups = d->soc->functions[group].groups; in mxs_pinctrl_get_func_groups()
193 *num_groups = d->soc->functions[group].ngroups; in mxs_pinctrl_get_func_groups()
429 soc->functions = devm_kzalloc(&pdev->dev, soc->nfunctions * in mxs_pinctrl_probe_dt()
430 sizeof(*soc->functions), GFP_KERNEL); in mxs_pinctrl_probe_dt()
431 if (!soc->functions) in mxs_pinctrl_probe_dt()
441 f = &soc->functions[idxf]; in mxs_pinctrl_probe_dt()
473 f = &soc->functions[idxf++]; in mxs_pinctrl_probe_dt()
494 f = &soc->functions[idxf++]; in mxs_pinctrl_probe_dt()
Dpinctrl-imx1-core.c320 info->functions[selector].name, info->groups[group].name); in imx1_pmx_set()
368 return info->functions[selector].name; in imx1_pmx_get_func_name()
378 *groups = info->functions[selector].groups; in imx1_pmx_get_groups()
379 *num_groups = info->functions[selector].num_groups; in imx1_pmx_get_groups()
523 func = &info->functions[index]; in imx1_pinctrl_parse_functions()
572 info->functions = devm_kzalloc(&pdev->dev, in imx1_pinctrl_parse_dt()
580 if (!info->functions || !info->groups) in imx1_pinctrl_parse_dt()
Dpinctrl-imx.c200 info->functions[selector].name, grp->name); in imx_pmx_set()
281 return info->functions[selector].name; in imx_pmx_get_func_name()
291 *groups = info->functions[selector].groups; in imx_pmx_get_groups()
292 *num_groups = info->functions[selector].num_groups; in imx_pmx_get_groups()
588 func = &info->functions[index]; in imx_pinctrl_parse_functions()
627 info->functions = devm_kzalloc(&pdev->dev, nfuncs * sizeof(struct imx_pmx_func), in imx_pinctrl_probe_dt()
629 if (!info->functions) in imx_pinctrl_probe_dt()
Dpinctrl-imx1.h64 struct imx1_pmx_func *functions; member
Dpinctrl-imx.h81 struct imx_pmx_func *functions; member
Dpinctrl-mxs.h81 struct mxs_function *functions; member
/linux-4.1.27/drivers/pinctrl/sunxi/
Dpinctrl-sunxi.c57 struct sunxi_pinctrl_function *func = pctl->functions; in sunxi_pinctrl_find_function_by_name()
82 struct sunxi_desc_function *func = pin->functions; in sunxi_pinctrl_desc_find_function_by_name()
107 struct sunxi_desc_function *func = pin->functions; in sunxi_pinctrl_desc_find_function_by_pin()
362 return pctl->functions[function].name; in sunxi_pmx_get_func_name()
372 *groups = pctl->functions[function].groups; in sunxi_pmx_get_func_groups()
373 *num_groups = pctl->functions[function].ngroups; in sunxi_pmx_get_func_groups()
403 struct sunxi_pinctrl_function *func = pctl->functions + function; in sunxi_pmx_set_mux()
744 struct sunxi_pinctrl_function *func = pctl->functions; in sunxi_pinctrl_add_function()
789 pctl->functions = devm_kzalloc(&pdev->dev, in sunxi_pinctrl_build_state()
790 pctl->desc->npins * sizeof(*pctl->functions), in sunxi_pinctrl_build_state()
[all …]
Dpinctrl-sunxi.h92 struct sunxi_desc_function *functions; member
121 struct sunxi_pinctrl_function *functions; member
134 .functions = (struct sunxi_desc_function[]){ \
/linux-4.1.27/Documentation/gpio/
Dconsumer.txt13 that depend on GPIOLIB. The functions that allow a driver to obtain and use
18 All the functions that work with the descriptor-based GPIO interface are
28 gpiod_get() functions. Like many other kernel subsystems, gpiod_get() takes the
46 later with one of the dedicated functions.
51 Both functions return either a valid GPIO descriptor, or an error code checkable
58 gpiod_get_index_optional() functions can be used. These functions return NULL
91 Device-managed variants of these functions are also defined:
126 It is strictly forbidden to use a descriptor after calling these functions.
144 invoking one of the gpiod_direction_*() functions:
236 Note that these functions should only be used with great moderation ; a driver
[all …]
Dboard.txt4 This document explains how GPIOs can be assigned to given devices and functions.
19 GPIOs can easily be mapped to devices and functions in the device tree. The
93 Finally, GPIOs can be bound to devices and functions using platform data. Board
Ddriver.txt168 When implementing an irqchip inside a GPIO driver, these two functions should
179 try_module_get()). A GPIO driver can use the following functions instead
190 These functions must be used with care since they do not affect module use
191 count. Do not use the functions to request gpio descriptors not owned by the
/linux-4.1.27/kernel/
DKconfig.locks94 # lock_* functions are inlined when:
97 # trylock_* functions are inlined when:
100 # unlock and unlock_irq functions are inlined when:
105 # unlock_bh and unlock_irqrestore functions are inlined when:
/linux-4.1.27/drivers/staging/media/davinci_vpfe/
Ddavinci-vpfe-mc.txt49 IOCTLs and controls where possible and practical. Much of the functions provided
53 containing hardware-dependent functions.
65 VIDIOC_VPFE_RSZ_S_CONFIG are used to configure, enable and disable functions in
67 functions in the blocks they control. VIDIOC_VPFE_ISIF_S_RAW_PARAMS IOCTL
75 The detailed functions of the VPFE itself related to a given VPFE block is
/linux-4.1.27/Documentation/devicetree/bindings/pinctrl/
Dmarvell,dove-pinctrl.txt11 Available mpp pins/groups and functions:
14 Note: pmu* also allows for Power Management functions listed below
16 name pins functions
63 Power Management functions (pmu*):
79 * group "mpp_audio1" allows the following functions and gpio pins:
Dmarvell,orion-pinctrl.txt14 Available mpp pins/groups and functions:
20 name pins functions
45 name pins functions
70 name pins functions
Dallwinner,sunxi-pinctrl.txt4 each bank has 32 pins. Each pin has 7 multiplexing functions, with
5 the first two functions being GPIO in and out. The configuration on
Dnvidia,tegra124-xusb-padctl.txt61 Valid functions for this group are: "snps", "xusb", "uart", "rsvd".
67 Valid functions for this group are: "snps", "xusb".
73 Valid functions for this group are: "pcie", "usb3", "sata", "rsvd".
Dmarvell,armada-xp-pinctrl.txt13 Available mpp pins/groups and functions:
19 name pins functions
76 name pins functions
Dmarvell,kirkwood-pinctrl.txt16 Available mpp pins/groups and functions:
22 name pins functions
60 name pins functions
104 name pins functions
153 name pins functions
216 name pins functions
286 name pins functions
Dpinctrl-palmas.txt62 There are 4 special functions: opt0, opt1, opt2 and opt3. If any of these
63 functions is selected then directly pins register will be written with 0, 1, 2
Dmarvell,armada-375-pinctrl.txt10 Available mpp pins/groups and functions:
14 name pins functions
Dmarvell,armada-39x-pinctrl.txt11 Available mpp pins/groups and functions:
15 name pins functions
/linux-4.1.27/arch/tile/
DKconfig.debug18 bool "Provide wrapper functions for hypervisor ABI calls"
21 Provide wrapper functions for the hypervisor ABI calls
/linux-4.1.27/drivers/staging/unisys/Documentation/
Doverview.txt21 handle a number of common functions across each of the other
35 buses required to support them. These modules use functions in and
93 The visorbus module handles the bus functions for most functional
100 The visorclientbus module forwards the bus functions for virthba, and
105 The virtpci module handles the bus functions for virthba, and virtnic.
111 depend on functions in the modules described in the support modules
127 clean-up functions on the guest before the guest is shut down or
139 The modules described in this section provide functions and
/linux-4.1.27/arch/c6x/lib/
Ddivi.S20 ;; ABI considerations for the divide functions
27 ;; In our implementation, divu and remu are leaf functions,
29 ;; A0 is not clobbered by any of the functions.
Dremu.S20 ;; ABI considerations for the divide functions
27 ;; In our implementation, divu and remu are leaf functions,
29 ;; A0 is not clobbered by any of the functions.
41 ;; The ABI seems designed to prevent these functions calling each other,
Dremi.S20 ;; ABI considerations for the divide functions
27 ;; In our implementation, divu and remu are leaf functions,
29 ;; A0 is not clobbered by any of the functions.
Ddivu.S20 ;; ABI considerations for the divide functions
27 ;; In our implementation, divu and remu are leaf functions,
29 ;; A0 is not clobbered by any of the functions.
/linux-4.1.27/drivers/staging/iio/magnetometer/
DKconfig22 - hmc5843_core (core functions)
36 - hmc5843_core (core functions)
/linux-4.1.27/Documentation/hwmon/
Dlm8764 The LM87 has four pins which can serve one of two possible functions,
67 Some functions share pins, so not all functions are available at the same
73 For reference, here is the list of exclusive functions:
Ducd900031 interrupts, cascading, or other system functions. Twelve of these pins offer PWM
33 margining, and general-purpose PWM functions.
39 functions. Ten of these pins offer PWM functionality. Using these pins, the
40 UCD9090 offers support for margining, and general-purpose PWM functions.
Dsubmitting-patches66 * Avoid calculations in macros and macro-generated functions. While such macros
69 than necessary. Use inline functions or just regular functions instead.
71 * Use devres functions whenever possible to allocate resources. For rationale
72 and supported functions, please see Documentation/driver-model/devres.txt.
/linux-4.1.27/drivers/staging/speakup/
DTODO19 Some places are currently using in_atomic() because speakup functions
24 There is a duplication of the selection functions in selections.c. These
25 functions should get exported from drivers/char/selection.c (clear_selection
/linux-4.1.27/scripts/coccinelle/free/
Difnullfree.cocci1 /// NULL check before some freeing functions is not needed.
52 msg = "WARNING: NULL check before freeing functions like kfree, debugfs_remove, debugfs_remove_recu…
/linux-4.1.27/drivers/pinctrl/mvebu/
Dpinctrl-mvebu.c55 struct mvebu_pinctrl_function *functions; member
134 if (strcmp(name, pctl->functions[n].name) == 0) in mvebu_pinctrl_find_function_by_name()
135 return &pctl->functions[n]; in mvebu_pinctrl_find_function_by_name()
248 return pctl->functions[fid].name; in mvebu_pinmux_get_func_name()
257 *groups = pctl->functions[fid].groups; in mvebu_pinmux_get_groups()
258 *num_groups = pctl->functions[fid].num_groups; in mvebu_pinmux_get_groups()
266 struct mvebu_pinctrl_function *func = &pctl->functions[fid]; in mvebu_pinmux_set()
512 pctl->functions = funcs; in mvebu_pinctrl_build_functions()
/linux-4.1.27/fs/befs/
DChangeLog22 * Segregated the functions that interface directly with the linux vfs
76 * Made functions in endian.h to do the correct byteswapping, no matter
84 Uses the functions from endian.h [WD]
94 * Cleanup of NLS functions (util.c) [WD]
113 * Added new debug/warning/error print functions in debug.c.
166 * Converted all non vfs-callback functions to use befs_sb_info as the
178 * Added functions to get the private superblock and inode structures from
200 * Removed prototypes for functions who's definitions have been removed
267 * Added B+tree reading functions (in btree.c).
300 * Created io.c, for io related functions.
[all …]
/linux-4.1.27/Documentation/netlabel/
Dlsm_interface.txt29 These are the functions which allow the LSM developer to manipulate the labels
32 level functions are translated into low level protocol operations based on how
43 can use the NetLabel caching functions to associate the LSM internal
/linux-4.1.27/Documentation/virtual/kvm/
Ds390-diag.txt35 DIAGNOSE function code 'X'500' - KVM virtio functions
38 If the function code specifies 0x500, various virtio-related functions
79 If the function code specifies 0x501, breakpoint functions may be performed.
Dcpuid.txt10 KVM cpuid functions are:
19 and will be updated if more functions are added in the future.
/linux-4.1.27/Documentation/trace/
Dfunction-graph-fold.vim6 " functions. While closed, a fold will show the total time taken for a call,
8 " functions will not include finish_task_switch(), so folding should remain
Dtracepoints.txt8 connect probe functions to them and provides some examples of probe
9 functions.
106 put in inline functions, inlined static functions, and unrolled loops
107 as well as regular functions.
Dftrace.txt189 has a side effect of enabling or disabling specific functions
190 to be traced. Echoing names of functions into this file
191 will limit the trace to only those functions.
215 This lists the functions that ftrace
227 displays all functions that have a callback attached to them
229 Note, a callback may also call multiple functions which will
244 When set it will enable all functions with either the function
246 keep a histogram of the number of functions that were called
248 track of the time spent in those functions. The histogram
311 functions the stack tracer will check.
[all …]
Dftrace-design.txt31 You will need to implement the mcount and the ftrace_stub functions.
69 Here is some pseudo code that should help (these functions should actually be
110 some functions to save (hijack) and restore the return address.
210 If you can't trace NMI functions, then skip this option.
322 patching multiple things. First, only functions that we actually want to trace
340 There are two functions that are used to do runtime patching of arbitrary
341 functions. The first is used to turn the mcount call site into a nop (which
345 linux/ftrace.h for the functions:
/linux-4.1.27/drivers/pinctrl/
Dpinctrl-as3722.c83 const struct as3722_pin_function *functions; member
219 return as_pci->functions[function].name; in as3722_pinctrl_get_func_name()
228 *groups = as_pci->functions[function].groups; in as3722_pinctrl_get_func_groups()
229 *num_groups = as_pci->functions[function].ngroups; in as3722_pinctrl_get_func_groups()
238 u8 val = AS3722_GPIO_IOSF_VAL(as_pci->functions[function].mux_option); in as3722_pinctrl_set()
580 as_pci->functions = as3722_pin_function; in as3722_pinctrl_probe()
Dpinctrl-adi2.h65 const struct adi_pmx_func *functions; member
Dpinctrl-tegra-xusb.c71 const struct tegra_xusb_padctl_function *functions; member
273 return padctl->soc->functions[function].name; in tegra_xusb_padctl_get_function_name()
283 *num_groups = padctl->soc->functions[function].num_groups; in tegra_xusb_padctl_get_function_groups()
284 *groups = padctl->soc->functions[function].groups; in tegra_xusb_padctl_get_function_groups()
861 .functions = tegra124_functions,
Dpinctrl-tegra.c250 return pmx->soc->functions[function].name; in tegra_pinctrl_get_func_name()
260 *groups = pmx->soc->functions[function].groups; in tegra_pinctrl_get_func_groups()
261 *num_groups = pmx->soc->functions[function].ngroups; in tegra_pinctrl_get_func_groups()
656 struct tegra_function *func = &soc_data->functions[fn]; in tegra_pinctrl_probe()
Dpinctrl-tegra.h181 struct tegra_function *functions; member
/linux-4.1.27/drivers/iio/imu/
DKconfig46 A set of IO helper functions for the Analog Devices ADIS* device family.
52 A set of buffer helper functions for the Analog Devices ADIS* device
/linux-4.1.27/drivers/usb/gadget/
Dcomposite.c210 list_add_tail(&function->list, &config->functions); in usb_add_function()
410 list_for_each_entry(f, &config->functions, list) { in config_buf()
621 list_for_each_entry(f, &cdev->config->functions, list) { in reset_config()
755 INIT_LIST_HEAD(&config->functions); in usb_add_config_only()
797 while (!list_empty(&config->functions)) { in usb_add_config()
800 f = list_first_entry(&config->functions, in usb_add_config()
851 while (!list_empty(&config->functions)) { in remove_config()
854 f = list_first_entry(&config->functions, in remove_config()
974 list_for_each_entry(f, &c->functions, list) { in get_string()
1033 list_for_each_entry(f, &c->functions, list) { in get_string()
[all …]
DMakefile10 libcomposite-y += composite.o functions.o configfs.o u_f.o
/linux-4.1.27/Documentation/watchdog/
Dconvert_drivers_to_kernel_api.txt17 needed. So, in general, the 'file_operations' struct and assorted functions can
18 go. Only very few driver-specific details have to be moved to other functions.
19 Here is a overview of the functions and probably needed actions:
83 Check the functions for device-specific stuff and keep it for later
118 functions in the old driver. Note that you will now get a pointer to the
119 watchdog_device as a parameter to these functions, so you probably have to
/linux-4.1.27/drivers/pinctrl/mediatek/
Dpinctrl-mtk-common.h44 const struct mtk_desc_function *functions; member
52 .functions = (struct mtk_desc_function[]){ \
/linux-4.1.27/arch/x86/
DMakefile_32.cpu27 cflags-$(CONFIG_MCRUSOE) += -march=i686 $(align)-functions=0 $(align)-jumps=0 $(align)-loops=0
28 cflags-$(CONFIG_MEFFICEON) += -march=i686 $(call tune,pentium3) $(align)-functions=0 $(align)-jumps…
31 cflags-$(CONFIG_MCYRIXIII) += $(call cc-option,-march=c3,-march=i486) $(align)-functions=0 $(align)…
/linux-4.1.27/Documentation/filesystems/
Dseq_file.txt25 The 2.6 kernel contains a set of functions (implemented by Alexander Viro)
35 * Some utility functions for formatting objects for output without
83 Four functions must be implemented to make the iterator work. The first,
151 the four functions we have just defined:
164 manipulated by the other functions is considered to be completely opaque by
179 output must be passed to the seq_file code. Some utility functions have
185 For straight character output, the following functions may be used:
195 There are also a pair of functions for printing filenames:
219 So far, we have a nice set of functions which can produce output within the
240 by the iterator functions.
[all …]
Ddebugfs.txt36 kernel has been built without debugfs support and none of the functions
55 actually necessary; the debugfs code provides a number of helper functions
71 the following functions can be used instead:
82 These functions are useful as long as the developer knows the size of the
124 Debugfs offers two functions: one to make a registers-only file, and
151 There are a couple of other directory-oriented helper functions:
Drelay.txt12 functions; these automatically log into the current cpu's channel
27 functions in the relay interface code - please see that for details.
71 a couple simple utility functions and a set of examples are provided.
80 The 'klog debugging functions' patch (klog.patch in the relay-apps
81 tarball) provides a couple of high-level logging functions to the
85 functions allow you to put unconditional 'trace' statements anywhere
157 channel management functions:
169 write functions:
183 helper functions:
203 filesystem's directory removal functions should be used for that,
[all …]
/linux-4.1.27/Documentation/ABI/stable/
Dvdso6 These functions are called just like ordinary C function according to
8 if you set CS on x86 to something strange, the vDSO functions are
/linux-4.1.27/Documentation/isdn/
DINTERFACE.CAPI44 From then on, Kernel CAPI may call the registered callback functions for the
49 callback functions by Kernel CAPI.
78 register_capi_driver() and unregister_capi_driver() functions, and contains
94 all controller specific lower layer interface and callback functions to
131 pointers to callback functions for registration and deregistration of
133 Calls to these functions are serialized by Kernel CAPI so that only
157 pointers to callback functions for the device's proc file
162 Note: Callback functions except send_message() are never called in interrupt
274 Library functions (from <linux/isdn/capilli.h>):
305 Library functions for working with _cmsg structures
/linux-4.1.27/drivers/pinctrl/samsung/
Dpinctrl-samsung.c713 struct samsung_pmx_func *functions, *func; in samsung_pinctrl_create_functions() local
742 functions = devm_kzalloc(dev, func_cnt * sizeof(*functions), in samsung_pinctrl_create_functions()
744 if (!functions) { in samsung_pinctrl_create_functions()
748 func = functions; in samsung_pinctrl_create_functions()
783 return functions; in samsung_pinctrl_create_functions()
797 struct samsung_pmx_func *functions; in samsung_pinctrl_parse_dt() local
806 functions = samsung_pinctrl_create_functions(dev, drvdata, &func_cnt); in samsung_pinctrl_parse_dt()
807 if (IS_ERR(functions)) { in samsung_pinctrl_parse_dt()
814 drvdata->pmx_functions = functions; in samsung_pinctrl_parse_dt()
Dpinctrl-exynos5440.c676 struct exynos5440_pmx_func *functions, *func; in exynos5440_pinctrl_parse_dt() local
693 functions = devm_kzalloc(dev, grp_cnt * sizeof(*functions), GFP_KERNEL); in exynos5440_pinctrl_parse_dt()
694 if (!functions) { in exynos5440_pinctrl_parse_dt()
698 func = functions; in exynos5440_pinctrl_parse_dt()
761 priv->pmx_functions = functions; in exynos5440_pinctrl_parse_dt()
/linux-4.1.27/Documentation/i2c/
Ddev-interface94 IMPORTANT: because of the use of inline functions, you *have* to use
140 Not meant to be called directly; instead, use the access functions
148 for details) through the following functions:
166 The above functions are all inline functions, that resolve to calls to
203 5* These i2c-core.c/i2c.h functions are wrappers to the actual
205 callback functions implementing these standard calls.
Dfunctionality85 to let the client drivers check for the support of SMBus functions
86 without having to care whether the said functions are implemented in
112 functions: i2c_smbus_read_byte_data(), i2c_smbus_write_byte_data(),
115 i2c_check_functionality() should match exactly the i2c_smbus_* functions
Dwriting-clients60 All other fields are for call-back functions which will be explained
89 I have found it useful to define foo_read and foo_write functions for this.
90 For some cases, it will be easier to call the i2c functions directly,
94 The below functions are simple examples, and should not be copied
259 Note that some functions are marked by `__init'. These functions can
261 Likewise, functions marked by `__exit' are dropped by the compiler when
315 If you want to communicate with your device, there are several functions
357 This is the generic SMBus function. All functions below are implemented
/linux-4.1.27/Documentation/sh/
Dnew-machine.txt71 | have their own set of cache/tlb functions.
152 machvec functions fall into a number of categories:
154 - I/O functions to IO memory (inb etc) and PCI/main memory (readb etc).
155 - I/O mapping functions (ioport_map, ioport_unmap, etc).
162 There are machvec functions added and removed over time, so always be sure to
166 pointers in the machvec at boot time, as machvec functions are referenced
178 any machine specific IO functions prefixed with the machine name, for
200 the machine specific io functions (if there are enough to warrant it).
/linux-4.1.27/Documentation/pcmcia/
Dlocking.txt16 The following functions and callbacks to struct pcmcia_socket must
33 The following functions and callbacks to struct pcmcia_socket must
/linux-4.1.27/drivers/pinctrl/bcm/
Dpinctrl-cygnus-mux.c112 const struct cygnus_pin_function *functions; member
755 return pinctrl->functions[selector].name; in cygnus_get_function_name()
765 *groups = pinctrl->functions[selector].groups; in cygnus_get_function_groups()
766 *num_groups = pinctrl->functions[selector].num_groups; in cygnus_get_function_groups()
831 &pinctrl->functions[func_select]; in cygnus_pinmux_set_mux()
985 pinctrl->functions = cygnus_pin_functions; in cygnus_pinmux_probe()
Dpinctrl-bcm281xx.c95 const struct bcm281xx_pin_function *functions; member
945 .functions = bcm281xx_functions,
1042 return pdata->functions[function].name; in bcm281xx_pinctrl_get_fcn_name()
1052 *groups = pdata->functions[function].groups; in bcm281xx_pinctrl_get_fcn_groups()
1053 *num_groups = pdata->functions[function].ngroups; in bcm281xx_pinctrl_get_fcn_groups()
1063 const struct bcm281xx_pin_function *f = &pdata->functions[function]; in bcm281xx_pinmux_set()
/linux-4.1.27/Documentation/networking/caif/
DLinux-CAIF.txt69 CAIF payload with receive and transmit functions.
77 The CAIF protocol can be divided into two parts: Support functions and Protocol
78 Implementation. The support functions include:
81 CAIF Packet has functions for creating, destroying and adding content
/linux-4.1.27/fs/ncpfs/
DMakefile16 CFLAGS_ncplib_kernel.o := -finline-functions
/linux-4.1.27/tools/testing/selftests/rcutorture/bin/
Dparse-console.sh33 . functions.sh
Dparse-build.sh35 . functions.sh
Dkvm-recheck-rcu.sh33 . tools/testing/selftests/rcutorture/bin/functions.sh
Dparse-torture.sh36 . functions.sh
Dkvm-recheck.sh28 . tools/testing/selftests/rcutorture/bin/functions.sh
/linux-4.1.27/Documentation/ptp/
Dptp.txt60 functions in the interface. If a clock does not offer a particular
62 from those functions.
81 - 6 GPIOs with dedicated functions (LED/JTAG/clock) can also be
/linux-4.1.27/drivers/soc/qcom/
DKconfig10 functions for connecting the underlying serial UART, SPI, and I2C
/linux-4.1.27/Documentation/timers/
Dtimers-howto.txt20 You must use the *delay family of functions. These
21 functions use the jiffie estimation of clock speed
38 You should use the *sleep[_range] family of functions.
Dhighres.txt92 structure with clock-specific property parameters and callback functions. The
94 set of system functions a clock event device will be used to support. This
101 The management layer assigns one or more of the following functions to a clock
109 functions completely to the management layer. The clock management layer stores
117 registration interface it provides functions to schedule the next event
148 clock source and the clock event device layers provide notification functions
174 execute callback functions directly from the next event interrupt handler. This
209 extended by three functions:
/linux-4.1.27/Documentation/arm/Samsung-S3C24XX/
DGPIO.txt22 of the GPIO functions such as reading and writing a pin will
25 Once all the extant drivers have been converted, the functions
29 The following functions now either have a s3c_ specific variant
98 the GPIO functions which pin is to be used.
/linux-4.1.27/Documentation/devicetree/bindings/arm/
Dversatile-sysreg.txt5 platform functions like board detection and identification, software
Dpsci.txt3 Firmware implementing the PSCI functions described in ARM document number
8 Issue A of the specification describes functions for CPU suspend, hotplug
Dvexpress-sysreg.txt5 platform functions like board detection and identification, software
86 - some functions (eg. energy meter, with its 64 bit long counter)
/linux-4.1.27/arch/m68k/ifpsp060/
Disp.doc91 the ISP routines to reference external functions that must be provided
94 to a function required by the ISP (these functions and their location are
101 to access the functions within the ISP. Since the isp.sa hex file contains
188 _060_real_lock_page() and _060_real_unlock_page(). These functions are
194 the functions _060_real_cas() or _060_real_cas2(). When this new emulation
/linux-4.1.27/Documentation/video4linux/
Domap3isp.txt102 possible and practical. Much of the functions provided by the ISP, however,
107 containing hardware-dependent functions.
120 include/linux/omap3isp.h. The detailed functions of the ISP itself related to
134 configure, enable and disable functions in the CCDC and preview blocks,
135 respectively. Both IOCTLs control several functions in the blocks they
146 functions in the CCDC and preview blocks is associated with a flag (either
Dvideobuf5 The videobuf layer functions as a sort of glue layer between a V4L2 driver
7 the storage of video frames. There is a set of functions which can be used
9 poll(), and, happily, mmap(). Another set of functions can be used to
176 are void functions which, evidently, are immune to failure.
193 Either one of these functions will read frame data into data, returning the
198 one of the above functions, then stop the engine before returning (though a
240 calls. The relevant helper functions are:
254 These support functions can replace a great deal of buffer management
257 The vidioc_streamon() and vidioc_streamoff() functions will be a bit more
350 header files; there are a few low-level functions declared there which have
Dv4l2-framework.txt35 common code into utility functions shared by all drivers.
238 Helper functions exists for sub-devices on an I2C bus that do most of this
294 module owner. This is done for you if you use the i2c helper functions.
433 the two functions takes two arguments: a pointer to struct v4l2_device and a
501 Since these drivers are so common, special helper functions are available to
551 The bridge driver also has some helper functions it can use:
565 Both functions return NULL if something went wrong.
575 There are two more helper functions:
592 v4l2_i2c_new_(probed_)subdev functions will call s_config as well, but with
658 This queue pointer is also used by the vb2 helper functions to check for
[all …]
/linux-4.1.27/arch/x86/math-emu/
DREADME70 (4) The trig, log, and exp functions are based in each case upon quasi-
107 functions and its 80486 value with these functions is likely to differ
170 Timing: Some simple timing tests have been made on the emulator functions.
221 progressively slower for most functions as more of the 80486 features
231 The results of the basic arithmetic functions (+,-,*,/), and fsqrt
238 trig and log functions against the Turbo C "emulator". For this table,
271 The code for reducing the argument for the trig functions (fsin, fcos,
274 consequence, the accuracy of these functions for large arguments has
304 the transcendental functions (in their principal range) was not as
306 has been considerably improved and these functions now give measured
/linux-4.1.27/drivers/pinctrl/qcom/
Dpinctrl-msm.h113 const struct msm_function *functions; member
/linux-4.1.27/drivers/net/ethernet/wiznet/
DKconfig29 the MAC and PHY functions only, onchip TCP/IP is unused.
42 the MAC and PHY functions only, onchip TCP/IP is unused.
/linux-4.1.27/tools/power/cpupower/
DToDo3 - Use bitmask functions to parse CPU topology more robust
/linux-4.1.27/Documentation/security/
DIMA-templates.txt16 a new template is defined, the functions that generate and display
28 two functions, init() and show(), respectively to generate and display
48 The functions ima[_ascii]_measurements_show() retrieve, for each entry,
/linux-4.1.27/drivers/pinctrl/spear/
Dpinctrl-spear.c222 return pmx->machdata->functions[function]->name; in spear_pinctrl_get_func_name()
231 *groups = pmx->machdata->functions[function]->groups; in spear_pinctrl_get_func_groups()
232 *ngroups = pmx->machdata->functions[function]->ngroups; in spear_pinctrl_get_func_groups()
/linux-4.1.27/Documentation/fmc/
DAPI.txt4 The FMC core exports the usual 4 functions that are needed for a bus to
30 The functions to register and unregister n devices are meant to be used
D00-INDEX14 - The functions that are exported by the bus driver
/linux-4.1.27/drivers/sn/
DKconfig14 functions on such a card, but provides necessary infrastructure
/linux-4.1.27/kernel/livepatch/
DKconfig17 a patch, causing calls to patched functions to be redirected
/linux-4.1.27/drivers/pinctrl/intel/
Dpinctrl-intel.h113 const struct intel_function *functions; member
/linux-4.1.27/scripts/coccinelle/misc/
Dboolreturn.cocci1 /// Return statements in functions returning bool should use
/linux-4.1.27/firmware/matrox/
Dg200_warp.H162 * WARP pipes are named according to the functions they perform, where
Dg400_warp.H162 * WARP pipes are named according to the functions they perform, where
/linux-4.1.27/Documentation/mic/mpssd/
Dmicctrl30 . /etc/init.d/functions
Dmpss34 . /etc/init.d/functions
/linux-4.1.27/arch/m68k/fpsp040/
Dkernel_ex.S6 | transcendental functions. Typically, the t_xx routine will
62 | t_dz2 is used by monadic functions such as flogn (from do_func).
63 | t_dz is used by monadic functions such as satanh (from the
/linux-4.1.27/Documentation/locking/
Dlockstat.txt14 Lockdep already has hooks in the lock functions and maps lock instances to
16 The graph below shows the relation between the lock functions and the various
39 lock, unlock - the regular lock functions
Dlglock.txt73 turned into a set of functions by Andi Kleen [7]. The change to functions
76 functions is also the basis to eliminated the restriction of not
/linux-4.1.27/arch/powerpc/platforms/powermac/
Dpfunc_core.c542 struct list_head functions; member
670 list_add(&func->link, &dev->functions); in pmf_add_function_prop()
730 INIT_LIST_HEAD(&dev->functions); in pmf_register_driver()
795 while(!list_empty(&dev->functions)) { in pmf_unregister_driver()
797 list_entry(dev->functions.next, typeof(*func), link); in pmf_unregister_driver()
844 list_for_each_entry(func, &dev->functions, link) { in __pmf_find_function()
970 list_for_each_entry_safe(func, tmp, &dev->functions, link) { in pmf_do_functions()
/linux-4.1.27/Documentation/scsi/
Dscsi_mid_low_api.txt87 a) directly invoking functions supplied by the mid level
90 functions at some point in the future. The LLD will supply
91 implementations of these functions.
95 Those functions in group a) are listed in a section entitled "Mid level
96 supplied functions" below.
98 Those functions in group b) are listed in a section entitled "Interface
99 functions" below. Their function pointers are placed in the members of
101 scsi_host_alloc() ** . Those interface functions that the LLD does not
111 All functions defined within an LLD and all data defined at file scope
118 and scsi_unregister() functions remain to support legacy LLDs that use
[all …]
/linux-4.1.27/Documentation/PCI/
Dpci.txt68 the PCI functions described below are defined as inline functions either
114 of PCI Power Management and the related functions.)
179 1.1 "Attributes" for driver functions/data
181 Please mark the initialization and cleanup functions where appropriate
189 o The module_init()/module_exit() functions (and all
190 initialization functions called _only_ from these)
229 These functions are hotplug-safe. They increment the reference count on
509 space of a device represented by struct pci_dev *. All these functions return 0
527 6. Other interesting functions
553 All PCI layer functions use this identification and it's the only
[all …]
Dpcieaer-howto.txt31 driver provides three basic functions:
142 upstream ports should provide their own reset_link functions.
165 Below sections specify when to call the error callback functions.
205 3.3 helper functions
239 A: This infrastructure calls the error callback functions of the
247 A: It could call the helper functions to enable AER in devices and
/linux-4.1.27/Documentation/blockdev/drbd/
DREADME.txt13 relates some functions, and write packets.
/linux-4.1.27/Documentation/devicetree/bindings/mfd/
Dqcom,tcsr.txt4 functions for their peripherals. This node is intended to allow access to these
/linux-4.1.27/drivers/pcmcia/
Dcardbus.c75 s->functions = pci_scan_slot(bus, PCI_DEVFN(0, 0)); in cb_alloc()
/linux-4.1.27/Documentation/serial/
Dtty.txt207 Callers to the line discipline functions from the tty layer are required to
223 reference takes away your right to call the ldisc functions until you take
231 While these functions are slightly slower than the old code they should have
236 functions are called with the ldisc unavailable. Thus tty_ldisc_ref will
237 fail in this situation if used within these functions. Ldisc and driver
238 code calling its own functions must be careful in this case.
/linux-4.1.27/Documentation/i2c/busses/
Di2c-ismt32 The S12xx series contain a pair of PCI functions. An output of lspci will show
/linux-4.1.27/drivers/pinctrl/nomadik/
DKconfig4 bool "ST-Ericsson ABx500 family Mixed Signal Circuit gpio functions"
Dpinctrl-nomadik.h144 const struct nmk_function *functions; member
Dpinctrl-abx500.h181 const struct abx500_function *functions; member
/linux-4.1.27/arch/arm/mach-shmobile/
Dheadsmp.S54 adr r6, 2f @ array of per-cpu functions
/linux-4.1.27/drivers/mfd/
DKconfig14 tristate "AMD CS5535 and CS5536 southbridge core functions"
18 This is the core driver for CS5535/CS5536 MFD functions. This is
254 functions, such as regulators, RTC, codec, Coulomb counter, etc.
305 other drivers to control these functions, currently GPIO and
325 thermal, charger and related power management functions
372 device may provide functions like watchdog, GPIO, UART and I2C bus.
594 facilities, and registers devices for the various functions
616 This enables support for the Philips UCB1400 core functions.
666 of the independent functions as children nodes in the device tree.
782 asynchronous serial ports, audio functions, and a dual display video
[all …]
/linux-4.1.27/arch/alpha/kernel/
Dhead.S59 # The following two functions are needed for supporting SRM PALcode
/linux-4.1.27/scripts/coccinelle/null/
Deno.cocci1 /// The various basic memory allocation functions don't return ERR_PTR
/linux-4.1.27/drivers/staging/android/ion/
DKconfig18 kernel and device side ION functions.
/linux-4.1.27/Documentation/arm/Samsung/
DGPIO.txt40 on these functions.
/linux-4.1.27/Documentation/dmaengine/
Dprovider.txt242 The functions that we have to fill in there, and hence have to
248 - These functions will be called whenever a driver will call
254 - These functions can sleep.
257 - These functions are matching the capabilities you registered
259 - These functions all take the buffer or the scatterlist relevant
262 - These functions can be called from an interrupt context
312 the prep_* functions
/linux-4.1.27/Documentation/nfc/
Dnfc-pn544.txt17 write functions behave a bit differently because the message formats
/linux-4.1.27/Documentation/devicetree/bindings/i2c/
Di2c-opal.txt13 the relevant OPAL functions.
/linux-4.1.27/scripts/coccinelle/api/alloc/
Dalloc_cast.cocci1 /// Remove casting the values returned by memory allocation functions
/linux-4.1.27/arch/mips/alchemy/
DKconfig11 # to create the necessary gpio_* functions in your board code/headers!
/linux-4.1.27/Documentation/filesystems/caching/
Dnetfs-api.txt240 (8) A pair of functions to manage contexts for the completion callback
243 The cache read/write functions are passed a context which is then passed
245 valid until after the I/O completion is called, two functions may be
250 scope, then these functions are not required. These functions are not
251 required for indices as indices may not contain data. These functions may
348 functions - see below).
446 three functions that are used to do this.
503 maintained with the get_context/put_context functions mentioned above.
659 each page on which the read or write page functions above have been called to
666 operation started by the read/alloc and write functions, so the page
[all …]
/linux-4.1.27/Documentation/sound/alsa/
DREADME.maya4419 The following functions work, as tested by Rainer Zimmermann and Piotr Makowski:
29 The following functions *should* work, but are not fully tested:
37 *In particular, we would appreciate testing of these functions by anyone who has access to an M/IO/…
/linux-4.1.27/scripts/
DKbuild.include68 # gcc support functions
123 cc-option-align = $(subst -functions=0,,\
124 $(call cc-option,-falign-functions=0,-malign-functions=0))

1234