| /OK3568_Linux_fs/kernel/drivers/gpu/arm/mali400/mali/common/ |
| H A D | mali_soft_job.c | 20 MALI_STATIC_INLINE void mali_soft_job_system_lock(struct mali_soft_job_system *system) in mali_soft_job_system_lock() argument 22 MALI_DEBUG_ASSERT_POINTER(system); in mali_soft_job_system_lock() 23 _mali_osk_spinlock_irq_lock(system->lock); in mali_soft_job_system_lock() 24 MALI_DEBUG_PRINT(5, ("Mali Soft Job: soft system %p lock taken\n", system)); in mali_soft_job_system_lock() 25 MALI_DEBUG_ASSERT(0 == system->lock_owner); in mali_soft_job_system_lock() 26 MALI_DEBUG_CODE(system->lock_owner = _mali_osk_get_tid()); in mali_soft_job_system_lock() 29 MALI_STATIC_INLINE void mali_soft_job_system_unlock(struct mali_soft_job_system *system) in mali_soft_job_system_unlock() argument 31 MALI_DEBUG_ASSERT_POINTER(system); in mali_soft_job_system_unlock() 32 MALI_DEBUG_PRINT(5, ("Mali Soft Job: releasing soft system %p lock\n", system)); in mali_soft_job_system_unlock() 33 MALI_DEBUG_ASSERT(_mali_osk_get_tid() == system->lock_owner); in mali_soft_job_system_unlock() [all …]
|
| H A D | mali_timeline.c | 20 #define MALI_TIMELINE_SYSTEM_LOCKED(system) (mali_spinlock_reentrant_is_held((system)->spinlock, _m… argument 31 * timeline system, we can use these three value to decide 38 static mali_scheduler_mask mali_timeline_system_release_waiter(struct mali_timeline_system *system, 109 struct mali_timeline_system *system; in mali_timeline_timer_callback() local 118 system = timeline->system; in mali_timeline_timer_callback() 119 MALI_DEBUG_ASSERT_POINTER(system); in mali_timeline_timer_callback() 121 mali_spinlock_reentrant_wait(system->spinlock, tid); in mali_timeline_timer_callback() 123 if (!system->timer_enabled) { in mali_timeline_timer_callback() 124 mali_spinlock_reentrant_signal(system->spinlock, tid); in mali_timeline_timer_callback() 134 mali_spinlock_reentrant_signal(system->spinlock, tid); in mali_timeline_timer_callback() [all …]
|
| H A D | mali_soft_job.h | 28 * by the Timeline system. 41 * Once the job is added to the timeline system, the state changes to MALI_SOFT_JOB_STATE_STARTED. 74 /* Protected by soft job system lock. */ 77 struct mali_soft_job_system *system; /**< The soft job system this job is in. */ member 78 _mali_osk_list_t system_list; /**< List element used by soft job system. */ 82 * Per-session soft job system. 84 * The soft job system is used to manage all soft jobs that belongs to a session. 87 …struct mali_session_data *session; /**< The session this soft job system belong… 90 …_mali_osk_spinlock_irq_t *lock; /**< Lock used to protect soft job system an… 91 … /**< Contains tid of thread that locked the system or 0, if not locke… [all …]
|
| /OK3568_Linux_fs/kernel/drivers/eisa/ |
| H A D | eisa.ids | 18 ACE1010 "ACME Super Fast System Board" 26 ACR1201 "Acer 1200 486/25 EISA System Board" 27 ACR1211 "AcerFrame 3000SP33 486/33 EISA System Board" 39 ACR1711 "AcerFrame 1000 486/33 SYSTEM-2" 40 ACR1801 "Acer P43WE EISA System Board" 41 ACR3211 "AcerFrame 3000MP 486 SYSTEM-1" 42 ACR3221 "AcerFrame 486 Series SYSTEM-2" 43 ACR3231 "AcerFrame 486 Series SYSTEM-3" 44 ACR3241 "AcerFrame 486 Series SYSTEM-4" 45 ACR3261 "AcerFrame 3000MP 486 SYSTEM-1" [all …]
|
| /OK3568_Linux_fs/yocto/meta-openembedded/meta-oe/recipes-devtools/android-tools/android-tools/ |
| H A D | gitignore | 10 !/system/ 11 !/system/core/ 12 !/system/core/adb/ 13 !/system/core/fastboot/ 14 !/system/core/fs_mgr/ 15 !/system/core/fs_mgr/include/ 16 !/system/core/include/ 17 !/system/core/include/android/ 18 !/system/core/include/cutils/ 19 !/system/core/include/log/ [all …]
|
| /OK3568_Linux_fs/kernel/Documentation/ABI/testing/ |
| H A D | sysfs-devices-system-cpu | 1 What: /sys/devices/system/cpu/ 10 /sys/devices/system/cpu/cpu#/ 12 What: /sys/devices/system/cpu/kernel_max 13 /sys/devices/system/cpu/offline 14 /sys/devices/system/cpu/online 15 /sys/devices/system/cpu/possible 16 /sys/devices/system/cpu/present 35 the system. 40 What: /sys/devices/system/cpu/probe 41 /sys/devices/system/cpu/release [all …]
|
| H A D | sysfs-devices-memory | 1 What: /sys/devices/system/memory 5 The /sys/devices/system/memory contains a snapshot of the 12 What: /sys/devices/system/memory/memoryX/removable 16 The file /sys/devices/system/memory/memoryX/removable 24 What: /sys/devices/system/memory/memoryX/phys_device 28 The file /sys/devices/system/memory/memoryX/phys_device 33 What: /sys/devices/system/memory/memoryX/phys_index 37 The file /sys/devices/system/memory/memoryX/phys_index 42 What: /sys/devices/system/memory/memoryX/state 46 The file /sys/devices/system/memory/memoryX/state [all …]
|
| /OK3568_Linux_fs/kernel/Documentation/admin-guide/pm/ |
| H A D | sleep-states.rst | 5 System Sleep States 13 Sleep states are global low-power states of the entire system in which user 14 space code cannot be executed and the overall system activity is significantly 22 the Linux kernel can support up to four system sleep states, including 23 hibernation and up to three variants of system suspend. The sleep states that 31 This is a generic, pure software, light-weight variant of system suspend (also 36 states while the system is suspended. 38 The system is woken up from this state by in-band interrupts, so theoretically 44 deeper system suspend variants to provide reduced resume latency. It is always 54 operating state is lost (the system core logic retains power), so the system can [all …]
|
| H A D | suspend-flows.rst | 5 System Suspend Code Flows 12 At least one global system-wide transition needs to be carried out for the 13 system to get from the working state into one of the supported 16 referred to as *system-wide suspend* (or simply *system suspend*) states, need 19 For those sleep states, the transition from the working state of the system into 20 the target sleep state is referred to as *system suspend* too (in the majority 21 of cases, whether this means a transition or a sleep state of the system should 23 working state is referred to as *system resume*. 26 different sleep states of the system are quite similar, but there are some 45 The following steps are taken in order to transition the system from the working [all …]
|
| H A D | strategies.rst | 15 One of them is based on using global low-power states of the whole system in 16 which user space code cannot be executed and the overall system activity is 18 kernel puts the system into one of these states when requested by user space 19 and the system stays in it until a special signal is received from one of 21 user space code can run. Because sleep states are global and the whole system 23 :doc:`system-wide power management <system-wide>`. 27 components of the system, as needed, in the working state. In consequence, if 28 this strategy is in use, the working state of the system usually does not 30 a metastate covering a range of different power states of the system in which 37 If all of the system components are active, the system as a whole is regarded as [all …]
|
| /OK3568_Linux_fs/buildroot/package/qt5/qt5webengine/ |
| H A D | qt5webengine.mk | 37 -feature-webengine-system-libdrm \ 38 -feature-webengine-system-x11 \ 39 -feature-webengine-system-xkbfile \ 40 -feature-webengine-system-xcomposite \ 41 -feature-webengine-system-xcursor \ 42 -feature-webengine-system-xi \ 43 -feature-webengine-system-xproto-gl \ 44 -feature-webengine-system-xtst 48 -no-feature-webengine-system-libdrm \ 49 -no-feature-webengine-system-x11 \ [all …]
|
| /OK3568_Linux_fs/kernel/include/asm-generic/ |
| H A D | syscall.h | 3 * Access to user system call parameters and results 23 * syscall_get_nr - find what system call a task is executing 27 * If @task is executing a system call or is at system call 28 * tracing about to attempt one, returns the system call number. 29 * If @task is not executing a system call, i.e. it's blocked 33 * system call number can be meaningful. If the actual arch value 41 * syscall_rollback - roll back registers after an aborted system call 42 * @task: task of interest, must be in system call exit tracing 45 * It's only valid to call this when @task is stopped for system 48 * the system call from taking place. [all …]
|
| /OK3568_Linux_fs/kernel/Documentation/process/ |
| H A D | adding-syscalls.rst | 4 Adding a New System Call 7 This document describes what's involved in adding a new system call to the 12 System Call Alternatives 15 The first thing to consider when adding a new system call is whether one of 16 the alternatives might be suitable instead. Although system calls are the 35 - If you're just exposing runtime system information, a new node in sysfs 43 :manpage:`fcntl(2)` is a multiplexing system call that hides a lot of complexity, so 49 with :manpage:`fcntl(2)`, this system call is a complicated multiplexor so 57 A new system call forms part of the API of the kernel, and has to be supported 63 together with the corresponding follow-up system calls -- [all …]
|
| /OK3568_Linux_fs/yocto/meta-clang/dynamic-layers/selinux/android-tools/ |
| H A D | android-tools_10.0.0.r36.bb | 24 …n.org/android-tools-team/android-platform-system-core;name=core;protocol=https;nobranch=1;destsuff… 25 …org/android-tools-team/android-platform-system-extras;name=extras;protocol=https;nobranch=1;destsu… 31 # Patches copied from android-platform-system-core/debian/patches 34 file://core-debian/move-log-file-to-proper-dir.patch;patchdir=system/core \ 35 file://core-debian/Added-missing-headers.patch;patchdir=system/core \ 36 file://core-debian/libusb-header-path.patch;patchdir=system/core \ 37 file://core-debian/stdatomic.patch;patchdir=system/core \ 38 file://core-debian/Nonnull.patch;patchdir=system/core \ 39 file://core-debian/Vector-cast.patch;patchdir=system/core \ 40 file://core-debian/use-Python-3-for-mkbootimg.patch;patchdir=system/core \ [all …]
|
| /OK3568_Linux_fs/kernel/arch/powerpc/include/asm/ |
| H A D | ipic.h | 26 #define IPIC_SICFR 0x00 /* System Global Interrupt Configuration Register */ 27 #define IPIC_SIVCR 0x04 /* System Global Interrupt Vector Register */ 28 #define IPIC_SIPNR_H 0x08 /* System Internal Interrupt Pending Register (HIGH) */ 29 #define IPIC_SIPNR_L 0x0C /* System Internal Interrupt Pending Register (LOW) */ 30 #define IPIC_SIPRR_A 0x10 /* System Internal Interrupt group A Priority Register */ 31 #define IPIC_SIPRR_B 0x14 /* System Internal Interrupt group B Priority Register */ 32 #define IPIC_SIPRR_C 0x18 /* System Internal Interrupt group C Priority Register */ 33 #define IPIC_SIPRR_D 0x1C /* System Internal Interrupt group D Priority Register */ 34 #define IPIC_SIMSR_H 0x20 /* System Internal Interrupt Mask Register (HIGH) */ 35 #define IPIC_SIMSR_L 0x24 /* System Internal Interrupt Mask Register (LOW) */ [all …]
|
| /OK3568_Linux_fs/kernel/arch/nds32/include/asm/ |
| H A D | syscall.h | 14 * syscall_get_nr - find what system call a task is executing 18 * If @task is executing a system call or is at system call 19 * tracing about to attempt one, returns the system call number. 20 * If @task is not executing a system call, i.e. it's blocked 24 * system call number can be meaningful. If the actual arch value 36 * syscall_rollback - roll back registers after an aborted system call 37 * @task: task of interest, must be in system call exit tracing 40 * It's only valid to call this when @task is stopped for system 43 * the system call from taking place. 46 * system call instruction was a no-op. The registers containing [all …]
|
| /OK3568_Linux_fs/kernel/Documentation/livepatch/ |
| H A D | system-state.rst | 2 System State Changes 5 Some users are really reluctant to reboot a system. This brings the need 14 change the system behavior or state so that it is no longer safe to 19 This is where the livepatch system state tracking gets useful. It 22 - store data needed to manipulate and restore the system state 28 1. Livepatch system state API 31 The state of the system might get modified either by several livepatch callbacks 46 - Non-zero number used to identify the affected system state. 50 - Number describing the variant of the system state change that 68 The system state version is used to prevent loading incompatible livepatches. [all …]
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/arm/hisilicon/controller/ |
| H A D | sysctrl.yaml | 7 title: Hisilicon system controller 13 The Hisilicon system controller is used on many Hisilicon boards, it can be 14 used to assist the slave core startup, reboot the system, etc. 16 There are some variants of the Hisilicon system controller, such as HiP01, 17 Hi3519, Hi6220 system controller, each of them is mostly compatible with the 18 Hisilicon system controller, but some same registers located at different 19 offset. In addition, the HiP01 system controller has some specific control 22 The compatible names of each system controller are as follows: 23 Hisilicon system controller --> hisilicon,sysctrl 24 HiP01 system controller --> hisilicon,hip01-sysctrl [all …]
|
| /OK3568_Linux_fs/kernel/Documentation/ABI/stable/ |
| H A D | sysfs-devices-node | 1 What: /sys/devices/system/node/possible 7 What: /sys/devices/system/node/online 13 What: /sys/devices/system/node/has_normal_memory 19 What: /sys/devices/system/node/has_cpu 25 What: /sys/devices/system/node/has_high_memory 32 What: /sys/devices/system/node/nodeX 40 What: /sys/devices/system/node/nodeX/cpumap 46 What: /sys/devices/system/node/nodeX/cpulist 52 What: /sys/devices/system/node/nodeX/meminfo 59 What: /sys/devices/system/node/nodeX/numastat [all …]
|
| /OK3568_Linux_fs/external/rkwifibt/src/ |
| H A D | rk_wifibt_init.c | 108 #define RTL8188EU_DRIVER_MODULE_PATH "/system/lib/modules/RTL8188EU.ko" 109 #define RTL8723BU_DRIVER_MODULE_PATH "/system/lib/modules/RTL8723BU.ko" 110 #define RTL8723BS_DRIVER_MODULE_PATH "/system/lib/modules/RTL8723BS.ko" 111 #define RTL8723CS_DRIVER_MODULE_PATH "/system/lib/modules/RTL8723CS.ko" 112 #define RTL8723DS_DRIVER_MODULE_PATH "/system/lib/modules/RTL8723DS.ko" 113 #define RTL8188FU_DRIVER_MODULE_PATH "/system/lib/modules/RTL8188FU.ko" 114 #define RTL8822BU_DRIVER_MODULE_PATH "/system/lib/modules/RTL8822BU.ko" 115 #define RTL8822BS_DRIVER_MODULE_PATH "/system/lib/modules/RTL8822BS.ko" 116 #define RTL8189ES_DRIVER_MODULE_PATH "/system/lib/modules/RTL8189ES.ko" 117 #define RTL8189FS_DRIVER_MODULE_PATH "/system/lib/modules/RTL8189FS.ko" [all …]
|
| /OK3568_Linux_fs/kernel/drivers/soc/renesas/ |
| H A D | Kconfig | 49 #comment "Renesas ARM SoCs System Type" 288 bool "System Controller support for R-Car" if COMPILE_TEST 291 bool "System Controller support for R-Car D3" if COMPILE_TEST 295 bool "System Controller support for R-Car E2" if COMPILE_TEST 299 bool "System Controller support for R-Car E3" if COMPILE_TEST 303 bool "System Controller support for R-Car H1" if COMPILE_TEST 307 bool "System Controller support for R-Car H2" if COMPILE_TEST 311 bool "System Controller support for R-Car H3" if COMPILE_TEST 315 bool "System Controller support for R-Car M2-W/N" if COMPILE_TEST 319 bool "System Controller support for R-Car M3-N" if COMPILE_TEST [all …]
|
| /OK3568_Linux_fs/kernel/Documentation/admin-guide/ |
| H A D | initrd.rst | 9 This RAM disk can then be mounted as the root file system and programs 10 can be run from it. Afterwards, a new root file system can be mounted 14 initrd is mainly designed to allow system startup to occur in two phases, 25 When using initrd, the system typically boots as follows: 38 6) init mounts the "real" root file system 39 7) init places the root file system at the root directory using the 40 pivot_root system call 43 9) the initrd file system is removed 65 the "normal" root file system is mounted. initrd data can be read 67 in this case and doesn't necessarily have to be a file system image. [all …]
|
| /OK3568_Linux_fs/kernel/Documentation/userspace-api/ |
| H A D | seccomp_filter.rst | 8 A large number of system calls are exposed to every userland process 10 As system calls change and mature, bugs are found and eradicated. A 12 of available system calls. The resulting set reduces the total kernel 13 surface exposed to the application. System call filtering is meant for 17 incoming system calls. The filter is expressed as a Berkeley Packet 19 operated on is related to the system call being made: system call 20 number and the system call arguments. This allows for expressive 21 filtering of system calls using a filter program language with a long 25 to time-of-check-time-of-use (TOCTOU) attacks that are common in system 27 pointers which constrains all filters to solely evaluating the system [all …]
|
| /OK3568_Linux_fs/external/rk_pcba_test/ |
| H A D | cpu_test.h | 5 #define _CPU_0_FREQ_TABLE "/sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies" 6 #define _CPU_1_FREQ_TABLE "/sys/devices/system/cpu/cpu1/cpufreq/scaling_available_frequencies" 7 #define _CPU_2_FREQ_TABLE "/sys/devices/system/cpu/cpu2/cpufreq/scaling_available_frequencies" 8 #define _CPU_3_FREQ_TABLE "/sys/devices/system/cpu/cpu3/cpufreq/scaling_available_frequencies" 10 #define _CPU_0_FREQ_GOVERNOR "/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor" 11 #define _CPU_1_FREQ_GOVERNOR "/sys/devices/system/cpu/cpu1/cpufreq/scaling_governor" 12 #define _CPU_2_FREQ_GOVERNOR "/sys/devices/system/cpu/cpu2/cpufreq/scaling_governor" 13 #define _CPU_3_FREQ_GOVERNOR "/sys/devices/system/cpu/cpu3/cpufreq/scaling_governor" 15 #define _CPU_0_FREQ_SET "/sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed" 16 #define _CPU_1_FREQ_SET "/sys/devices/system/cpu/cpu1/cpufreq/scaling_setspeed" [all …]
|
| /OK3568_Linux_fs/kernel/Documentation/crypto/ |
| H A D | userspace-if.rst | 62 send()/write() system call family. The result of the cipher operation is 63 obtained with the read()/recv() system call family. 77 3. Invoke accept with the socket descriptor. The accept system call 80 system calls to send data to the kernel or obtain data from the 88 the input buffer used for the send/write system call and the output 89 buffer used by the read/recv system call may be one and the same. This 120 Using the send() system call, the application provides the data that 121 should be processed with the message digest. The send system call allows 124 - MSG_MORE: If this flag is set, the send system call acts like a 126 calculated. If the flag is not set, the send system call calculates [all …]
|