Home
last modified time | relevance | path

Searched full:to (Results 1 – 25 of 6011) sorted by relevance

12345678910>>...241

/system/tools/aidl/
Dast_java.cpp10 * Unless required by applicable law or agreed to in writing, software
40 void WriteComment(CodeWriter* to, const std::string& comment) { in WriteComment() argument
41 to->Write("%s", comment.c_str()); in WriteComment()
42 if (!comment.empty() && comment.back() != '\n') to->Write("\n"); in WriteComment()
45 void WriteModifiers(CodeWriter* to, int mod, int mask) { in WriteModifiers() argument
49 to->Write("@Override "); in WriteModifiers()
53 to->Write("public "); in WriteModifiers()
55 to->Write("private "); in WriteModifiers()
57 to->Write("protected "); in WriteModifiers()
61 to->Write("static "); in WriteModifiers()
[all …]
/system/chre/doc/
Dvendor_extensions.md5 The CHRE framework is easily extensible with no modifications to the core
7 steps must be performed. At a high-level, to add a new vendor-specific API to
13 2. Expose the new APIs from the framework to nanoapps, and connect them to a new
14 module to provide the desired functionality
17 event subsystem, to provide complete functionality that fits within the
20 It's best to refer to existing standard CHRE API feature areas, such as
26 To prevent collision with future common CHRE API definitions, vendor extensions
28 it’s recommended to prefix the APIs with the vendor’s name as lowercase. For
30 ‘widget’ API, it’s recommended to use a naming scheme like
37 where vendors may wish or need to define a custom value in an existing field. To
[all …]
/system/bpfprogs/
DLICENSE8 Everyone is permitted to copy and distribute verbatim copies of this license
13 The licenses for most software are designed to take away your freedom to share
14 and change it. By contrast, the GNU General Public License is intended to
15 guarantee your freedom to share and change free software--to make sure the
16 software is free for all its users. This General Public License applies to
17 most of the Free Software Foundation's software and to any other program whose
18 authors commit to using it. (Some other Free Software Foundation software is
19 covered by the GNU Library General Public License instead.) You can apply it to
22 When we speak of free software, we are referring to freedom, not price. Our
23 General Public Licenses are designed to make sure that you have the freedom to
[all …]
/system/memory/libion/original-kernel-headers/linux/
DLICENSE8 Everyone is permitted to copy and distribute verbatim copies of this license
13 The licenses for most software are designed to take away your freedom to share
14 and change it. By contrast, the GNU General Public License is intended to
15 guarantee your freedom to share and change free software--to make sure the
16 software is free for all its users. This General Public License applies to
17 most of the Free Software Foundation's software and to any other program whose
18 authors commit to using it. (Some other Free Software Foundation software is
19 covered by the GNU Library General Public License instead.) You can apply it to
22 When we speak of free software, we are referring to freedom, not price. Our
23 General Public Licenses are designed to make sure that you have the freedom to
[all …]
/system/media/audio_utils/
DDoxyfile3 # This file describes the settings to be used by the documentation system
37 # The PROJECT_NUMBER tag can be used to enter a project or revision number. This
52 # the logo to the output directory.
56 # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) path
58 # entered, it will be relative to the location where doxygen was started. If
63 # If the CREATE_SUBDIRS tag is set to YES then doxygen will create 4096 sub-
73 # If the ALLOW_UNICODE_NAMES tag is set to YES, doxygen will allow non-ASCII
74 # characters to appear in the names of generated files. If set to NO, non-ASCII
81 # The OUTPUT_LANGUAGE tag is used to specify the language in which all
83 # information to generate all constant output in the proper language.
[all …]
/system/chre/chre_api/doc/
DDoxyfile3 # This file describes the settings to be used by the documentation system
37 # The PROJECT_NUMBER tag can be used to enter a project or revision number. This
52 # the logo to the output directory.
56 # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) path
58 # entered, it will be relative to the location where doxygen was started. If
63 # If the CREATE_SUBDIRS tag is set to YES then doxygen will create 4096 sub-
73 # If the ALLOW_UNICODE_NAMES tag is set to YES, doxygen will allow non-ASCII
74 # characters to appear in the names of generated files. If set to NO, non-ASCII
81 # The OUTPUT_LANGUAGE tag is used to specify the language in which all
83 # information to generate all constant output in the proper language.
[all …]
/system/chre/pal/doc/
DDoxyfile3 # This file describes the settings to be used by the documentation system
37 # The PROJECT_NUMBER tag can be used to enter a project or revision number. This
52 # the logo to the output directory.
56 # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) path
58 # entered, it will be relative to the location where doxygen was started. If
63 # If the CREATE_SUBDIRS tag is set to YES then doxygen will create 4096 sub-
73 # If the ALLOW_UNICODE_NAMES tag is set to YES, doxygen will allow non-ASCII
74 # characters to appear in the names of generated files. If set to NO, non-ASCII
81 # The OUTPUT_LANGUAGE tag is used to specify the language in which all
83 # information to generate all constant output in the proper language.
[all …]
/system/sepolicy/prebuilts/api/202504/private/
Dapexd.te23 # Allow apexd to create files and directories for snapshots of apex data
31 # Allow apexd to read /data/misc_de and the directories under it, in order to
38 # allow apexd to create loop devices with /dev/loop-control
40 # allow apexd to access loop devices
52 # Allow apexd to access /dev/block
56 #allow apexd to access virtual disks
59 # allow apexd to access /dev/block/dm-* (device-mapper entries)
63 # sys_admin is required to access the device-mapper and mount
69 # than one of the groups assigned to the current process to see if
71 # bit was even set. We do not appear to truly need this capability
[all …]
Dshell.te6 # systrace support - allow atrace to run
20 # allow reading tombstones. users can already use bugreports to get those.
28 # allow shell to call dumpsys storaged
39 # Allow shell binaries to write trace data to Perfetto. Used for testing and
45 # Allow shell to execute tradeinmode for testing.
48 # Allow shell binaries to exec the perfetto cmdline util and have that
49 # transition into its own domain, so that it behaves consistently to
52 # Allow to send SIGINT to perfetto when daemonized.
55 # Allow shell to run adb shell cmd stats commands. Needed for CTS.
58 # Allow shell to read and unlink traces stored in /data/misc/a11ytraces.
[all …]
Dstatsd.te5 # Allow to exec the perfetto cmdline client and pass it the trace config on
6 # stdint through a pipe. It allows statsd to capture traces and hand them
7 # to Android dropbox.
11 # Grant statsd with permissions to register the services.
16 # Allow incidentd to obtain the statsd incident section.
19 # Allow StatsCompanionService to pipe data to statsd.
22 # Allow any app to pipe data to statsd.
23 # Access control to all statsd APIs inherit from system_api_service, so
24 # appdomain permissions are granted to avoid listing each individual
28 # Allow statsd to retrieve SF statistics over binder
[all …]
/system/sepolicy/private/
Dapexd.te23 # Allow apexd to create files and directories for snapshots of apex data
31 # Allow apexd to read /data/misc_de and the directories under it, in order to
38 # allow apexd to create loop devices with /dev/loop-control
40 # allow apexd to access loop devices
52 # Allow apexd to access /dev/block
56 #allow apexd to access virtual disks
59 # allow apexd to access /dev/block/dm-* (device-mapper entries)
63 # sys_admin is required to access the device-mapper and mount
69 # than one of the groups assigned to the current process to see if
71 # bit was even set. We do not appear to truly need this capability
[all …]
Dshell.te6 # systrace support - allow atrace to run
20 # allow reading tombstones. users can already use bugreports to get those.
28 # allow shell to call dumpsys storaged
39 # Allow shell binaries to write trace data to Perfetto. Used for testing and
45 # Allow shell to execute tradeinmode for testing.
48 # Allow shell binaries to exec the perfetto cmdline util and have that
49 # transition into its own domain, so that it behaves consistently to
52 # Allow to send SIGINT to perfetto when daemonized.
55 # Allow shell to run adb shell cmd stats commands. Needed for CTS.
58 # Allow shell to read and unlink traces stored in /data/misc/a11ytraces.
[all …]
Dstatsd.te5 # Allow to exec the perfetto cmdline client and pass it the trace config on
6 # stdint through a pipe. It allows statsd to capture traces and hand them
7 # to Android dropbox.
11 # Grant statsd with permissions to register the services.
16 # Allow incidentd to obtain the statsd incident section.
19 # Allow StatsCompanionService to pipe data to statsd.
22 # Allow any app to pipe data to statsd.
23 # Access control to all statsd APIs inherit from system_api_service, so
24 # appdomain permissions are granted to avoid listing each individual
28 # Allow statsd to retrieve SF statistics over binder
[all …]
/system/sepolicy/prebuilts/api/202404/private/
Dshell.te6 # systrace support - allow atrace to run
20 # allow reading tombstones. users can already use bugreports to get those.
28 # allow shell to call dumpsys storaged
39 # Allow shell binaries to write trace data to Perfetto. Used for testing and
45 # Allow shell binaries to exec the perfetto cmdline util and have that
46 # transition into its own domain, so that it behaves consistently to
49 # Allow to send SIGINT to perfetto when daemonized.
52 # Allow shell to run adb shell cmd stats commands. Needed for CTS.
55 # Allow shell to read and unlink traces stored in /data/misc/a11ytraces.
61 # Allow shell to read and unlink traces stored in /data/misc/perfetto-traces.
[all …]
Dapexd.te20 # Allow apexd to create files and directories for snapshots of apex data
28 # Allow apexd to read /data/misc_de and the directories under it, in order to
35 # allow apexd to create loop devices with /dev/loop-control
37 # allow apexd to access loop devices
49 # Allow apexd to access /dev/block
53 #allow apexd to access virtual disks
56 # allow apexd to access /dev/block/dm-* (device-mapper entries)
60 # sys_admin is required to access the device-mapper and mount
66 # than one of the groups assigned to the current process to see if
68 # bit was even set. We do not appear to truly need this capability
[all …]
/system/sepolicy/prebuilts/api/34.0/private/
Dshell.te6 # systrace support - allow atrace to run
24 # allow shell to call dumpsys storaged
35 # Allow shell binaries to write trace data to Perfetto. Used for testing and
41 # Allow shell binaries to exec the perfetto cmdline util and have that
42 # transition into its own domain, so that it behaves consistently to
45 # Allow to send SIGINT to perfetto when daemonized.
48 # Allow shell to run adb shell cmd stats commands. Needed for CTS.
51 # Allow shell to read and unlink traces stored in /data/misc/a11ytraces.
57 # Allow shell to read and unlink traces stored in /data/misc/perfetto-traces.
64 # Allow shell to create/remove configs stored in /data/misc/perfetto-configs.
[all …]
/system/chre/apps/test/common/chre_cross_validator_sensor/inc/
Dchre_cross_validator_sensor_manager.h10 * Unless required by applicable law or agreed to in writing, software
31 // to avoid it becoming to complex.
37 * Class to manage a CHRE cross validator nanoapp.
64 * Struct to hold the state of the cross validator nanoapp.
67 // Set upon received start message and read when nanoapp ends to handle
78 // sending data back to AP.
81 // sending data back to AP.
122 * @param stream The stream to write to.
123 * @param field The field to write to (unused).
124 * @param arg The data passed in order to write to the stream.
[all …]
/system/sepolicy/prebuilts/api/33.0/private/
Dshell.te6 # systrace support - allow atrace to run
24 # allow shell to call dumpsys storaged
35 # Allow shell binaries to write trace data to Perfetto. Used for testing and
41 # Allow shell binaries to exec the perfetto cmdline util and have that
42 # transition into its own domain, so that it behaves consistently to
45 # Allow to send SIGINT to perfetto when daemonized.
48 # Allow shell to run adb shell cmd stats commands. Needed for CTS.
51 # Allow shell to read and unlink traces stored in /data/misc/a11ytraces.
57 # Allow shell to read and unlink traces stored in /data/misc/perfetto-traces.
64 # Allow shell to create/remove configs stored in /data/misc/perfetto-configs.
[all …]
Dapexd.te19 # Allow apexd to setup fs-verity for SEPolicy files in metadata
28 # Allow apexd to create files and directories for snapshots of apex data
36 # Allow apexd to read directories under /data/misc_de in order to snapshot and
40 # allow apexd to create loop devices with /dev/loop-control
42 # allow apexd to access loop devices
54 # Allow apexd to access /dev/block
58 #allow apexd to access virtual disks
61 # allow apexd to access /dev/block/dm-* (device-mapper entries)
65 # sys_admin is required to access the device-mapper and mount
71 # than one of the groups assigned to the current process to see if
[all …]
/system/chre/chre_api/legacy/v1_6/
Dchre.h10 * Unless required by applicable law or agreed to in writing, software
22 * This header file includes all the headers which combine to fully define the
24 * of interest to both implementers of CHREs and authors of nanoapps. The API
25 * documentation attempts to address concerns of both.
47 * CHRE is the Context Hub Runtime Environment. CHRE is used in Android to run
50 * API, documented herein, is the common interface exposed to nanoapps for any
53 * implementations and underlying platforms. Refer to the following sections for
59 * The following entry points are used to bind a nanoapp to the CHRE system, and
66 * prior to invoking nanoappStart, or after nanoappEnd returns:
67 * - bss section zeroed out (prior to nanoappStart)
[all …]
/system/chre/chre_api/include/chre_api/
Dchre.h10 * Unless required by applicable law or agreed to in writing, software
22 * This header file includes all the headers which combine to fully define the
24 * of interest to both implementers of CHREs and authors of nanoapps. The API
25 * documentation attempts to address concerns of both.
48 * CHRE is the Context Hub Runtime Environment. CHRE is used in Android to run
51 * API, documented herein, is the common interface exposed to nanoapps for any
54 * implementations and underlying platforms. Refer to the following sections for
60 * The following entry points are used to bind a nanoapp to the CHRE system, and
67 * prior to invoking nanoappStart, or after nanoappEnd returns:
68 * - bss section zeroed out (prior to nanoappStart)
[all …]
/system/chre/chre_api/legacy/v1_10/
Dchre.h10 * Unless required by applicable law or agreed to in writing, software
22 * This header file includes all the headers which combine to fully define the
24 * of interest to both implementers of CHREs and authors of nanoapps. The API
25 * documentation attempts to address concerns of both.
47 * CHRE is the Context Hub Runtime Environment. CHRE is used in Android to run
50 * API, documented herein, is the common interface exposed to nanoapps for any
53 * implementations and underlying platforms. Refer to the following sections for
59 * The following entry points are used to bind a nanoapp to the CHRE system, and
66 * prior to invoking nanoappStart, or after nanoappEnd returns:
67 * - bss section zeroed out (prior to nanoappStart)
[all …]
/system/chre/chre_api/legacy/v1_1/
Dchre.h10 * Unless required by applicable law or agreed to in writing, software
22 * This header file includes all the headers which combine to fully define the
24 * of interest to both implementers of CHREs and authors of nanoapps. The API
25 * documentation attempts to address concerns of both.
43 * CHRE is the Context Hub Runtime Environment. CHRE is used in Android to run
46 * API, documented herein, is the common interface exposed to nanoapps for any
49 * implementations and underlying platforms. Refer to the following sections for
55 * The following entry points are used to bind a nanoapp to the CHRE system, and
62 * prior to invoking nanoappStart, or after nanoappEnd returns:
63 * - bss section zeroed out (prior to nanoappStart)
[all …]
/system/chre/chre_api/legacy/v1_2/
Dchre.h10 * Unless required by applicable law or agreed to in writing, software
22 * This header file includes all the headers which combine to fully define the
24 * of interest to both implementers of CHREs and authors of nanoapps. The API
25 * documentation attempts to address concerns of both.
44 * CHRE is the Context Hub Runtime Environment. CHRE is used in Android to run
47 * API, documented herein, is the common interface exposed to nanoapps for any
50 * implementations and underlying platforms. Refer to the following sections for
56 * The following entry points are used to bind a nanoapp to the CHRE system, and
63 * prior to invoking nanoappStart, or after nanoappEnd returns:
64 * - bss section zeroed out (prior to nanoappStart)
[all …]
/system/chre/chre_api/legacy/v1_4/
Dchre.h10 * Unless required by applicable law or agreed to in writing, software
22 * This header file includes all the headers which combine to fully define the
24 * of interest to both implementers of CHREs and authors of nanoapps. The API
25 * documentation attempts to address concerns of both.
45 * CHRE is the Context Hub Runtime Environment. CHRE is used in Android to run
48 * API, documented herein, is the common interface exposed to nanoapps for any
51 * implementations and underlying platforms. Refer to the following sections for
57 * The following entry points are used to bind a nanoapp to the CHRE system, and
64 * prior to invoking nanoappStart, or after nanoappEnd returns:
65 * - bss section zeroed out (prior to nanoappStart)
[all …]

12345678910>>...241