Home
last modified time | relevance | path

Searched refs:application (Results 1 – 25 of 721) sorted by relevance

12345678910>>...29

/linux-6.15/net/bluetooth/cmtp/
H A Dcapi.c206 if (application) { in cmtp_recv_interopmsg()
208 application->msgnum = 0; in cmtp_recv_interopmsg()
219 if (application) { in cmtp_recv_interopmsg()
221 application->msgnum = 0; in cmtp_recv_interopmsg()
327 if (application) { in cmtp_recv_capimsg()
328 appl = application->appl; in cmtp_recv_capimsg()
376 if (!application) { in cmtp_register_appl()
409 err = -application->err; in cmtp_register_appl()
440 if (!application) { in cmtp_release_appl()
447 cmtp_send_interopmsg(session, CAPI_REQ, application->mapping, application->msgnum, in cmtp_release_appl()
[all …]
/linux-6.15/tools/testing/selftests/hid/tests/
H A Dbase_gamepad.py59 def __init__(self, rdesc, application="Game Pad", name=None, input_info=None): argument
61 super().__init__(name, application, input_info=input_info, rdesc=rdesc)
71 if r.application_name == self.application:
88 application="Game Pad", argument
146 gamepad, reportID=reportID, application=application
199 def __init__(self, rdesc, application="Joystick", name=None, input_info=None): argument
200 super().__init__(rdesc, application, name, input_info)
210 application=None, argument
226 if application is None:
227 application = "Joystick"
[all …]
H A Dbase_device.py244 if application in matches:
245 return matches[application].is_a_match(self.libevdev)
281 application, argument
299 self.application = application
345 def match_evdev_rule(self, application, evdev): argument
378 def next_sync_events(self, application=None): argument
379 evdev = self.get_evdev(application)
392 def get_evdev(self, application=None): argument
393 if application is None:
394 application = self.application
[all …]
H A Dtest_ite_keyboard.py135 def event(self, keys, reportID=None, application=None): argument
136 application = application or "Keyboard"
137 return super().event(keys, reportID, application)
/linux-6.15/drivers/hid/
H A Dwacom_wac.h171 ((f)->application == HID_DG_PEN) || \
172 ((f)->application == HID_DG_DIGITIZER) || \
173 ((f)->application == WACOM_HID_WD_PEN) || \
174 ((f)->application == WACOM_HID_WD_DIGITIZER) || \
175 ((f)->application == WACOM_HID_G9_PEN) || \
176 ((f)->application == WACOM_HID_G11_PEN))
179 ((f)->application == HID_DG_TOUCHSCREEN) || \
182 ((f)->application == WACOM_HID_WT_TOUCHPAD) || \
183 ((f)->application == HID_DG_TOUCHPAD))
187 ((f)->application == HID_DG_PEN) || \
[all …]
H A Dhid-multitouch.c117 unsigned int application; member
442 application->quirks = val; in mt_set_quirks()
571 unsigned int application = report->application; in mt_allocate_application() local
579 mt_application->application = application; in mt_allocate_application()
606 unsigned int application = report->application; in mt_find_application() local
610 if (application == tmp->application) { in mt_find_application()
639 if (!rdata->application) { in mt_allocate_report_data()
1369 application = rdata->application; in mt_input_mapping()
1415 application); in mt_input_mapping()
1655 switch (hi->application) { in mt_input_configured()
[all …]
H A Dhid-plantronics.c57 int allow_consumer = field->application == HID_CP_CONSUMERCONTROL && in plantronics_input_mapping()
62 if (field->application == HID_GD_JOYSTICK) in plantronics_input_mapping()
92 !((field->application ^ plt_type) & HID_USAGE_PAGE)) in plantronics_input_mapping()
116 usage->hid, field->application); in plantronics_input_mapping()
121 usage->hid, field->application); in plantronics_input_mapping()
127 usage->hid, field->application, mapped_key); in plantronics_input_mapping()
/linux-6.15/Documentation/userspace-api/media/v4l/
H A Dvidioc-subdev-enum-mbus-code.rst34 This call is used by the application to access the enumeration
74 application.
78 Filled in by the application.
116 encoding. The application can ask to configure the colorspace of the
123 The application can ask to configure the transform function of
129 - The driver allows the application to try to change the default Y'CbCr
130 encoding. The application can ask to configure the Y'CbCr encoding of the
136 - The driver allows the application to try to change the default HSV
137 encoding. The application can ask to configure the HSV encoding of the
143 - The driver allows the application to try to change the default
[all …]
H A Dpixfmt-v4l2.rst69 the value requested by the application, returning ``width`` times
111 by the driver for capture streams and by the application for
113 flag ``V4L2_PIX_FMT_FLAG_SET_CSC`` then the application can set
155 the driver for capture streams and by the application for output
156 streams, see :ref:`colorspaces`. If the application sets the
157 flag ``V4L2_PIX_FMT_FLAG_SET_CSC`` then the application can set
169 the driver for capture streams and by the application for output
171 ``V4L2_PIX_FMT_FLAG_SET_CSC`` then the application can set this
185 the driver for capture streams and by the application for output
187 ``V4L2_PIX_FMT_FLAG_SET_CSC`` then the application can set
[all …]
H A Dvidioc-enum-fmt.rst87 - Number of the format in the enumeration, set by the application.
101 - Type of the data stream, set by the application. Only these types
141 application. Only applicable to drivers that advertise the
207 - The driver allows the application to try to change the default
209 The application can ask to configure the colorspace of the capture device
214 - The driver allows the application to try to change the default
216 The application can ask to configure the transfer function of the capture
221 - The driver allows the application to try to change the default
228 - The driver allows the application to try to change the default
235 - The driver allows the application to try to change the default
[all …]
H A Duserp.rst19 methods. Buffers (planes) are allocated by the application itself, and
55 area of memory. This happens transparently to the application in the
69 the application's free list and subsequently reused for other purposes,
74 application waits until a filled buffer can be dequeued, and re-enqueues
77 started. In the write loop, when the application runs out of free
79 Two methods exist to suspend execution of the application until one or
97 application needs to synchronize with another event it should examine
117 because an application may share them with other processes.
H A Dvidioc-enum-framesizes.rst48 (zero-based) is valid. The application should increase the index by
67 When the application calls the function with index zero, it must check
79 without any interaction from the application itself. This means that the
80 enumeration data is consistent if the application does not perform any
87 the application, *OUT* denotes values that the driver fills in. The
88 application should zero out all members except for the *IN* fields.
/linux-6.15/Documentation/ABI/testing/
H A 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
H A Dsysfs-class-fc5 This interface allows an admin to set an FC application
8 an application or logical entity such as a virtual
9 machine or container group. The application or logical
13 entities can utilize the application id and FC traffic
25 If an admin wants to remove an FC application identifier
H A Dsysfs-driver-w1_therm13 Users: any user space application which wants to communicate with
29 Users: any user space application which wants to communicate with
43 Users: any user space application which wants to communicate with
65 Users: any user space application which wants to communicate with
86 Users: any user space application which wants to communicate with
107 Users: any user space application which wants to communicate with
135 Users: any user space application which wants to communicate with
163 Users: An application using the w1_term device
190 Users: An application using the w1_term device
/linux-6.15/Documentation/networking/device_drivers/wwan/
H A Diosm.rst13 MBIM protocol [1]. Any front end application ( eg: Modem Manager) could easily
21 application to detect port enumeration and enable MBIM functionality.
23 Examples of few such userspace application are:
34 Management application development
51 The userspace application is responsible for all control message fragmentation
56 The MBIM control messages from the management application must not exceed the
61 The management application must accept control messages of up the negotiated
74 The userspace management application is responsible for creating new IP link
/linux-6.15/Documentation/networking/
H A Dkcm.rst8 interface over TCP for generic application protocols. With KCM an application
9 can efficiently send and receive application protocol messages over TCP using
75 of a received message can be deduced from the application protocol header
93 using the socket. When the application gets the error notification for a
195 if an application thread knows that it will be doing a lot of
223 KCM accelerates application layer protocols. Specifically, it allows
238 parallelized). In an application, a KCM socket can be opened for each
255 On transmit, there are three ways an application can batch (pipeline)
272 An application should include a thread to monitor errors raised on
276 on the socket thus waking up the application thread. When the application
[all …]
H A Dcdc_mbim.rst46 userspace MBIM management application always is required to enable a
55 management application:
62 Management application development
79 application. It is therefore up to this application to ensure that it
101 The userspace application can access the CDC MBIM functional
110 The userspace application is responsible for all control message
116 The MBIM control messages from the management application *must not*
122 The management application *must* accept control messages of up the
183 The userspace management application is responsible for adding new
210 assumption is that a userspace application initiating a DSS session
[all …]
H A Dtcp-thin.rst9 that the application sends data with such a low rate that the
15 dependency on the arrival of new data from the application to trigger
25 In order to reduce application-layer latency when packets are lost,
40 they must be specifically activated by the application using the
/linux-6.15/Documentation/misc-devices/
H A Dibmvmc.rst38 In the management partition, a management application exists which enables
43 The management application runs on a Linux logical partition on a
47 application using a combination of HMC to hypervisor interfaces and
51 application component are passed to the hypervisor over a VMC interface,
68 for communicating between the management application and the hypervisor. It
107 This section provides an example for the management application
122 which will be used for management application session initialization.
177 During normal runtime, the management application and the hypervisor
179 sending data to the hypervisor, the management application performs a
188 and passes the data up to the appropriate management application via a
[all …]
/linux-6.15/Documentation/arch/arm/
H A Dmarvell.rst308 Dove family (application processor)
315 …https://web.archive.org/web/20111102020643/http://www.marvell.com/application-processors/armada-50…
318 …https://web.archive.org/web/20160428160231/http://www.marvell.com/application-processors/armada-50…
321 …https://web.archive.org/web/20120130172443/http://www.marvell.com/application-processors/armada-50…
324 …https://web.archive.org/web/20160822232651/http://www.marvell.com/application-processors/armada-50…
341 … : https://web.archive.org/web/20150927135510/http://www.marvell.com/application-processors/pxa-…
344 … : https://web.archive.org/web/20140211221535/http://www.marvell.com/application-processors/pxa-…
354 … : https://web.archive.org/web/20130727144559/http://www.marvell.com/application-processors/pxa-…
385 … : https://web.archive.org/web/20110926014256/http://www.marvell.com/application-processors/arma…
386 … : https://web.archive.org/web/20111102030100/http://www.marvell.com/application-processors/arma…
[all …]
/linux-6.15/Documentation/iio/
H A Diio_tools.rst13 * lsiio: example application that provides a list of IIO devices and triggers
14 * iio_event_monitor: example application that reads events from an IIO device
16 * iio_generic_buffer: example application that reads data from buffer
/linux-6.15/Documentation/admin-guide/cgroup-v1/
H A Dnet_prio.rst9 Nominally, an application would set the priority of its traffic via the
12 1) The application may not have been coded to set this value
13 2) The priority of application traffic is often a site-specific administrative
14 decision rather than an application defined one.
52 One usage for the net_prio cgroup is with mqprio qdisc allowing application
/linux-6.15/Documentation/networking/devlink/
H A Dsfc.rst44 - SmartNIC application co-processor (APU) first stage boot loader version.
47 - SmartNIC application co-processor (APU) co-operating system loader version.
50 - SmartNIC application co-processor (APU) main operating system version.
53 - SmartNIC application co-processor (APU) recovery operating system version.
/linux-6.15/Documentation/devicetree/bindings/remoteproc/
H A Dti,pru-consumer.yaml13 A PRU application/consumer/user node typically uses one or more PRU device
14 nodes to implement a PRU application/functionality. Each application/client
20 The application nodes shall define their own bindings like regular platform

12345678910>>...29