Home
last modified time | relevance | path

Searched refs:application (Results 1 – 200 of 316) sorted by relevance

12

/linux-4.4.14/net/bluetooth/cmtp/
Dcapi.c189 struct cmtp_application *application; in cmtp_recv_interopmsg() local
207 application = cmtp_application_get(session, CMTP_MSGNUM, msgnum); in cmtp_recv_interopmsg()
208 if (application) { in cmtp_recv_interopmsg()
209 application->state = BT_CONNECTED; in cmtp_recv_interopmsg()
210 application->msgnum = 0; in cmtp_recv_interopmsg()
211 application->mapping = CAPIMSG_APPID(skb->data); in cmtp_recv_interopmsg()
220 application = cmtp_application_get(session, CMTP_MAPPING, appl); in cmtp_recv_interopmsg()
221 if (application) { in cmtp_recv_interopmsg()
222 application->state = BT_CLOSED; in cmtp_recv_interopmsg()
223 application->msgnum = 0; in cmtp_recv_interopmsg()
[all …]
/linux-4.4.14/Documentation/arm/Marvell/
DREADME138 Dove family (application processor)
143 …Product Brief : http://www.marvell.com/application-processors/armada-500/assets/Marvell_Armada51…
144 …Hardware Spec : http://www.marvell.com/application-processors/armada-500/assets/Armada-510-Hardw…
145 …Functional Spec : http://www.marvell.com/application-processors/armada-500/assets/Armada-510-Funct…
146 Homepage: http://www.marvell.com/application-processors/armada-500/
160 …Product Brief : http://www.marvell.com/application-processors/pxa-family/assets/pxa_27x_pb…
161 …Design guide : http://www.marvell.com/application-processors/pxa-family/assets/pxa_27x_de…
162 …Developers manual : http://www.marvell.com/application-processors/pxa-family/assets/pxa_27x_de…
163 …Specification : http://www.marvell.com/application-processors/pxa-family/assets/pxa_27x_em…
164 …Specification update : http://www.marvell.com/application-processors/pxa-family/assets/pxa_27x_sp…
[all …]
/linux-4.4.14/Documentation/ABI/testing/
Dsysfs-platform-chipidea-usb-otg7 the application running on the A-device wants to use the bus,
8 and to be 0 when the application no longer wants to use
15 Reading: returns 1 if the application running on the A-device
24 application running on the A-device wants to power down
39 that the application running on the B-device wants to use the
40 bus as host, and is 0 when the application no longer wants to
45 Reading: returns if the application running on the B device
Dsysfs-bus-iio-chemical-vz89x7 This value has little application outside of calibration.
Dsysfs-bus-hsi7 serial interface mainly used for connecting application
Dsysfs-driver-tegra-fuse10 Users: any user space application which wants to read the efuses on
Dsysfs-driver-hid-picolcd41 tiles get changed and it's not appropriate to expect the application
Dsysfs-bus-iio84 application of scale and offset are millivolts.
99 is required is a consistent labeling. Units after application
112 application of scale and offset are milliamps.
119 application of scale and offset are nanofarads.
129 is required is a consistent labeling. Units after application
146 less measurements. Units after application of scale and offset
164 after application of scale and offset are m/s^2.
174 Units after application of scale and offset are radians per
184 arbitrarily assigned). Data converted by application of offset
194 assigned). Data converted by application of offset
[all …]
Dsysfs-driver-genwqe10 Description: Identifies the currently active card application e.g. 'GZIP'
Dsysfs-class-uwb_rc52 The application-specific information element (ASIE)
Dsysfs-bus-fcoe115 Users: The first user of this interface will be the fcoeadm application,
Dsysfs-bus-pci253 number of VFs. A userspace application would typically read the
257 file. A userspace application wanting to disable the VFs would
/linux-4.4.14/drivers/hid/
Dhid-plantronics.c39 #define PLT_ALLOW_CONSUMER (field->application == HID_CP_CONSUMERCONTROL && \
73 else if (!((field->application ^ plt_type) & HID_USAGE_PAGE)) { in plantronics_input_mapping()
97 usage->hid, field->application); in plantronics_input_mapping()
103 usage->hid, field->application, mapped_key); in plantronics_input_mapping()
Dwacom_wac.h90 ((f)->application == HID_DG_PEN) || \
91 ((f)->application == HID_DG_DIGITIZER) || \
92 ((f)->application == WACOM_VENDORDEFINED_PEN))
95 ((f)->application == HID_DG_TOUCHSCREEN))
Dhid-multitouch.c437 if (field->application == HID_DG_TOUCHSCREEN) in mt_touch_input_mapping()
443 if (field->application == HID_DG_TOUCHPAD || in mt_touch_input_mapping()
831 field->application != HID_DG_TOUCHSCREEN && in mt_input_mapping()
832 field->application != HID_DG_PEN && in mt_input_mapping()
833 field->application != HID_DG_TOUCHPAD) in mt_input_mapping()
850 if (field->application == HID_DG_TOUCHSCREEN || in mt_input_mapping()
851 field->application == HID_DG_TOUCHPAD) in mt_input_mapping()
869 if (field->application == HID_DG_TOUCHSCREEN || in mt_input_mapped()
870 field->application == HID_DG_TOUCHPAD) in mt_input_mapped()
1015 switch (field->application) { in mt_input_configured()
Dhid-uclogic.c727 (field->application == HID_DG_PEN)) in uclogic_input_mapping()
748 switch (field->application) { in uclogic_input_configured()
Dhid-lg.c587 if (field->application == HID_GD_MOUSE) { in lg_input_mapping()
633 field->application = HID_GD_MULTIAXIS; in lg_input_mapped()
Dhid-ntrig.c588 if (field->application == HID_DG_PEN) in ntrig_event()
871 switch (hidinput->report->field[0]->application) { in ntrig_input_configured()
Dhid-rmi.c554 (field->application == HID_GD_POINTER || in rmi_event()
555 field->application == HID_GD_MOUSE)) { in rmi_event()
1281 unsigned app = (*report)->field[i]->application; in rmi_check_valid_report_id()
Dhid-debug.c544 if (field->application) { in hid_dump_field()
547 hid_resolv_usage(field->application, f); seq_printf(f, ")\n"); in hid_dump_field()
Dhid-input.c538 switch (field->application) { in hidinput_configure_usage()
1014 if (field->application == HID_GD_GAMEPAD || field->application == HID_GD_JOYSTICK) in hidinput_configure_usage()
/linux-4.4.14/Documentation/cgroups/
Dnet_prio.txt8 Nominally, an application would set the priority of its traffic via the
11 1) The application may not have been coded to set this value
12 2) The priority of application traffic is often a site-specific administrative
13 decision rather than an application defined one.
50 One usage for the net_prio cgroup is with mqprio qdisc allowing application
Dhugetlb.txt7 the application will get SIGBUS signal if it tries to access HugeTLB pages
8 beyond its limit. This requires the application to know beforehand how much
Dmemory.txt25 a. Isolate an application or a group of applications
420 Sometimes a user might find that the application under a cgroup is
574 node. One of the use cases is evaluating application performance by
575 combining this information with the application's CPU allocation.
726 To register a threshold, an application must:
745 To register a notifier, an application must:
751 The application will be notified through eventfd when OOM happens.
812 register a notification, an application must:
/linux-4.4.14/Documentation/networking/
Dcdc_mbim.txt43 userspace MBIM management application always is required to enable a
51 management application:
57 Management application development
74 application. It is therefore up to this application to ensure that it
91 limits the maximum control message size. The managament application is
96 The userspace application can access the CDC MBIM functional
105 The userspace application is responsible for all control message
111 The MBIM control messages from the management application *must not*
117 The management application *must* accept control messages of up the
176 The userspace management application is responsible for adding new
[all …]
Dtcp-thin.txt5 that the application sends data with such a low rate that the
11 dependency on the arrival of new data from the application to trigger
21 In order to reduce application-layer latency when packets are lost,
36 they must be specifically activated by the application using the
Drds.txt26 The high-level semantics of RDS from the application's point of view are
121 RDS supports the poll interface to allow the application
141 This allows the application to discard all messages queued to a
144 This allows the application to cancel outstanding messages if
147 The application may decide it's not worth it, and cancel the
231 situation very rarely occurs. An application encountering this
353 return to application
Dtuntap.txt197 Another interesting application using TUN/TAP is pipsecd
208 the kernel sends an IPX packet to tap0, it is passed to the application
209 (VTun for example). The application encrypts, compresses and sends it to
210 the other side over TCP or UDP. The application on the other side decompresses
Drxrpc.txt71 left to the application. AF_RXRPC only deals in blobs. Even the operation ID
84 The Andrew File System (AFS) is an example of an application that uses this and
230 (*) Once the application has received the last message associated with a call,
267 message to server application to let it know there's a new call awaiting
269 application then uses sendmsg to assign a tag to the new call. Once that
272 (*) The server application has to provide the server socket with a keyring of
333 This is used to indicate the application's call ID. It's an unsigned long
341 This is can be used by an application to abort a call by passing it to
349 This is delivered to a server application to indicate that the final ACK
355 This is delivered to an application to indicate that an ICMP error message
[all …]
Dcxgb.txt102 application. Doing so is not warranted in any way by Chelsio Communications,
299 4. On multiprocessor systems, it has been noted that an application which
310 You may need to experiment which CPU to bind the application to in
313 If you are developing an application designed for 10Gb networking,
315 sched_setaffinity & sched_getaffinity to bind your application.
Dcan.txt89 often the need for adaption of large parts of the application to the
108 same received matching CAN frames. An application wishing to
111 write application data byte streams, without having to deal with
120 application would have to do all these operations using ioctl(2)s.
128 provides the character device for the application to work with.
135 application on the one hand, and a interface for hardware-specific
174 application opens a CAN RAW socket, the raw protocol module itself
197 To ensure that application A receives the same information in the
230 Frames that can optionally be passed to the user application in the
234 be requested by the user application using the common CAN filter
[all …]
Dmac80211-injection.txt63 You can also find a link to a complete inject application here:
Dopenvswitch.txt179 But this change would negatively affect a userspace application that
181 The application could, following the flow compatibility rules above,
185 802.1Q header) and it could cause the application's behavior to change
196 nested inside the "encap" attribute. Thus, an application that does
Dscaling.txt230 application locality. This is accomplished by Receive Flow Steering
232 kernel processing of packets to the CPU where the application thread
245 a single application thread handles flows with many different flow hashes.
329 the application thread consuming the packets of each flow is running.
332 will either be the same CPU where the application runs, or at least a CPU
333 which is local to the application thread’s CPU in the cache hierarchy.
Dtproxy.txt25 modify your application to allow it to send datagrams _from_ non-local IP
Ddccp.txt79 size (application payload size) in bytes, see RFC 4340, section 14.
109 always cover the entire packet and that only fully covered application data is
Dudplite.txt16 From here you can also download some example application source code.
246 * application has specified larger min. coverage
Dixgb.txt267 can be increased significantly more if necessary for your application.
374 environments. If this is observed, increasing the application's socket buffer
376 See the specific application manual and /usr/src/linux*/Documentation/
Dtcp.txt26 application rather than the network.
De1000.txt42 parameters, see the application note at:
415 environments. If this is observed, increasing the application's socket buffer
417 See the specific application manual and /usr/src/linux*/Documentation/
Doperstates.txt133 driver. Afterwards, the userspace application can set IFLA_OPERSTATE
Dl2tp.txt110 When creating PPPoL2TP sockets, the application provides information
163 tunnel. There is no need for an L2TP userspace application in this
Dvortex.txt230 Becker's `ether-wake' application may be used to wake suspended
304 3Com's DOS-based application for setting up the NICs EEPROMs:
Dphonet.txt158 "third party" application. This means that both endpoints are passive.
Dbaycom.txt151 leave it to kmod to load the correct driver depending on the application.
/linux-4.4.14/Documentation/ABI/stable/
Dsysfs-driver-w1_ds28e046 Users: any user space application which wants to communicate with DS28E04-100
15 Users: any user space application which wants to communicate with DS28E04-100
Dsysfs-driver-w1_ds28ea006 Users: any user space application which wants to communicate with DS28EA00
Dsysfs-bus-w110 Users: any user space application which wants to know bus scanning
/linux-4.4.14/Documentation/crypto/
Dasync-tx-api.txt18 4.2 "My application needs exclusive control of hardware channels"
79 operations complete. When an application needs to submit a chain of
82 acknowledged by the application before the offload engine driver is allowed to
95 automatically issues pending operations. An application can force this
97 channels since the application has no knowledge of channel to operation
101 There are two methods for an application to learn about the completion
108 called in application context if the operation is carried out
110 async_<operation>, or when the application needs to submit a chain of
177 4.2 "My application needs exclusive control of hardware channels"
Dapi-intro.txt109 as well as general application notes such as RFC2451 ("The ESP CBC-Mode
/linux-4.4.14/Documentation/power/
Dswsusp-and-swap-files.txt30 2) Use an application that will bmap the swap file with the help of the
41 application in 2) (of course, this step may be carried out automatically
42 by the same application that determines the swap file's header offset using the
47 Use a userland suspend application that will set the partition and offset
Dswsusp.txt280 Think of the following: you suspend while an application is running
281 that keeps sensitive data in memory. The application itself prevents
324 Q: If my application(s) causes lots of memory & swap space to be used
/linux-4.4.14/Documentation/filesystems/
Ddnotify.txt8 The basic mechanism involves the application registering for notification
12 The application decides which "events" it wants to be notified about.
23 Usually, the application must reregister after each notification, but
33 Preferably the application will choose one of the real time signals
Dsysfs-pci.txt103 do legacy port I/O. The application should open the file, seek to the desired
106 desired, e.g. 0xa0000 for the VGA frame buffer. The application can then
Dquota.txt28 the above events to userspace. There they can be captured by an application
Drelay.txt76 kernel sides of a relay application. When combined these two sets of
140 In order for a user application to make use of relay files, the
265 of sub-buffers is completely dependent on the application and even for
266 the same application, different conditions will warrant different
469 within the kernel application, such as enabling/disabling logging to
Dfuse.txt245 2) creating a filesystem containing a suid or sgid application,
246 then executing this application
279 whole system. For example a suid application locking a
Dseq_file.txt19 than an application is likely to read in a single operation. Handling
237 file->private_data. If you have an application where the same iterator can
/linux-4.4.14/Documentation/isdn/
DREADME.audio50 the application. See below for data format
83 received from the application via phone line.
87 On incoming calls, if the application responds to a RING
98 starts sending audio data to the application. There are several
129 CONNECT, and starts transferring data from application to the phone line.
DINTERFACE.CAPI7 COMMON-ISDN-API (CAPI) is an application programming interface standard used
16 application registration to an available device, forwarding it to the
18 directions between the application and the hardware driver.
58 parameter structure provided by the application. This is analogous to the
62 application may be passed to the driver for the device via calls to the
65 Kernel CAPI for forwarding to an application, specifying its ApplID.
70 messages for that application may be passed to or from the device anymore.
269 for forwarding to the specified application
342 application up and down events.
/linux-4.4.14/Documentation/
Dsysfs-rules.txt34 application's behavior, but never try to search for sysfs. Never try
57 is a bug in the application
76 bug in the application
82 like the "device"-link, is a bug in the application
123 the application.
130 a bug in the application.
140 a device in /sys/devices/ is a bug in the application.
141 Accessing /sys/class/net/eth0/device is a bug in the application.
151 the application.
163 access the chain of parents is a bug in the application.
Dkernel-per-CPU-kthreads.txt82 3. Once your application has started, prevent CPU-hotplug operations
85 bring it back online before you start your application.)
89 3. Once your application has started, prevent CPU-hotplug operations
92 bring it back online before you start your application.)
96 3. Once your application has started, prevent CPU-hotplug operations
99 bring it back online before you start your application.)
177 application cannot tolerate:
Dhsi.txt17 commonly prefixed by AC for signals going from the application die to the
Ddell_rbu.txt27 The rbu driver needs to have an application (as mentioned above)which will
96 Also after updating the BIOS image a user mode application needs to execute
Dunshare.txt35 its simplicity but also from allowing application programmers to work
53 unshare would be useful to large application frameworks such as PAM
78 Consider a client/server application where the server is processing
84 request. For large and complex middleware application frameworks, this
Dpi-futex.txt25 improve the statistical distribution of locking related application
43 Media players (such as Jack) are an example of reasonable application
Ddcdbas.txt25 the SMI and provides a way for the application to generate the SMI.
Djava.txt19 as the application itself).
380 Now compile the application with:
Dstable_api_nonsense.txt10 the one that application programs use, the syscall interface. That
14 that users and application programmers can count on being stable.
Drfkill.txt105 After an application opens /dev/rfkill, it can read the current state of all
Dvgaarbiter.txt17 ideally, being a userspace application, it is not the role of the X server to
/linux-4.4.14/Documentation/misc-devices/mei/
Dmei.txt15 communication channel between a host application and the Intel ME feature.
42 HTTP/S that are received from a remote management console application.
53 An application maintains communication with an Intel ME feature while
65 and host application.
71 A code snippet for an application communicating with Intel AMTHI client:
181 local application using the same network interface as a remote application
184 When a local application sends a message addressed to the local Intel AMT host
198 single application.
/linux-4.4.14/scripts/coccinelle/misc/
Dnoderef.cocci58 cocci.print_main("application of sizeof to pointer",p)
64 msg = "ERROR: application of sizeof to pointer"
/linux-4.4.14/drivers/staging/most/Documentation/
Ddriver_usage.txt27 core layer and the application layer. The core layer consists of the core
36 USB, MediaLB, I2C). A module of the application layer is referred to as an
37 AIM (application interfacing module). The modules of this layer give access
76 The application layer contains so called application interfacing modules (AIM).
77 Depending on how the driver should interface to the application, one or more
80 The AIMs encapsulate the application interface specific knowledge of the driver
/linux-4.4.14/Documentation/block/
Ddata-integrity.txt8 application tried to write is most likely lost.
11 application meant it to. Recent additions to both the SCSI family
64 generated by Linux or the application at very low cost (comparable to
86 they enable us to protect the entire path from application to storage
94 transport protocols completely transparent to the application.
99 It is completely unreasonable for an application to be aware whether
103 from the application. As far as the application (and to some extent
156 the protection data, as well as getting and setting application tags.
163 will require extra work due to the application tag.
191 attached. It can also use the application tag space if this is
Dcmdline-partition.txt27 partition name, kernel send uevent with "PARTNAME". application can create
29 user space application can access partition by partition name.
/linux-4.4.14/Documentation/pti/
Dpti_intel_mid.txt22 the user-space application shuts down (plus avoids
31 *Hook /dev/pti to a user-level debugging application for writing
37 Below is example pseudo-code on how a 'privileged' application
39 a system. 'Privileged' means the application has enough
/linux-4.4.14/Documentation/dvb/
Dci.txt16 (2) one requires a userspace application, ca_zap. This small userland
17 application is in charge of sending the descrambling related information
20 This application requires the following to function properly as of now.
72 the application programmer it would be as simple as sending/receiving an
109 application. The driver/hardware will take care of all that.
113 exist in this case in the application to driver communication. It is
Dfaq.txt27 you can use to watch TV with any v4l application. xawtv is known
29 have to zap using [sct]zap. If you want a nice application for
41 a nice DVB application which includes a builtin software MPEG
DREADME.dvb-usb159 At this point you should be able to start a dvb-capable application. I'm use
165 - Don't remove the USB device while running an DVB application, your system
/linux-4.4.14/Documentation/hwmon/
Dsch563632 An application note describing the Theseus' registers, as well as an
33 application note describing the protocol for communicating with the
Dsch562725 through an embedded microcontroller. An application note describing the
Dabituguru351 with a custom Abit application running on it.
Dabituguru82 W83L950D is a generic microcontroller with a custom Abit application running
Dadm102690 The datasheet shows an example application with VID signals attached to
/linux-4.4.14/Documentation/sound/alsa/
Dtimestamping.txt14 event or application query.
23 the application needs:
65 The app time corresponds to the time tracked by an application after
68 The application can query what the hardware supports, define which
78 In case the application requests an audio tstamp that is not supported
92 information on how much the application pointer can be rewound
115 application, the audio_tstamp_config can be changed dynamically. In
117 any application selection. To work around this limitation without
Dhdspm.txt72 result), but if MMAP is used by the application. Therefore it
104 conversion. A test-application shows the usage of the controller.
127 frequency or slave), since even not using an Audio-application
346 note: Use only when the application supports this (which is a special case).
DOSS-Emulation.txt119 In such a case, you can change the behavior of PCM per application by
130 app_name is the name of application with (higher priority) or without
138 disable the application tries to open a pcm device for
147 capture) is not handled correctly by the application although the
/linux-4.4.14/Documentation/s390/
Dzfcpdump.txt42 The user space application of zfcpdump can reside in an intitramfs or an
43 initrd. It can also be included in a built-in kernel initramfs. The application
47 initramfs with a user space application that writes the dump to a SCSI
Dmonreader.txt168 EIO: reply failed, read data is invalid and the application
170 EFAULT: copy_to_user failed, read data is invalid and the application should
179 (EIO, EFAULT) there will be missing data. It's up to the application if it will
D3270.txt29 workstation. With the DEF GRAF command, an application such as xterm,
203 Running" and nothing typed, the application receives a newline.)
219 PA1 causes a SIGINT to the currently running application. You may do
225 PF3 causes an EOF to be received as input by the application. You may
/linux-4.4.14/Documentation/blockdev/drbd/
Ddrbd-connection-state-overview.dot39 label="new application (WRITE?) requests blocked\lwhile bitmap is exchanged"
48 …pe=record,label="{<any>resynchronisation process running\l'concurrent' application requests allowe…
/linux-4.4.14/drivers/staging/media/davinci_vpfe/
DTODO34 for building application).
37 for building application).
/linux-4.4.14/drivers/hsi/
DKconfig9 application engines and cellular modems.
/linux-4.4.14/Documentation/hid/
Dhiddev.txt100 This ioctl call returns the HID application usage associated with the
101 hid device. The third argument to ioctl() specifies which application
103 application collection. If the index is invalid (greater or equal to
104 the number of application collections this device has) the ioctl
105 returns -1. You can find out beforehand how many application
111 application collections, but all the collections the device has. It
Dhid-sensor.txt153 an application/driver to determine what data is being communicated by the sensor.
158 To allow application to utilize these sensors, here they are exported uses sysfs
Dhidraw.txt9 Hidraw should be used if the userspace application knows exactly how to
/linux-4.4.14/drivers/isdn/hardware/eicon/
Dcapifunc.c26 APPL *application = (APPL *) NULL; variable
769 if (application[appl - 1].Id == appl) { in diva_register_appl()
814 this = &application[appl - 1]; in diva_register_appl()
851 APPL *this = &application[appl - 1]; in diva_release_appl()
885 APPL *this = &application[GET_WORD(&msg->header.appl_id) - 1]; in diva_send_message()
1137 if (!(application = diva_os_malloc(0, sizeof(APPL) * MAX_APPL))) { in init_main_structs()
1143 memset(application, 0, sizeof(APPL) * MAX_APPL); in init_main_structs()
1153 if (application) in remove_main_structs()
1154 diva_os_free(0, application); in remove_main_structs()
Dmessage.c247 extern APPL *application;
1560 sendf(&application[i], _DISCONNECT_I, Id, 0, "w", _OTHER_APPL_CONNECTED); in connect_res()
1594 sendf(&application[i], _DISCONNECT_I, Id, 0, "w", 0); in disconnect_req()
3361 sendf(&application[i], _DISCONNECT_I, Id, 0, "w", _OTHER_APPL_CONNECTED); in select_b_req()
4676 if (application[i].CDEnable) in control_rc()
4678 if (!application[i].Id) application[i].CDEnable = 0; in control_rc()
4681 sendf(&application[i], _FACILITY_R | CONFIRM, Id, in control_rc()
4683 if (Info) application[i].CDEnable = 0; in control_rc()
5177 if (application[i].CDEnable) in sig_ind()
5179 if (application[i].Id) sendf(&application[i], _FACILITY_I, Id, 0, "ws", 3, SS_Ind); in sig_ind()
[all …]
/linux-4.4.14/Documentation/arm/sti/
Dstih418-overview.txt8 and server/connected client application for satellite, cable, terrestrial
Dstih407-overview.txt8 and server/connected client application for satellite, cable, terrestrial
/linux-4.4.14/Documentation/devicetree/bindings/mips/brcm/
Dsoc.txt12 BMIPS4355 cable modem CPU instead of the BMIPS5000 application processor.
/linux-4.4.14/Documentation/video4linux/
Dmeye.txt102 application). The argument to MEYEIOC_QBUF_CAPT is the
109 for the application to use. It returns the buffer size.
118 Look at the 'motioneye' application code for an actual example.
Dsi470x.txt12 Part of this reference design is also a radio application in binary and source
49 Testing is usually done with most application under Debian/testing:
54 - radio - ncurses-based radio application
DREADME.cpia29 an mjpeg enabled application can be used with the camera. We have modified the
10 gqcam application to view this stream.
115 We are providing a modified gqcam application to view the output. In
Domap3isp.txt85 application using the VIDIOC_OMAP3ISP_STAT_REQ IOCTL. The events available
236 written back to user application.
243 space application will be an unique value associated to that request. When
244 user application receives an event for buffer availability or when a new
Duvcvideo.txt27 The second mechanism requires uvcvideo-specific knowledge for the application to
65 hardcoded in the application or queried using other ways such as by parsing the
79 application developers are encouraged to use UVCIOC_CTRL_QUERY instead.
DREADME.davinci-vpbe42 selection or at run time when application change the output through
Dvivid.txt16 allows you to use this driver as a test input for application development, since
247 the driver behavior and test your application with all sorts of permutations.
464 interface to pass the RDS blocks on to the application for decoding.
528 allow you to check if your application can handle such things correctly.
851 by the application, or "Controls" where the RDS data is provided by
871 RDS Tx I/O Mode: this can be "Block I/O" where the application has to use write()
967 This allows you to test your application for all these variations.
1013 Video output will also honor any data_offset that the application set.
Dpxa_camera.txt25 userland application.
DREADME.ivtv16 an application that can handle MPEG input such as mplayer, xine, MythTV,
Dvideobuf196 if they are needed to satisfy the count requested by the application. A
267 user-space pages and will be very scattered indeed. If the application is
/linux-4.4.14/drivers/hsi/controllers/
DKconfig11 an application engine with a cellular modem.
/linux-4.4.14/net/irda/ircomm/
DKconfig10 infrared link. Thus you should be able to use application like PPP,
/linux-4.4.14/Documentation/powerpc/
Dcxlflash.txt8 purpose co-processors which can read or write an application's
23 user space application direct access to Flash storage.
56 initial setup before the user application is allowed to send requests
84 Once these scsi block devices are instantiated, an application
100 and the entire space for the LUN is available to the application.
103 data written to the block device will survive application exit and
105 not survive after the application terminates or the system reboots).
282 where the changes affect the application (such as a LUN resize), the
283 cxlflash driver will report the changed state to the application.
Dqe_firmware.txt91 This structure contains 6 words that the application should copy to some
128 | | push command | given by the application, the software must |
Dhvcs.txt197 Attempting to connect an application to /dev/hvcs* prior to insertion of
234 used to launch the interactive I/O application. If one is using xterm and
241 session before disconnecting an application such as kermit from the device
/linux-4.4.14/drivers/spmi/
DKconfig8 serial interface between baseband and application processors
/linux-4.4.14/drivers/media/platform/marvell-ccic/
DKconfig23 controller found on Marvell Armada 610 application
/linux-4.4.14/Documentation/devicetree/bindings/mfd/
Dmax77802.txt5 up application processors and peripherals, a 2-channel 32kHz clock outputs,
/linux-4.4.14/sound/usb/line6/
DKconfig19 audio application
/linux-4.4.14/net/rxrpc/
DKconfig13 left to the application).
/linux-4.4.14/drivers/parisc/
DREADME.dino24 ** "The pci_check program will also be available as application
/linux-4.4.14/drivers/of/unittest-data/
Dtests-overlay.dtsi185 /* test overlays application and removal in sequence */
203 /* test overlays application and removal in bad sequence */
/linux-4.4.14/include/uapi/linux/
Dhiddev.h98 __u32 application; /* application usage for this field */ member
/linux-4.4.14/arch/x86/boot/
Dheader.S174 .word 0xa # Subsystem (EFI application)
217 # The EFI application loader requires a relocation section
/linux-4.4.14/Documentation/watchdog/
Dhpwdt.txt15 is, an application needs to be started that kicks off the watchdog timer. A
16 basic application exists in the Documentation/watchdog/src directory called
/linux-4.4.14/Documentation/security/
DYama.txt15 running state of any of their processes. For example, if one application
35 In mode 1, software that has defined application-specific relationships
Dkeys-trusted-encrypted.txt58 application specific, which is identified by 'format'.
DSmack.txt614 You will often find that your labeled application has to talk to the outside,
620 It means that your application will have unlabeled access to @IP1 if it has
628 @ means Internet, any application with any label has access to it
645 application interacts with Smack will determine what it will have to do to
739 Bringup mode provides logging features that can make application
/linux-4.4.14/Documentation/x86/
Dintel_mpx.txt31 is how we expect the compiler, application and kernel to work together.
51 4) If the application needs to spill bounds out of the 4 registers, it
56 5) If the application violates the bounds specified in the bounds registers,
68 * inserts code early in the application to call in to the "gcc runtime"
129 A: MPX-enabled application will possibly create a lot of bounds tables in
/linux-4.4.14/Documentation/devicetree/bindings/soc/rockchip/
Dpower_domain.txt4 powered up/down by software based on different application scenes to save power.
/linux-4.4.14/Documentation/serial/
Dmoxa-smartio454 application, for example, sending AT command to a modem connected to the
469 spd_hi Use 57.6kb when the application requests 38.4kb.
470 spd_vhi Use 115.2kb when the application requests 38.4kb.
471 spd_shi Use 230.4kb when the application requests 38.4kb.
472 spd_warp Use 460.8kb when the application requests 38.4kb.
473 spd_normal Use 38.4kb when the application requests 38.4kb.
475 application requests 38.4kb.
/linux-4.4.14/Documentation/fmc/
DFMC-and-SDB.txt43 In the typical application the mezzanine is mostly analog while the
45 match the specific mezzanine and the desired application. Thus, you may
Dfmc-write-eeprom.txt12 However, since the EEPROM may include application-specific information
/linux-4.4.14/Documentation/arm64/
Dtagged-pointers.txt14 this byte for application use, with the following caveats:
Dlegacy_instructions.txt57 be unexpected results in the application.
/linux-4.4.14/Documentation/devicetree/bindings/reset/
Dnxp,lpc1850-rgu.txt56 56 ARM Cortex-M0 application core (LPC4370 only)
/linux-4.4.14/Documentation/ia64/
Derr_inject.txt10 The tool includes two parts: a kernel driver and a user application
13 arch/ia64/kernel/err_inject.c. The application sample (shown below)
22 Below is a sample application as part of the whole tool. The sample
25 application to have more thorough test.
27 The sample application takes err.conf as error configuration input. GCC
29 this sample application to inject errors.
64 The sample application source code:
/linux-4.4.14/Documentation/misc-devices/
Dad525x_dpot.txt8 interpretation of this settings is required by the end application according to
Dspear-pcie-gadget.txt121 An application can repetitively read this node till link is found UP. It can
/linux-4.4.14/Documentation/video4linux/bttv/
DREADME.WINVIEW11 I don't yet have any application to test the radio support. The tuner
DREADME.freeze21 console and let some terminal application log the messages. /me uses
/linux-4.4.14/Documentation/devicetree/bindings/pci/
Dpci-keystone.txt15 reg: index 1 is the base address and length of DW application registers.
/linux-4.4.14/security/selinux/
DKconfig85 by the application or the protection that will be applied by the
90 default to checking the protection requested by the application.
/linux-4.4.14/Documentation/fb/
Dframebuffer.txt12 represents the frame buffer of some video hardware and allows application
98 All this hardware abstraction makes the implementation of application programs
103 application programs is the screen organization (bitplanes or chunky pixels
128 The X server (XF68_FBDev) is the most notable application program for the frame
Dpxafb.txt123 framebuffer framework, application has to take care of the offsets
Dapi.txt154 application modifies the format.
238 long time and is thus widely used by application. It is the recommended API
Dudlfb.txt69 application must send down damage notifcations to trigger repaints of the
Dviafb.txt170 device node file, thus a user mode application can't access it directly.
/linux-4.4.14/Documentation/usb/
Dlinux-cdc-acm.inf83 ; application program and the firmware on the microcontroller must match.
Diuu_phoenix.txt10 used by your favorite application to pilot the IUU
/linux-4.4.14/Documentation/vm/
Dksm.txt16 application which generates many instances of the same data.
23 KSM only operates on those areas of address space which an application
Dnuma38 application software must arrange for a large majority of the memory references
64 application features on non-NUMA platforms, and as a sort of memory resource
107 System administrators and application designers can restrict a task's migration
Dsoft-dirty.txt35 including soft dirty bits. To notify user space application about such
Dhwpoison.txt60 Send SIGBUS to the application as soon as the error is detected
66 Send SIGBUS when the application runs into the corrupted page.
Dtranshuge.txt25 runtime of the application. The second factor consist of two
80 In certain cases when hugepages are enabled system wide, application
81 may end up allocating more memory resources. An application may mmap a
190 == Need of application restart ==
194 application that could have been using hugepages. This also applies to
/linux-4.4.14/arch/blackfin/
DKconfig.debug44 can cause the wrong application, or even the kernel to receive a
110 can be handy when an application dies - we print out the execution
191 space when in reality an application is buggy.
/linux-4.4.14/kernel/
DKconfig.preempt25 latency of rescheduling, providing faster application reactions,
/linux-4.4.14/Documentation/w1/masters/
Domap-hdq20 A typical application of the HDQ/1-Wire module is the communication with battery
/linux-4.4.14/Documentation/arm/
Duefi.txt28 PE/COFF executable, including a loader application that makes it possible to
/linux-4.4.14/Documentation/leds/
Dledtrig-oneshot.txt6 trigger, the application needs only to signal the trigger when an event has
Dledtrig-transient.txt15 set a timer to hold a state, however when user space application crashes or
/linux-4.4.14/drivers/block/drbd/
DKconfig25 On the node with the primary device the application is supposed to
/linux-4.4.14/scripts/
Dspelling.txt75 allpication||application
94 aplication||application
96 applicaion||application
97 appliction||application
/linux-4.4.14/Documentation/w1/
Dw1.netlink178 Sequence number for userspace requests is set by userspace application.
188 This archive includes userspace application w1d.c which uses
/linux-4.4.14/Documentation/ABI/obsolete/
Dsysfs-driver-hid-roccat-arvo35 windows and application keys, to protect the user from the outcome
/linux-4.4.14/Documentation/scsi/
Dosd.txt6 called objects. Objects are intended to contain operating system and application
57 osd_test.c User-mode application to call the kernel tests
DChangeLog.megaraid_sas222 e). In driver's IOCTL routine, the application cmds will wait for the
229 application which driver will support the device update. So application
230 will not need to do the device update after application add/del the device
DChangeLog.arcmsr62 ** inconsistency with sg_mod driver if application directly calls
DChangeLog.megaraid88 application communicates with MegaRAID HBA driver.
294 capacity, application shall now use the device attribute to get the
469 addresses in application mailbox and passthru structures.
/linux-4.4.14/Documentation/devicetree/bindings/soc/fsl/
Dbman.txt89 not the specific needs of an application
Dqman.txt106 capabilities and not the specific needs of an application
/linux-4.4.14/drivers/scsi/
Dgdth_ioctl.h175 u8 application; member
Dgdth.c160 static void gdth_readapp_event(gdth_ha_str *ha, u8 application,
2878 e->application = 0; in gdth_store_event()
2916 u8 application, gdth_evt_str *estr) in gdth_readapp_event() argument
2923 TRACE2(("gdth_readapp_event() app. %d\n", application)); in gdth_readapp_event()
2930 if ((e->application & application) == 0) { in gdth_readapp_event()
2931 e->application |= application; in gdth_readapp_event()
/linux-4.4.14/Documentation/devicetree/bindings/input/touchscreen/
Dti-tsc-adc.txt6 ti,wires: Wires refer to application modes i.e. 4/5/8 wire touchscreen
/linux-4.4.14/net/irda/
DKconfig21 will need to install some OBEX application, such as OpenObex :
/linux-4.4.14/tools/perf/Documentation/
Dperf-timechart.txt30 There are also poll bars which show how much time application spent
/linux-4.4.14/Documentation/devicetree/bindings/mmc/
Dti-omap-hsmmc.txt95 not every application needs SDIO irq, e.g. MMC cards.
/linux-4.4.14/Documentation/sound/alsa/soc/
Doverview.txt37 core and are subsequently matched and configured when the application
/linux-4.4.14/Documentation/bus-devices/
Dti-gpmc.txt6 * Asynchronous SRAM like memories and application specific integrated
/linux-4.4.14/drivers/staging/unisys/Documentation/ABI/
Dsysfs-platform-visorchipset57 Description: This entry is used by Unisys application software on the guest
/linux-4.4.14/tools/power/cpupower/bench/
DREADME-BENCH122 Due to the high priority, the application may not be responsible for some time.
/linux-4.4.14/Documentation/scheduler/
Dsched-deadline.txt482 The first testing application is called rt-app and can be used to
510 The second testing application is a modification of schedtool, called
512 certain pid/application. schedtool-dl is available at:
522 application, given that you know its pid:
531 application developer.
/linux-4.4.14/drivers/staging/most/Documentation/ABI/
Dsysfs-class-most.txt60 name is dictated by the HDM. This enables an application to
/linux-4.4.14/Documentation/devicetree/bindings/arm/msm/
Dqcom,idle-state.txt56 complete application processor subsystem shut down.
/linux-4.4.14/drivers/hid/usbhid/
Dhiddev.c774 finfo.application = field->application; in hiddev_ioctl()
/linux-4.4.14/Documentation/thermal/
Dsysfs-api.txt24 An intelligent thermal management application can make decisions based on
249 algorithm or user space application.
252 trip points so that user application can take full
/linux-4.4.14/net/netfilter/ipvs/
DKconfig59 to your virtual server application. It is good to set the table size
269 comment 'IPVS application helper'
/linux-4.4.14/Documentation/ide/
DChangeLog.ide-tape.1995-2002202 * Also, sometimes an application finishes but the
210 * if the application data rate is higher than 1100 KB/s;
/linux-4.4.14/Documentation/devicetree/bindings/arm/
Darm,scpi.txt59 A small area of SRAM is reserved for SCPI communication between application
/linux-4.4.14/drivers/uio/
DKconfig150 A sample userspace application using this driver is available
/linux-4.4.14/Documentation/devicetree/bindings/i2c/
Dtrivial-devices.txt51 dlg,da9063 DA9063: system PMIC for quad-core application processors
/linux-4.4.14/include/linux/netfilter/
Dnf_conntrack_h323_types.h77 DataApplicationCapability_application application; member
/linux-4.4.14/Documentation/console/
Dconsole.txt83 unbinding will not succeed. An example of an application that sets the console
/linux-4.4.14/drivers/firmware/
DKconfig93 supporting application to communicate with the BIOS regarding the new
/linux-4.4.14/arch/m68k/ifpsp060/
Dos.S58 | or supervisor application space. The examples below use simple "move"
/linux-4.4.14/Documentation/acpi/apei/
Deinj.txt146 from the BIOS that hopefully will allow an application wishing to use
/linux-4.4.14/Documentation/connector/
Dconnector.txt152 with a different group number, the userspace application must subscribe to
/linux-4.4.14/Documentation/device-mapper/
Dcache-policies.txt61 promote sequential blocks to the cache (e.g. fast application startup).

12