| /OK3568_Linux_fs/buildroot/board/rockchip/rk3566_rk3568/fs-overlay/usr/share/matrix-gui-2.0/ |
| H A D | json.txt | 1 …application","Exec":"fltest_qt_audiorecorder","ProgramType":"gui","Description_Link":-1,"Lock":-1,…
|
| /OK3568_Linux_fs/kernel/net/bluetooth/cmtp/ |
| H A D | capi.c | 77 BT_DBG("session %p application %p appl %d", session, app, appl); in cmtp_application_add()
92 BT_DBG("session %p application %p", session, app); in cmtp_application_del()
187 struct cmtp_application *application; in cmtp_recv_interopmsg() local
205 application = cmtp_application_get(session, CMTP_MSGNUM, msgnum); in cmtp_recv_interopmsg()
206 if (application) { in cmtp_recv_interopmsg()
207 application->state = BT_CONNECTED; in cmtp_recv_interopmsg()
208 application->msgnum = 0; in cmtp_recv_interopmsg()
209 application->mapping = CAPIMSG_APPID(skb->data); in cmtp_recv_interopmsg()
218 application = cmtp_application_get(session, CMTP_MAPPING, appl); in cmtp_recv_interopmsg()
219 if (application) { in cmtp_recv_interopmsg()
[all …]
|
| /OK3568_Linux_fs/external/security/rk_tee_user/v2/export-ta_arm32/include/ |
| H A D | tee_ta_api.h | 19 * Each Trusted Application must provide the Implementation with a number
25 * Trusted Application Entry Points:
29 * The function TA_CreateEntryPoint is the Trusted Application's
31 * the Trusted Application. To register instance data, the implementation
50 * The function TA_DestroyEntryPoint is the Trusted Application‟s
73 * requests to open a session with the Trusted Application. The open
74 * session request may result in a new Trusted Application instance being
78 * to the Trusted Application instance in the arguments paramTypes and
79 * params. These arguments can also be used by the Trusted Application
84 * Trusted Application instance and can invoke Trusted Application
[all …]
|
| /OK3568_Linux_fs/external/security/rk_tee_user/v2/export-ta_arm64/host_include/ |
| H A D | tee_ta_api.h | 19 * Each Trusted Application must provide the Implementation with a number
25 * Trusted Application Entry Points:
29 * The function TA_CreateEntryPoint is the Trusted Application's
31 * the Trusted Application. To register instance data, the implementation
50 * The function TA_DestroyEntryPoint is the Trusted Application‟s
73 * requests to open a session with the Trusted Application. The open
74 * session request may result in a new Trusted Application instance being
78 * to the Trusted Application instance in the arguments paramTypes and
79 * params. These arguments can also be used by the Trusted Application
84 * Trusted Application instance and can invoke Trusted Application
[all …]
|
| /OK3568_Linux_fs/external/security/rk_tee_user/v2/export-ta_arm64/include/ |
| H A D | tee_ta_api.h | 19 * Each Trusted Application must provide the Implementation with a number
25 * Trusted Application Entry Points:
29 * The function TA_CreateEntryPoint is the Trusted Application's
31 * the Trusted Application. To register instance data, the implementation
50 * The function TA_DestroyEntryPoint is the Trusted Application‟s
73 * requests to open a session with the Trusted Application. The open
74 * session request may result in a new Trusted Application instance being
78 * to the Trusted Application instance in the arguments paramTypes and
79 * params. These arguments can also be used by the Trusted Application
84 * Trusted Application instance and can invoke Trusted Application
[all …]
|
| /OK3568_Linux_fs/external/security/rk_tee_user/v2/export-ta_arm32/host_include/ |
| H A D | tee_ta_api.h | 19 * Each Trusted Application must provide the Implementation with a number
25 * Trusted Application Entry Points:
29 * The function TA_CreateEntryPoint is the Trusted Application's
31 * the Trusted Application. To register instance data, the implementation
50 * The function TA_DestroyEntryPoint is the Trusted Application‟s
73 * requests to open a session with the Trusted Application. The open
74 * session request may result in a new Trusted Application instance being
78 * to the Trusted Application instance in the arguments paramTypes and
79 * params. These arguments can also be used by the Trusted Application
84 * Trusted Application instance and can invoke Trusted Application
[all …]
|
| /OK3568_Linux_fs/external/security/rk_tee_user/v1/export-user_ta/include/ |
| H A D | tee_ta_api.h | 41 * Each Trusted Application must provide the Implementation with a number
47 * Trusted Application Entry Points:
51 * The function TA_CreateEntryPoint is the Trusted Application's
53 * the Trusted Application. To register instance data, the implementation
72 * The function TA_DestroyEntryPoint is the Trusted Application‟s
95 * requests to open a session with the Trusted Application. The open
96 * session request may result in a new Trusted Application instance being
100 * to the Trusted Application instance in the arguments paramTypes and
101 * params. These arguments can also be used by the Trusted Application
106 * Trusted Application instance and can invoke Trusted Application
[all …]
|
| /OK3568_Linux_fs/external/security/rk_tee_user/v1/export-user_ta/host_include/ |
| H A D | tee_ta_api.h | 41 * Each Trusted Application must provide the Implementation with a number
47 * Trusted Application Entry Points:
51 * The function TA_CreateEntryPoint is the Trusted Application's
53 * the Trusted Application. To register instance data, the implementation
72 * The function TA_DestroyEntryPoint is the Trusted Application‟s
95 * requests to open a session with the Trusted Application. The open
96 * session request may result in a new Trusted Application instance being
100 * to the Trusted Application instance in the arguments paramTypes and
101 * params. These arguments can also be used by the Trusted Application
106 * Trusted Application instance and can invoke Trusted Application
[all …]
|
| /OK3568_Linux_fs/u-boot/include/optee_include/ |
| H A D | tee_client_api.h | 93 * client application to the TEE. TEEC_MEM_OUTPUT signifies data transfer
94 * direction from the TEE to the client application. Type is uint32_t.
97 * application to the Trusted Application.
99 * Application to the client application.
129 * TEEC_ERROR_TARGET_DEAD Trusted Application has panicked
166 * TEEC_ORIGIN_TRUSTED_APP The error originated within the Trusted Application
180 * Application process is provided.
182 * Application process is provided.
183 * TEEC_LOGIN_APPLICATION Login data about the running Client Application
213 * struct TEEC_Context - Represents a connection between a client application
[all …]
|
| /OK3568_Linux_fs/kernel/Documentation/arm/ |
| H A D | marvel.rst | 262 Dove family (application processor)
269 http://www.marvell.com/application-processors/armada-500/assets/Marvell_Armada510_SoC.pdf
272 http://www.marvell.com/application-processors/armada-500/assets/Armada-510-Hardware-Spec.pdf
275 http://www.marvell.com/application-processors/armada-500/assets/Armada-510-Functional-Spec.pdf
278 http://www.marvell.com/application-processors/armada-500/
292 - Application processor only
295 …- Product Brief : http://www.marvell.com/application-processors/pxa-family/assets/pxa_27x_…
296 …- Design guide : http://www.marvell.com/application-processors/pxa-family/assets/pxa_27x_…
297 …- Developers manual : http://www.marvell.com/application-processors/pxa-family/assets/pxa_27x_…
298 …- Specification : http://www.marvell.com/application-processors/pxa-family/assets/pxa_27x_…
[all …]
|
| /OK3568_Linux_fs/yocto/poky/bitbake/lib/toaster/toastermain/ |
| H A D | wsgi.py | 8 This module contains the WSGI application used by Django's development server
10 named ``application``. Django's ``runserver`` and ``runfcgi`` commands discover
11 this application via the ``WSGI_APPLICATION`` setting.
13 Usually you will have the standard Django WSGI application here, but it also
14 might make sense to replace the whole Django WSGI application with a custom one
16 middleware here, or combine a Django application with an application of another
28 # This application object is used by any WSGI server configured to use this
32 application = get_wsgi_application() variable
36 # application = HelloWorldApplication(application)
|
| /OK3568_Linux_fs/u-boot/doc/ |
| H A D | README.efi | 15 1.6 EFI Application
32 as an application or just as a means of getting U-Boot onto a new platform.
59 U-Boot supports running as an EFI application for 32-bit EFI only. This is
75 To build U-Boot as an EFI application (32-bit EFI required), enable CONFIG_EFI
92 u-boot-app.efi - U-Boot EFI application
93 u-boot-payload.efi - U-Boot EFI payload application
108 run the application. 'bios.bin' is the EFI 'BIOS'. Check [2] to obtain a
116 (or fs0:u-boot-app.efi for the application)
119 that EFI does not support booting a 64-bit application from a 32-bit
129 The application and payload approaches sound similar but are in fact
[all …]
|
| /OK3568_Linux_fs/external/security/rk_tee_user/v2/client_export/public/ |
| H A D | tee_client_api.h | 124 * client application to the TEE. TEEC_MEM_OUTPUT signifies data transfer
125 * direction from the TEE to the client application. Type is uint32_t.
128 * application to the Trusted Application.
130 * Application to the client application.
160 * TEEC_ERROR_TARGET_DEAD Trusted Application has panicked
199 * TEEC_ORIGIN_TRUSTED_APP The error originated within the Trusted Application
213 * Application process is provided.
215 * Application process is provided.
216 * TEEC_LOGIN_APPLICATION Login data about the running Client Application
219 * Client Application itself is provided.
[all …]
|
| /OK3568_Linux_fs/external/security/librkcrypto/third_party/optee_client/public/ |
| H A D | tee_client_api.h | 124 * client application to the TEE. TEEC_MEM_OUTPUT signifies data transfer
125 * direction from the TEE to the client application. Type is uint32_t.
128 * application to the Trusted Application.
130 * Application to the client application.
160 * TEEC_ERROR_TARGET_DEAD Trusted Application has panicked
199 * TEEC_ORIGIN_TRUSTED_APP The error originated within the Trusted Application
213 * Application process is provided.
215 * Application process is provided.
216 * TEEC_LOGIN_APPLICATION Login data about the running Client Application
219 * Client Application itself is provided.
[all …]
|
| /OK3568_Linux_fs/external/security/rk_tee_user/v1/client_export/public/ |
| H A D | tee_client_api.h | 117 * client application to the TEE. TEEC_MEM_OUTPUT signifies data transfer
118 * direction from the TEE to the client application. Type is uint32_t.
121 * application to the Trusted Application.
123 * Application to the client application.
153 * TEEC_ERROR_TARGET_DEAD Trusted Application has panicked
191 * TEEC_ORIGIN_TRUSTED_APP The error originated within the Trusted Application
205 * Application process is provided.
207 * Application process is provided.
208 * TEEC_LOGIN_APPLICATION Login data about the running Client Application
238 * struct TEEC_Context - Represents a connection between a client application
[all …]
|
| /OK3568_Linux_fs/kernel/arch/arm/mach-pxa/include/mach/ |
| H A D | pxa3xx-regs.h | 40 #define ASCR __REG(0x40f40000) /* Application Subsystem Power Status/Configuration */
41 #define ARSR __REG(0x40f40004) /* Application Subsystem Reset Status */
42 #define AD3ER __REG(0x40f40008) /* Application Subsystem Wake-Up from D3 Enable */
43 #define AD3SR __REG(0x40f4000c) /* Application Subsystem Wake-Up from D3 Status */
44 #define AD2D0ER __REG(0x40f40010) /* Application Subsystem Wake-Up from D2 to D0 Enable */
45 #define AD2D0SR __REG(0x40f40014) /* Application Subsystem Wake-Up from D2 to D0 Status */
46 #define AD2D1ER __REG(0x40f40018) /* Application Subsystem Wake-Up from D2 to D1 Enable */
47 #define AD2D1SR __REG(0x40f4001c) /* Application Subsystem Wake-Up from D2 to D1 Status */
48 #define AD1D0ER __REG(0x40f40020) /* Application Subsystem Wake-Up from D1 to D0 Enable */
49 #define AD1D0SR __REG(0x40f40024) /* Application Subsystem Wake-Up from D1 to D0 Status */
[all …]
|
| /OK3568_Linux_fs/yocto/meta-openembedded/meta-gnome/recipes-connectivity/geary/geary/ |
| H A D | 0002-Fix-accessibility-issues-with-initializer-of-constan.patch | 9 src/client/application/application-client.vala | 14 +++++++-------
12 diff --git a/src/client/application/application-client.vala b/src/client/application/application-cl…
14 --- a/src/client/application/application-client.vala
15 +++ b/src/client/application/application-client.vala
|
| /OK3568_Linux_fs/kernel/net/netlabel/ |
| H A D | netlabel_unlabeled.h | 25 * This message is sent from an application to add a new static label for
44 * This message is sent from an application to remove an existing static
62 * This message can be sent either from an application or by the kernel in
63 * response to an application generated STATICLIST message. When sent by an
64 * application there is no payload and the NLM_F_DUMP flag should be set.
83 * This message is sent from an application to set the default static
101 * This message is sent from an application to remove the existing default
115 * This message can be sent either from an application or by the kernel in
116 * response to an application generated STATICLISTDEF message. When sent by
117 * an application there is no payload and the NLM_F_DUMP flag should be set.
[all …]
|
| H A D | netlabel_mgmt.h | 26 * Sent by an application to add a domain mapping to the NetLabel system.
53 * Sent by an application to remove a domain mapping from the NetLabel
61 * This message can be sent either from an application or by the kernel in
62 * response to an application generated LISTALL message. When sent by an
63 * application there is no payload and the NLM_F_DUMP flag should be set.
90 * Sent by an application to set the default domain mapping for the NetLabel
107 * Sent by an application to remove the default domain mapping from the
111 * This message can be sent either from an application or by the kernel in
112 * response to an application generated LISTDEF message. When sent by an
113 * application there may be an optional payload.
[all …]
|
| /OK3568_Linux_fs/kernel/drivers/iio/accel/ |
| H A D | mma9551_core.c | 33 /* GPIO Application */
37 /* Sleep/Wake application */
43 /* AFE application */
48 /* Reset/Suspend/Clear application */
202 * @app_id: Application ID
203 * @reg: Application register
227 * @app_id: Application ID
228 * @reg: Application register
252 * @app_id: Application ID
253 * @reg: Application register
[all …]
|
| /OK3568_Linux_fs/kernel/Documentation/userspace-api/media/v4l/ |
| H A D | pixfmt-v4l2.rst | 47 - The pixel format or type of compression, set by the application.
69 the value requested by the application, returning ``width`` times
111 by the driver for capture streams and by the application for
112 output streams, see :ref:`colorspaces`. If the application sets the
113 flag ``V4L2_PIX_FMT_FLAG_SET_CSC`` then the application can set
148 - Flags set by the application or driver, see :ref:`format-flags`.
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
[all …]
|
| /OK3568_Linux_fs/yocto/poky/meta/files/common-licenses/ |
| H A D | LGPL-3.0-only | 14 “The Library” refers to a covered work governed by this License, other than an Application or a Com…
16 An “Application” is any work that makes use of an interface provided by the Library, but which is n…
18 A “Combined Work” is a work produced by combining or linking an Application with the Library. The p…
20 …s of the Combined Work that, considered in isolation, are based on the Application, and not on the…
22 …Application Code” for a Combined Work means the object code and/or source code for the Application…
28 …ications, a facility refers to a function or data to be supplied by an Application that uses the f…
30 …ided that you make a good faith effort to ensure that, in the event an Application does not supply…
35 The object code form of an Application may incorporate material from a header file that is part of …
48 …the Corresponding Application Code in a form suitable for, and under terms that permit, the user t…
50 …Application with a modified version of the Linked Version. (If you use option 4d0, the Installatio…
|
| H A D | LGPL-3.0-or-later | 25 an Application or a Combined Work as defined below.
29 An "Application" is any work that makes use of an interface provided by the
36 A "Combined Work" is a work produced by combining or linking an Application
44 Combined Work that, considered in isolation, are based on the Application,
49 The "Corresponding Application Code" for a Combined Work means the object
50 code and/or source code for the Application, including any data and utility
51 programs needed for reproducing the Combined Work from the Application, but
62 refers to a function or data to be supplied by an Application that uses the
67 that, in the event an Application does not supply the function or data, the
76 The object code form of an Application may incorporate material from a header
[all …]
|
| /OK3568_Linux_fs/buildroot/dl/qt5location/git/ |
| H A D | LICENSE.LGPL3 | 20 other than an Application or a Combined Work as defined below.
22 An "Application" is any work that makes use of an interface provided
28 Application with the Library. The particular version of the Library
35 based on the Application, and not on the Linked Version.
37 The "Corresponding Application Code" for a Combined Work means the
38 object code and/or source code for the Application, including any data
40 Application, but excluding the System Libraries of the Combined Work.
50 facility refers to a function or data to be supplied by an Application
56 ensure that, in the event an Application does not supply the
65 The object code form of an Application may incorporate material from
[all …]
|
| H A D | LICENSE.LGPLv3 | 31 other than an Application or a Combined Work as defined below.
33 An “Application” is any work that makes use of an interface provided
39 Application with the Library. The particular version of the Library
46 based on the Application, and not on the Linked Version.
48 The “Corresponding Application Code” for a Combined Work means the
49 object code and/or source code for the Application, including any data
51 Application, but excluding the System Libraries of the Combined Work.
61 facility refers to a function or data to be supplied by an Application
67 to ensure that, in the event an Application does not supply the
76 The object code form of an Application may incorporate material from
[all …]
|