Android 系统查看sys-devices-system-cpu-cpu0 目录结构

最新推荐文章于 2022-08-24 16:50:48 发布
最新推荐文章于 2022-08-24 16:50:48 发布
阅读量5.6k 收藏 4
点赞数 1
分类专栏： 安卓系统 文章标签： 查看CPU频率和策略 cpu freq policy cpu0目录 CPU调频档位
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/su749520/article/details/79024439
版权

一、 /sys/devices/system/cpu/cpu0 目录结构

/sys/devices/system/cpu/cpu0

Z91:/sys/devices/system/cpu/cpu0 # ls -al
ls -al
total 0
drwxr-xr-x  5 root root    0 2018-01-09 11:17 .
drwxr-xr-x 13 root root    0 2018-01-09 11:17 ..
lrwxrwxrwx  1 root root    0 2018-01-09 11:17 cpufreq -> ../cpufreq/policy0
drwxr-xr-x  5 root root    0 2018-01-09 11:17 cpuidle
lrwxrwxrwx  1 root root    0 2018-01-09 11:17 of_node -> ../../../../firmware/de
vicetree/base/cpus/cpu@0
-rw-r--r--  1 root root 4096 2018-01-09 11:17 online
drwxr-xr-x  2 root root    0 2018-01-09 11:17 power
lrwxrwxrwx  1 root root    0 2018-01-09 11:17 subsystem -> ../../../../bus/cpu
drwxr-xr-x  2 root root    0 2018-01-09 11:17 topology
-rw-r--r--  1 root root 4096 2018-01-09 11:17 uevent

二、重要信息获取

1. CPU 频率

cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq

cat cpuinfo_cur_freq
299000

2.CPU 所支持的主频率列表（KHZ）

cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies

Z91:/sys/devices/system/cpu/cpu0/cpufreq # cat scaling_available_frequencies
cat scaling_available_frequencies
1274000 1235000 1196000 1170000 1105000 1053000 1001000 962000 910000 845000 702
000 624000 546000 416000 338000 299000

CPU 调频需要选择对应的档位，且参数不同机器该配置不同

3.CPU 策略policy

cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors

Z91:/sys/devices/system/cpu/cpu0/cpufreq # cat scaling_available_governors
cat scaling_available_governors
ondemand userspace powersave interactive performance sched
  1. ondemand 表示使用内核提供的功能，可以动态调节频率
  2. userspace 表示用户模式，在此模式下允许其他用户程序调节CPU频率
  3. powersvae 表示省电模式，通常是在最低频率下运行
  4. interactive ondemand相似,规则是“快升慢降”
  5. performance 表示不降频，最高性能
  6. sched 基于调度器的 CPU 调频机制

4.查看当前 CPU 的运行模式

通过echo命令，能够改变当前处理器的governor类型

Z91:/sys/devices/system/cpu/cpu0/cpufreq # cat scaling_governor
cat scaling_governor
sched

三、 目录详情

1. cpufreq

主要获取 CPU 的频率、调频档位及策略等

http://blog.csdn.net/su749520/article/details/79023509

2. cpuidle

Z91:/sys/devices/system/cpu/cpu0/cpuidle # ls -al
ls -al
total 0
drwxr-xr-x 5 root root 0 2018-01-09 11:17 .
drwxr-xr-x 5 root root 0 2018-01-09 11:17 ..
drwxr-xr-x 2 root root 0 2018-01-09 11:17 driver
drwxr-xr-x 2 root root 0 2018-01-09 11:17 state0
drwxr-xr-x 2 root root 0 2018-01-09 11:17 state1
2.1 cpuidle/driver
Z91:/sys/devices/system/cpu/cpu0/cpuidle/driver # ls -al
ls -al
total 0
drwxr-xr-x 2 root root    0 2018-01-09 11:17 .
drwxr-xr-x 5 root root    0 2018-01-09 11:17 ..
-r--r--r-- 1 root root 4096 2018-01-09 11:17 name
2.1.1 cpuidle/driver/name
Z91:/sys/devices/system/cpu/cpu0/cpuidle/driver # cat name
cat name
mt67xx_acao_cpuidle
2.2 cpuidle/state0
Z91:/sys/devices/system/cpu/cpu0/cpuidle/state0 # ls -al
ls -al
total 0
drwxr-xr-x 2 root root    0 2018-01-09 11:17 .
drwxr-xr-x 5 root root    0 2018-01-09 11:17 ..
-r--r--r-- 1 root root 4096 2018-01-09 11:17 desc
-rw-r--r-- 1 root root 4096 2018-01-09 11:17 disable
-r--r--r-- 1 root root 4096 2018-01-09 11:17 latency
-r--r--r-- 1 root root 4096 2018-01-09 11:17 name
-r--r--r-- 1 root root 4096 2018-01-09 11:17 power
-r--r--r-- 1 root root 4096 2018-01-09 11:17 residency
-r--r--r-- 1 root root 4096 2018-01-09 11:17 time
-r--r--r-- 1 root root 4096 2018-01-09 11:17 usage
2.2.2 cpuidle/state0/desc
Z91:/sys/devices/system/cpu/cpu0/cpuidle/state0 # cat desc
cat desc
wfi
2.2.2 cpuidle/state0/disable
Z91:/sys/devices/system/cpu/cpu0/cpuidle/state0 # cat disable
cat disable
0
2.2.2 cpuidle/state0/latency
Z91:/sys/devices/system/cpu/cpu0/cpuidle/state0 # cat latency
cat latency
1
2.2.2 cpuidle/state0/name
Z91:/sys/devices/system/cpu/cpu0/cpuidle/state0 # cat name
cat name
rgidle
2.2.2 cpuidle/state0/power
Z91:/sys/devices/system/cpu/cpu0/cpuidle/state0 # cat power
cat power
0
2.2.2 cpuidle/state0/residency
Z91:/sys/devices/system/cpu/cpu0/cpuidle/state0 # cat residency
cat residency
1
2.2.2 cpuidle/state0/usage
Z91:/sys/devices/system/cpu/cpu0/cpuidle/state0 # cat usage
cat usage
11611074
2.3 cpuidle/state1

目录结构和 state0 一致

3. of_node

Z91:/sys/devices/system/cpu/cpu0/of_node # ls -al
ls -al
total 0
drwxr-xr-x 2 root root  0 2018-01-10 14:56 .
drwxr-xr-x 8 root root  0 2018-01-10 14:56 ..
-r--r--r-- 1 root root  4 2018-01-10 14:56 clock-frequency
-r--r--r-- 1 root root 15 2018-01-10 14:56 compatible
-r--r--r-- 1 root root 28 2018-01-10 14:56 cpu-idle-states
-r--r--r-- 1 root root  8 2018-01-10 14:56 cpu-release-addr
-r--r--r-- 1 root root  4 2018-01-10 14:56 device_type
-r--r--r-- 1 root root  5 2018-01-10 14:56 enable-method
-r--r--r-- 1 root root  4 2018-01-10 14:56 linux,phandle
-r--r--r-- 1 root root  4 2018-01-10 14:56 name
-r--r--r-- 1 root root  4 2018-01-10 14:56 phandle
-r--r--r-- 1 root root  4 2018-01-10 14:56 reg
3.1 /of_node/clock-frequency
1|Z91:/sys/devices/system/cpu/cpu0/of_node # cat clock-frequency
cat clock-frequency
w5?
3.2 /of_node/compatible

获取CPU架构信息

w5?Z91:/sys/devices/system/cpu/cpu0/of_node # cat compatible
cat compatible
arm,cortex-a53
3.3 /of_node/cpu-idle-states

cat 不出

3.4 /of_node/cpu-release-addr

cat 不出

3.5 /of_node/device_type
Z91:/sys/devices/system/cpu/cpu0/of_node # cat device_type
cat device_type
cpu
3.6 /of_node/enable-method
psci
3.7 /of_node/linux,phandle

cat 不出

3.8 /of_node/name
cpu
3.9 /of_node/phandle

cat 不出

3.10 /of_node/reg

cat 不出

4. online

查询结果如下

Z91:/sys/devices/system/cpu/cpu0 # cat online
cat online
1

表示当前 CPU 正在使用

5. power

Z91:/sys/devices/system/cpu/cpu0/power # ls -all
ls -all
total 0
drwxr-xr-x 2 root root    0 2018-01-09 11:17 .
drwxr-xr-x 5 root root    0 2018-01-09 11:17 ..
-rw-r--r-- 1 root root 4096 2018-01-09 11:17 autosuspend_delay_ms
-rw-r--r-- 1 root root 4096 2018-01-09 11:17 control
-r--r--r-- 1 root root 4096 2018-01-09 11:17 runtime_active_time
-r--r--r-- 1 root root 4096 2018-01-09 11:17 runtime_status
-r--r--r-- 1 root root 4096 2018-01-09 11:17 runtime_suspended_time
5.1 /power/autosuspend_delay_ms

cat 不出

Z91:/sys/devices/system/cpu/cpu0/power # cat autosuspend_delay_ms
cat autosuspend_delay_ms
/system/bin/sh: cat: autosuspend_delay_ms: I/O error
1
5.2 /power/control
cat control
auto
5.3 /power/runtime_active_time
cat runtime_active_time
0
5.4 /power/runtime_status
cat runtime_status
unsupported
5.5 /power/runtime_suspended_time
cat runtime_suspended_time
0

6. subsystem

Z91:/sys/devices/system/cpu/cpu0/subsystem # ls -all
ls -all
total 0
drwxr-xr-x  4 root root    0 2018-01-10 15:15 .
drwxr-xr-x 19 root root    0 2018-01-09 11:17 ..
drwxr-xr-x  2 root root    0 2018-01-10 15:15 devices
drwxr-xr-x  2 root root    0 2018-01-10 15:15 drivers
-rw-r--r--  1 root root 4096 2018-01-10 15:15 drivers_autoprobe
--w-------  1 root root 4096 2018-01-10 15:15 drivers_probe
--w-------  1 root root 4096 2018-01-10 15:15 uevent
6.1 /subsystem/devices
Z91:/sys/devices/system/cpu/cpu0/subsystem/devices # ls -all
ls -all
total 0
drwxr-xr-x 2 root root 0 2018-01-10 15:15 .
drwxr-xr-x 4 root root 0 2018-01-10 15:15 ..
lrwxrwxrwx 1 root root 0 2018-01-10 15:17 cpu0 -> ../../../devices/system/cpu/cp
u0
lrwxrwxrwx 1 root root 0 2018-01-10 15:17 cpu1 -> ../../../devices/system/cpu/cp
u1
lrwxrwxrwx 1 root root 0 2018-01-10 15:17 cpu2 -> ../../../devices/system/cpu/cp
u2
lrwxrwxrwx 1 root root 0 2018-01-10 15:17 cpu3 -> ../../../devices/system/cpu/cp
u3
6.2 /subsystem/drivers

空文件夹

6.3 /subsystem/drivers_autoprobe
Z91:/sys/devices/system/cpu/cpu0/subsystem # cat drivers_autoprobe
cat drivers_autoprobe
1
6.4 /subsystem/drivers_probe
Z91:/sys/devices/system/cpu/cpu0/subsystem # cat drivers_probe
cat drivers_probe
/system/bin/sh: cat: drivers_probe: Permission denied
6.5 /subsystem/uevent
1|Z91:/sys/devices/system/cpu/cpu0/subsystem # cat uevent
cat uevent
/system/bin/sh: cat: uevent: Permission denied

7. topology

Z91:/sys/devices/system/cpu/cpu0/topology # ls -all
ls -all
total 0
drwxr-xr-x 2 root root    0 2018-01-09 11:17 .
drwxr-xr-x 5 root root    0 2018-01-09 11:17 ..
-r--r--r-- 1 root root 4096 2018-01-09 11:17 core_id
-r--r--r-- 1 root root 4096 2018-01-09 11:17 core_siblings
-r--r--r-- 1 root root 4096 2018-01-09 11:17 core_siblings_list
-r--r--r-- 1 root root 4096 2018-01-09 11:17 physical_package_id
-r--r--r-- 1 root root 4096 2018-01-09 11:17 thread_siblings
-r--r--r-- 1 root root 4096 2018-01-09 11:17 thread_siblings_list
7.1 topology/core_id
cat core_id
0
7.2 topology/core_siblings
cat core_siblings
f
7.3 topology/core_siblings_list
cat core_siblings_list
0-3
7.4 topology/physical_package_id
cat physical_package_id
0
7.5 topology/thread_siblings
cat thread_siblings
1
7.6 topology/thread_siblings_list
cat thread_siblings_list
0

8. uevent

查询结果如下

Z91:/sys/devices/system/cpu/cpu0 # cat uevent
cat uevent
OF_NAME=cpu
OF_FULLNAME=/cpus/cpu@0
OF_TYPE=cpu
OF_COMPATIBLE_0=arm,cortex-a53
OF_COMPATIBLE_N=1
MODALIAS=cpu:type:aarch64:feature:,0000,0001,0002,0003,0004,0005,0006,0007
法迪
关注
  • 1
    点赞
  • 踩
  • 4
    收藏
    觉得还不错? 一键收藏
  • 打赏
    打赏
  • 0
    评论
专栏目录
pcf8563_i2c1_r8_ruoge_ov2640通过给RTC驱动增加设备节点读取秒钟成功+直接读取I2C1获取秒钟值20160626_2201.7z
06-26
pcf8563_i2c1_r8_ruoge_ov2640通过给RTC驱动增加设备节点读取秒钟成功+直接读取I2C1获取秒钟值20160626_2201.7z http://blog.csdn.net/21cnbao/article/details/7919055 在Android源码树中添加userspace I2C读写工具（i2c-util） 本文使用的开发板是：杭州若格科技有限公司的全志R8。CPU：CPUARM Cortex-A8 更多芯片资料请参见全志官网： http://www.allwinnertech.com/clq/r/R8.html 通过/dev/i2c-n节点，用户可以在userspace直接访问板上的i2c外设寄存器，主要是透过I2C_RDWR这个IO控制命令将i2c_msg数组传递给kernel去执行。 开发板的/dev/i2c-1总线下挂有一片I2C的RTC：pcf8563。 root@android:/dev # cd /sys/class/i2c-adapter/ root@android:/sys/class/i2c-adapter # ll lrwxrwxrwx root root 1970-01-02 08:31 i2c-0 -> ../../devices/platform/sun5i-i2c.0/i2c-0 lrwxrwxrwx root root 1970-01-02 08:31 i2c-1 -> ../../devices/platform/sun5i-i2c.1/i2c-1 lrwxrwxrwx root root 1970-01-02 08:31 i2c-2 -> ../../devices/platform/sun5i-i2c.2/i2c-2 root@android:/sys/class/i2c-adapter # cd i2c-1 root@android:/sys/class/i2c-adapter/i2c-1 # ll drwxr-xr-x root root 1970-01-02 08:31 1-0051 --w------- root root 4096 1970-01-02 08:31 delete_device lrwxrwxrwx root root 1970-01-02 08:31 device -> ../../sun5i-i2c.1 drwxr-xr-x root root 1970-01-01 08:00 i2c-dev -r--r--r-- root root 4096 1970-01-02 08:31 name --w------- root root 4096 1970-01-02 08:31 new_device drwxr-xr-x root root 1970-01-01 08:00 power lrwxrwxrwx root root 1970-01-02 08:31 subsystem -> ../../../../bus/i2c -rw-r--r-- root root 4096 1970-01-01 08:00 uevent root@android:/sys/class/i2c-adapter/i2c-1 # root@android:/sys/class/i2c-adapter/i2c-1 # cd 1-0051/ root@android:/sys/class/i2c-adapter/i2c-1/1-0051 # ll lrwxrwxrwx root root 1970-01-02 10:18 driver -> ../../../../../bus/i2c/drivers/pcf8563 -r--r--r-- root root 4096 1970-01-02 10:18 modalias -r--r--r-- root root 4096 1970-01-02 10:18 name drwxr-xr-x root root 1970-01-02 10:18 power drwxr-xr-x root root 1970-01-02 10:18 rtc lrwxrwxrwx root root 1970-01-02 10:18 subsystem -> ../../../../../bus/i2c -rw-r--r-- root root 4096 1970-01-02 10:18 uevent root@android:/sys/class/i2c-adapter/i2c-1/1-0051 # cat name pcf8563 root@android:/sys/class/i2c-adapter/i2c-1/1-0051 # 注释：1-0051 1 表示 i2c-1这条I2C1总线上挂载的设备，如果是I2C2总线上挂载的设备，路径就是2-00XX了。 0051 一般的I2C设备的从机地址都是一个字节的，因为前两位为0x00（16进制的），后两位为pcf8563移位自后的I2C从机地址0x51（也是16进制的） 压缩包中的PCF8563-CN.pdf，datasheet告诉我们：I2C总线从地址：读，0A3H；写，0A2H。右移一位之后正好是0x51。 下面的代码可以完成这个功能： #include #include #include #include #include #include #include #include #include #include #include /* This is the structure as used in the I2C_RDWR ioctl call */ struct i2c_rdwr_ioctl_data { struct i2c_msg __user *msgs; /* pointers to i2c_msgs */ __u32 nmsgs; /* number of i2c_msgs */ }; int i2c_read_reg(char *dev, unsigned char *buf, unsigned slave_address, unsigned reg_address, int len) { struct i2c_rdwr_ioctl_data work_queue; unsigned char w_val = reg_address; int ret; int fd = open(dev, O_RDWR); if (!fd) { printf("Error on opening the device file\n"); return 0; } work_queue.nmsgs = 2; work_queue.msgs = (struct i2c_msg*)malloc(work_queue.nmsgs *sizeof(struct i2c_msg)); if (!work_queue.msgs) { printf("Memory alloc error\n"); close(fd); return 0; } ioctl(fd, I2C_TIMEOUT, 2); ioctl(fd, I2C_RETRIES, 1); (work_queue.msgs[0]).len = 1; (work_queue.msgs[0]).addr = slave_address; (work_queue.msgs[0]).buf = &w_val; (work_queue.msgs[1]).len = len; (work_queue.msgs[1]).flags = I2C_M_RD; (work_queue.msgs[1]).addr = slave_address; (work_queue.msgs[1]).buf = buf; ret = ioctl(fd, I2C_RDWR, (unsigned long) &work_queue); if (ret < 0) { printf("Error during I2C_RDWR ioctl with error code: %d\n", ret); close(fd); free(work_queue.msgs); return 0; } else { printf("read salve:x reg:x\n", slave_address, reg_address); close(fd); free(work_queue.msgs); return len; } } int i2c_write_reg(char *dev, unsigned char *buf, unsigned slave_address, unsigned reg_address, int len) { struct i2c_rdwr_ioctl_data work_queue; unsigned char w_val = reg_address; unsigned char w_buf[len+1]; int ret; w_buf[0] = reg_address; int fd = open(dev, O_RDWR); if (!fd) { printf("Error on opening the device file\n"); return 0; } work_queue.nmsgs = 1; work_queue.msgs = (struct i2c_msg*)malloc(work_queue.nmsgs *sizeof(struct i2c_msg)); if (!work_queue.msgs) { printf("Memory alloc error\n"); close(fd); return 0; } ioctl(fd, I2C_TIMEOUT, 2); ioctl(fd, I2C_RETRIES, 1); (work_queue.msgs[0]).len = 1 + len; (work_queue.msgs[0]).addr = slave_address; (work_queue.msgs[0]).buf = w_buf; memcpy(w_buf + 1, buf, len); ret = ioctl(fd, I2C_RDWR, (unsigned long) &work_queue); if (ret < 0) { printf("Error during I2C_RDWR ioctl with error code: %d\n", ret); close(fd); free(work_queue.msgs); return 0; } else { printf("write salve:x reg:x\n", slave_address, reg_address); close(fd); free(work_queue.msgs); return len; } } int main(int argc, char **argv) { unsigned int fd; unsigned int slave_address, reg_address; unsigned r_w; unsigned w_val; unsigned char rw_val; if (argc < 5) { printf("Usage:\n%s /dev/i2c-x start_addr reg_addr rw[0|1] [write_val]\n", argv[0]); return 0; } fd = open(argv[1], O_RDWR); if (!fd) { printf("Error on opening the device file %s\n", argv[1]); return 0; } sscanf(argv[2], "%x", &slave_address); sscanf(argv[3], "%x", &reg_address); sscanf(argv[4], "%d", &r_w); if (r_w == 0) { i2c_read_reg(argv[1], &rw_val, slave_address, reg_address, 1); printf("Read %s-%x reg %x, read value:%x\n", argv[1], slave_address, reg_address, rw_val); } else { if (argc < 6) { printf("Usage:\n%s /dev/i2c-x start_addr reg_addr r|w[0|1] [write_val]\n", argv[0]); return 0; } sscanf(argv[5], "%d", &w_val); if ((w_val & ~0xff) != 0) printf("Error on written value %s\n", argv[5]); rw_val = (unsigned char)w_val; i2c_write_reg(argv[1], &rw_val, slave_address, reg_address, 1); } return 0; } 在android/external/新建i2c-util目录，上述源代码存入android/external/i2c-util/i2c-util.c， R:\wyb\pcf8563_i2c1_r8_ruoge_ov2640\android\i2c-util\i2c-util.c 编写对应的Android.mk: LOCAL_PATH := $(call my-dir) include $(CLEAR_VARS) LOCAL_MODULE_TAGS := optional LOCAL_MODULE = i2c-util # LOCAL_SRC_FILES := $(call all-subdir-c-files) LOCAL_SRC_FILES := i2c-util.c include $(BUILD_EXECUTABLE) 编译Android后，上述工具会位于/system/bin目录。在电路板上使用它： R:\wyb\pcf8563_i2c1_r8_ruoge_ov2640\android\out\target\product\nuclear-evb\system\bin\i2c-util 如果android已经编译了，只需要执行： rootroot@rootroot-E400:~/wyb/pcf8563_i2c1_r8_ruoge_ov2640/android$ source build/envsetup.sh rootroot@rootroot-E400:~/wyb/pcf8563_i2c1_r8_ruoge_ov2640/android$ lunch 选择：18. nuclear_evb-eng （注意：不同的ubuntu电脑，序号可能不同，但是只需要选择nuclear_evb-eng编译选项前面的序号既可！！！！） rootroot@rootroot-E400:~/wyb/pcf8563_i2c1_r8_ruoge_ov2640/android$ rootroot@rootroot-E400:~/wyb/pcf8563_i2c1_r8_ruoge_ov2640/android$ cd i2c-util/ rootroot@rootroot-E400:~/wyb/pcf8563_i2c1_r8_ruoge_ov2640/android/i2c-util$ rootroot@rootroot-E400:~/wyb/pcf8563_i2c1_r8_ruoge_ov2640/android/i2c-util$ rootroot@rootroot-E400:~/wyb/pcf8563_i2c1_r8_ruoge_ov2640/android/i2c-util$ mm 详细的编译步骤： Connecting to 192.168.1.103:22... Connection established. To escape to local shell, press 'Ctrl+Alt+]'. Welcome to Ubuntu 14.04 LTS (GNU/Linux 3.13.0-24-generic x86_64) * Documentation: https://help.ubuntu.com/ Last login: Sun Jun 26 19:23:30 2016 from 192.168.1.101 rootroot@rootroot-E400:~$ cd wyb/pcf8563_i2c1_r8_ruoge_ov2640/ rootroot@rootroot-E400:~/wyb/pcf8563_i2c1_r8_ruoge_ov2640$ rootroot@rootroot-E400:~/wyb/pcf8563_i2c1_r8_ruoge_ov2640$ rootroot@rootroot-E400:~/wyb/pcf8563_i2c1_r8_ruoge_ov2640$ ll total 8606460 drwxr-xr-x 4 rootroot rootroot 4096 Jun 26 20:46 ./ drwxr-xr-x 19 rootroot rootroot 4096 Jun 25 06:50 ../ drwxrwxr-x 29 rootroot rootroot 4096 Jun 26 19:51 android/ drwxrwxr-x 8 rootroot rootroot 4096 Jun 26 16:35 lichee/ rootroot@rootroot-E400:~/wyb/pcf8563_i2c1_r8_ruoge_ov2640$ cd android/ rootroot@rootroot-E400:~/wyb/pcf8563_i2c1_r8_ruoge_ov2640/android$ rootroot@rootroot-E400:~/wyb/pcf8563_i2c1_r8_ruoge_ov2640/android$ rootroot@rootroot-E400:~/wyb/pcf8563_i2c1_r8_ruoge_ov2640/android$ source build/envsetup.sh including device/asus/grouper/vendorsetup.sh including device/asus/tilapia/vendorsetup.sh including device/generic/armv7-a-neon/vendorsetup.sh including device/generic/armv7-a/vendorsetup.sh including device/generic/mips/vendorsetup.sh including device/generic/x86/vendorsetup.sh including device/samsung/maguro/vendorsetup.sh including device/samsung/manta/vendorsetup.sh including device/samsung/toroplus/vendorsetup.sh including device/samsung/toro/vendorsetup.sh including device/softwinner/common/vendorsetup.sh including device/softwinner/crane-evb/vendorsetup.sh including device/softwinner/nuclear-256m/vendorsetup.sh including device/softwinner/nuclear-evb/vendorsetup.sh including device/softwinner/nuclear-r8m-evb/vendorsetup.sh including device/ti/panda/vendorsetup.sh including sdk/bash_completion/adb.bash rootroot@rootroot-E400:~/wyb/pcf8563_i2c1_r8_ruoge_ov2640/android$ rootroot@rootroot-E400:~/wyb/pcf8563_i2c1_r8_ruoge_ov2640/android$ rootroot@rootroot-E400:~/wyb/pcf8563_i2c1_r8_ruoge_ov2640/android$ lunch You're building on Linux Lunch menu... pick a combo: 1. full-eng 2. full_x86-eng 3. vbox_x86-eng 4. full_mips-eng 5. full_grouper-userdebug 6. full_tilapia-userdebug 7. mini_armv7a_neon-userdebug 8. mini_armv7a-userdebug 9. mini_mips-userdebug 10. mini_x86-userdebug 11. full_maguro-userdebug 12. full_manta-userdebug 13. full_toroplus-userdebug 14. full_toro-userdebug 15. crane_evb-eng 16. nuclear_256m-user 17. nuclear_256m-eng 18. nuclear_evb-eng 19. nuclear_r8m_evb-eng 20. full_panda-userdebug Which would you like? [full-eng] 18 ============================================ PLATFORM_VERSION_CODENAME=REL PLATFORM_VERSION=4.2.2 TARGET_PRODUCT=nuclear_evb TARGET_BUILD_VARIANT=eng TARGET_BUILD_TYPE=release TARGET_BUILD_APPS= TARGET_ARCH=arm TARGET_ARCH_VARIANT=armv7-a-neon HOST_ARCH=x86 HOST_OS=linux HOST_OS_EXTRA=Linux-3.13.0-24-generic-x86_64-with-Ubuntu-14.04-trusty HOST_BUILD_TYPE=release BUILD_ID=JDQ39 OUT_DIR=out ============================================ rootroot@rootroot-E400:~/wyb/pcf8563_i2c1_r8_ruoge_ov2640/android$ rootroot@rootroot-E400:~/wyb/pcf8563_i2c1_r8_ruoge_ov2640/android$ rootroot@rootroot-E400:~/wyb/pcf8563_i2c1_r8_ruoge_ov2640/android$ ll total 156 drwxrwxr-x 29 rootroot rootroot 4096 Jun 26 19:51 ./ drwxr-xr-x 4 rootroot rootroot 4096 Jun 26 20:46 ../ drwxrwxr-x 3 rootroot rootroot 4096 Jun 13 11:38 abi/ drwxrwxr-x 10 rootroot rootroot 4096 Jun 13 11:38 bionic/ drwxrwxr-x 5 rootroot rootroot 4096 Jun 13 11:38 bootable/ drwxrwxr-x 7 rootroot rootroot 4096 Jun 13 11:38 build/ drwxrwxr-x 11 rootroot rootroot 4096 Jun 13 11:38 cts/ drwxrwxr-x 18 rootroot rootroot 4096 Jun 13 11:38 dalvik/ drwxrwxr-x 18 rootroot rootroot 4096 Jun 13 11:38 development/ drwxrwxr-x 10 rootroot rootroot 4096 Jun 13 11:38 device/ drwxrwxr-x 3 rootroot rootroot 4096 Jun 13 11:38 docs/ drwxrwxr-x 159 rootroot rootroot 4096 Jun 13 11:39 external/ drwxrwxr-x 14 rootroot rootroot 4096 Jun 13 11:40 frameworks/ drwxrwxr-x 10 rootroot rootroot 4096 Jun 13 11:40 gdk/ drwxrwxr-x 10 rootroot rootroot 4096 Jun 13 11:40 hardware/ drwxr-xr-x 2 rootroot rootroot 4096 Jun 26 19:37 i2cscan/ drwxr-xr-x 2 rootroot rootroot 4096 Jun 26 19:52 i2c-util/ drwxrwxr-x 11 rootroot rootroot 4096 Jun 13 11:40 libcore/ drwxrwxr-x 4 rootroot rootroot 4096 Jun 13 11:40 libnativehelper/ -r--r--r-- 1 rootroot rootroot 87 Jun 13 11:38 Makefile drwxrwxr-x 8 rootroot rootroot 4096 Jun 13 11:40 ndk/ drwxrwxr-x 4 rootroot rootroot 4096 Jun 26 16:43 out/ drwxrwxr-x 8 rootroot rootroot 4096 Jun 13 11:40 packages/ drwxrwxr-x 5 rootroot rootroot 4096 Jun 13 11:40 pdk/ drwxrwxr-x 10 rootroot rootroot 4096 Jun 13 11:41 prebuilts/ drwxr-xr-x 2 rootroot rootroot 4096 Jun 25 13:01 read_pcf8563/ drwxrwxr-x 6 rootroot rootroot 4096 Jun 13 11:38 .repo/ drwxrwxr-x 51 rootroot rootroot 4096 Jun 13 11:41 sdk/ drwxrwxr-x 9 rootroot rootroot 4096 Jun 13 11:41 system/ drwxrwxr-x 4 rootroot rootroot 4096 Jun 13 11:41 tools/ rootroot@rootroot-E400:~/wyb/pcf8563_i2c1_r8_ruoge_ov2640/android$ rootroot@rootroot-E400:~/wyb/pcf8563_i2c1_r8_ruoge_ov2640/android$ rootroot@rootroot-E400:~/wyb/pcf8563_i2c1_r8_ruoge_ov2640/android$ cd i2c-util/ rootroot@rootroot-E400:~/wyb/pcf8563_i2c1_r8_ruoge_ov2640/android/i2c-util$ rootroot@rootroot-E400:~/wyb/pcf8563_i2c1_r8_ruoge_ov2640/android/i2c-util$ rootroot@rootroot-E400:~/wyb/pcf8563_i2c1_r8_ruoge_ov2640/android/i2c-util$ mm ============================================ PLATFORM_VERSION_CODENAME=REL PLATFORM_VERSION=4.2.2 TARGET_PRODUCT=nuclear_evb TARGET_BUILD_VARIANT=eng TARGET_BUILD_TYPE=release TARGET_BUILD_APPS= TARGET_ARCH=arm TARGET_ARCH_VARIANT=armv7-a-neon HOST_ARCH=x86 HOST_OS=linux HOST_OS_EXTRA=Linux-3.13.0-24-generic-x86_64-with-Ubuntu-14.04-trusty HOST_BUILD_TYPE=release BUILD_ID=JDQ39 OUT_DIR=out ============================================ PRODUCT_COPY_FILES frameworks/base/data/sounds/effects/ogg/Effect_Tick.ogg:system/media/audio/ui/Effect_Tick.ogg ignored. PRODUCT_COPY_FILES frameworks/base/data/sounds/effects/ogg/KeypressStandard.ogg:system/media/audio/ui/KeypressStandard.ogg ignored. PRODUCT_COPY_FILES frameworks/base/data/sounds/effects/ogg/KeypressSpacebar.ogg:system/media/audio/ui/KeypressSpacebar.ogg ignored. PRODUCT_COPY_FILES frameworks/base/data/sounds/effects/ogg/KeypressDelete.ogg:system/media/audio/ui/KeypressDelete.ogg ignored. PRODUCT_COPY_FILES frameworks/base/data/sounds/effects/ogg/KeypressReturn.ogg:system/media/audio/ui/KeypressReturn.ogg ignored. PRODUCT_COPY_FILES frameworks/base/data/sounds/effects/ogg/VideoRecord.ogg:system/media/audio/ui/VideoRecord.ogg ignored. PRODUCT_COPY_FILES frameworks/base/data/sounds/effects/ogg/camera_click.ogg:system/media/audio/ui/camera_click.ogg ignored. PRODUCT_COPY_FILES frameworks/base/data/sounds/effects/ogg/LowBattery.ogg:system/media/audio/ui/LowBattery.ogg ignored. PRODUCT_COPY_FILES frameworks/base/data/sounds/effects/ogg/Dock.ogg:system/media/audio/ui/Dock.ogg ignored. PRODUCT_COPY_FILES frameworks/base/data/sounds/effects/ogg/Undock.ogg:system/media/audio/ui/Undock.ogg ignored. PRODUCT_COPY_FILES frameworks/base/data/sounds/effects/ogg/Lock.ogg:system/media/audio/ui/Lock.ogg ignored. PRODUCT_COPY_FILES frameworks/base/data/sounds/effects/ogg/Unlock.ogg:system/media/audio/ui/Unlock.ogg ignored. PRODUCT_COPY_FILES frameworks/base/data/sounds/ringtones/ogg/Sceptrum.ogg:system/media/audio/ringtones/Sceptrum.ogg ignored. PRODUCT_COPY_FILES frameworks/base/data/sounds/effects/ogg/KeypressStandard_120.ogg:system/media/audio/ui/KeypressStandard.ogg ignored. PRODUCT_COPY_FILES frameworks/base/data/sounds/effects/ogg/KeypressSpacebar_120.ogg:system/media/audio/ui/KeypressSpacebar.ogg ignored. PRODUCT_COPY_FILES frameworks/base/data/sounds/effects/ogg/KeypressDelete_120.ogg:system/media/audio/ui/KeypressDelete.ogg ignored. PRODUCT_COPY_FILES frameworks/base/data/sounds/effects/ogg/KeypressReturn_120.ogg:system/media/audio/ui/KeypressReturn.ogg ignored. PRODUCT_COPY_FILES frameworks/base/data/sounds/notifications/ogg/Capella.ogg:system/media/audio/notifications/Capella.ogg ignored. PRODUCT_COPY_FILES frameworks/base/data/sounds/notifications/ogg/CetiAlpha.ogg:system/media/audio/notifications/CetiAlpha.ogg ignored. PRODUCT_COPY_FILES frameworks/base/data/sounds/notifications/ogg/Polaris.ogg:system/media/audio/notifications/Polaris.ogg ignored. PRODUCT_COPY_FILES frameworks/base/data/sounds/notifications/ogg/Pollux.ogg:system/media/audio/notifications/Pollux.ogg ignored. PRODUCT_COPY_FILES frameworks/base/data/sounds/notifications/ogg/Procyon.ogg:system/media/audio/notifications/Procyon.ogg ignored. PRODUCT_COPY_FILES frameworks/base/data/sounds/ringtones/ogg/Aquila.ogg:system/media/audio/ringtones/Aquila.ogg ignored. PRODUCT_COPY_FILES frameworks/base/data/sounds/ringtones/ogg/ArgoNavis.ogg:system/media/audio/ringtones/ArgoNavis.ogg ignored. PRODUCT_COPY_FILES frameworks/base/data/sounds/ringtones/ogg/Carina.ogg:system/media/audio/ringtones/Carina.ogg ignored. PRODUCT_COPY_FILES frameworks/base/data/sounds/ringtones/ogg/Centaurus.ogg:system/media/audio/ringtones/Centaurus.ogg ignored. PRODUCT_COPY_FILES frameworks/base/data/sounds/ringtones/ogg/Cygnus.ogg:system/media/audio/ringtones/Cygnus.ogg ignored. PRODUCT_COPY_FILES frameworks/base/data/sounds/ringtones/ogg/Draco.ogg:system/media/audio/ringtones/Draco.ogg ignored. PRODUCT_COPY_FILES frameworks/base/data/sounds/ringtones/ogg/Machina.ogg:system/media/audio/ringtones/Machina.ogg ignored. PRODUCT_COPY_FILES frameworks/base/data/sounds/ringtones/ogg/Orion.ogg:system/media/audio/ringtones/Orion.ogg ignored. PRODUCT_COPY_FILES frameworks/base/data/sounds/ringtones/ogg/Pegasus.ogg:system/media/audio/ringtones/Pegasus.ogg ignored. PRODUCT_COPY_FILES frameworks/base/data/sounds/ringtones/ogg/Pyxis.ogg:system/media/audio/ringtones/Pyxis.ogg ignored. PRODUCT_COPY_FILES frameworks/base/data/sounds/ringtones/ogg/Rigel.ogg:system/media/audio/ringtones/Rigel.ogg ignored. PRODUCT_COPY_FILES frameworks/base/data/sounds/ringtones/ogg/Scarabaeus.ogg:system/media/audio/ringtones/Scarabaeus.ogg ignored. PRODUCT_COPY_FILES frameworks/base/data/sounds/ringtones/ogg/Solarium.ogg:system/media/audio/ringtones/Solarium.ogg ignored. PRODUCT_COPY_FILES device/softwinner/nuclear-common/googleservice/gapps-jb-20121130-signed/system/tts/lang_pico/es-ES_zl0_sg.bin:system/tts/lang_pico/es-ES_zl0_sg.bin ignored. PRODUCT_COPY_FILES device/softwinner/nuclear-common/googleservice/gapps-jb-20121130-signed/system/tts/lang_pico/es-ES_ta.bin:system/tts/lang_pico/es-ES_ta.bin ignored. PRODUCT_COPY_FILES device/softwinner/nuclear-common/googleservice/gapps-jb-20121130-signed/system/tts/lang_pico/fr-FR_nk0_sg.bin:system/tts/lang_pico/fr-FR_nk0_sg.bin ignored. PRODUCT_COPY_FILES device/softwinner/nuclear-common/googleservice/gapps-jb-20121130-signed/system/tts/lang_pico/fr-FR_ta.bin:system/tts/lang_pico/fr-FR_ta.bin ignored. PRODUCT_COPY_FILES device/softwinner/nuclear-common/googleservice/gapps-jb-20121130-signed/system/tts/lang_pico/de-DE_gl0_sg.bin:system/tts/lang_pico/de-DE_gl0_sg.bin ignored. PRODUCT_COPY_FILES device/softwinner/nuclear-common/googleservice/gapps-jb-20121130-signed/system/tts/lang_pico/it-IT_cm0_sg.bin:system/tts/lang_pico/it-IT_cm0_sg.bin ignored. PRODUCT_COPY_FILES device/softwinner/nuclear-common/googleservice/gapps-jb-20121130-signed/system/tts/lang_pico/it-IT_ta.bin:system/tts/lang_pico/it-IT_ta.bin ignored. PRODUCT_COPY_FILES device/softwinner/nuclear-common/googleservice/gapps-jb-20121130-signed/system/tts/lang_pico/de-DE_ta.bin:system/tts/lang_pico/de-DE_ta.bin ignored. No private recovery resources for TARGET_DEVICE nuclear-evb make: Entering directory `/home/rootroot/wyb/pcf8563_i2c1_r8_ruoge_ov2640/android' target thumb C: i2c-util cd R:\wyb\pcf8563_i2c1_r8_ruoge_ov2640\android\out\target\product\nuclear-evb\system\bin C:\Users\Administrator.USER-20150913SZ>r: R:\wyb\pcf8563_i2c1_r8_ruoge_ov2640\android\out\target\product\nuclear-evb\system\bin>adb remount remount succeeded R:\wyb\pcf8563_i2c1_r8_ruoge_ov2640\android\out\target\product\nuclear-evb\system\bin> R:\wyb\pcf8563_i2c1_r8_ruoge_ov2640\android\out\target\product\nuclear-evb\system\bin>dir i2c* 驱动器 R 中的卷是 rootroot 卷的序列号是 1A1C-E71D R:\wyb\pcf8563_i2c1_r8_ruoge_ov2640\android\out\target\product\nuclear-evb\system\bin 的目录 2016/06/26 21:10 5,388 i2c-util 1 个文件 5,388 字节 0 个目录 268,337,782,784 可用字节 R:\wyb\pcf8563_i2c1_r8_ruoge_ov2640\android\out\target\product\nuclear-evb\system\bin> R:\wyb\pcf8563_i2c1_r8_ruoge_ov2640\android\out\target\product\nuclear-evb\system\bin>adb push i2c-util /data/ 29 KB/s (5388 bytes in 0.180s) R:\wyb\pcf8563_i2c1_r8_ruoge_ov2640\android\out\target\product\nuclear-evb\system\bin> 将R8的串口连接到windows电脑上。通过串口工具：比如Xshell5（有些人可能喜欢使用SecureCRT）读取R8的串口打印 （ubuntu下请使用minicom，使用方法请自行搜索了） 波特率选择：115200 N 8 1 等R8的android启动完成之后（LCD进android主界面），输入：su [ 37.990060] init: process 'ril-daemon', pid 950 exited [ 38.010049] init: process 'ril-daemon' killing any children in process group su root@android:/ # root@android:/ # root@android:/ # cd /data root@android:/data # root@android:/data # ll drwxrwxr-x system system 1970-01-11 08:58 anr drwxrwx--x system system 1970-01-02 08:01 app drwx------ root root 1980-10-01 11:03 app-asec drwxrwx--x system system 1970-01-02 08:01 app-lib drwxrwx--x system system 1980-10-01 11:03 app-private drwx------ system system 1980-10-01 11:04 backup drwxrwx--x system system 1970-01-02 08:00 dalvik-cache drwxrwx--x system system 2016-06-21 10:11 data drwxr-x--- root log 1980-10-01 11:03 dontpanic drwxrwx--- drm drm 1980-10-01 11:04 drm -rw-rw-rw- root root 5388 2016-06-26 21:10 i2c-util drwxr-x--x root root 1980-10-01 11:03 local drwxrwx--- root root 1970-01-01 08:00 lost+found drwxrwx--- media_rw media_rw 1980-10-01 11:03 media drwxrwx--t system misc 1980-10-01 11:03 misc -rw------- system system 154 1970-01-02 08:02 pointercal drwx------ root root 1970-01-02 08:00 property -rwxrwxrwx root root 5392 2016-06-25 13:01 read_pcf8563 drwxrwx--x system system 1980-10-01 11:03 resource-cache drwxr-x--- root shell 1980-10-01 11:03 ssh drwxrwxr-x system system 1970-01-02 08:00 system drwx------ system system 1970-01-02 08:03 tombstones drwx--x--x system system 1980-10-01 11:03 user root@android:/data # （让i2c-util具有可执行权限：） root@android:/data # chmod 777 i2c-util root@android:/data # root@android:/data # ll i2c* -rwxrwxrwx root root 5388 2016-06-26 21:10 i2c-util root@android:/data # root@android:/data # root@android:/data # （可选执行） root@android:/data # sync root@android:/data # 注意：串口打印会打印很多log信息。上面的步骤中的状态信息已经被过滤了。 如果你的串口打印过量的log信息，属于正常现象！ 如果不想要这么多的状态信息，可以考虑使用adb shell。 不过windows命令行中的adb shell不能够按TAB键自动补充，ubuntu的可以。 也许我们可以把windows的命令行特别设计一下（给它修正一下），让它也可以通过按TAB键来自动补全！^_ 读取pcf8563的第2个寄存器（秒钟值）： 表 5：BCD 格式寄存器概况 标明“－”的位无效 地址 寄存器名称 Bit7 Bit6 Bit5 Bit4 Bit3 Bit2 Bit1 Bit0 02h 秒 VL 00～59BCD 码格式数 root@android:/data # ./i2c-util /dev/i2c-1 0x51 0x02 0 read salve:51 reg:02 Read /dev/i2c-1-51 reg 2, read value:11 root@android:/data # ./i2c-util /dev/i2c-1 0x51 0x02 0 read salve:51 reg:02 Read /dev/i2c-1-51 reg 2, read value:12 root@android:/data # ./i2c-util /dev/i2c-1 0x51 0x02 0 read salve:51 reg:02 Read /dev/i2c-1-51 reg 2, read value:12 root@android:/data # ./i2c-util /dev/i2c-1 0x51 0x02 0 read salve:51 reg:02 Read /dev/i2c-1-51 reg 2, read value:13 root@android:/data # ./i2c-util /dev/i2c-1 0x51 0x02 0 read salve:51 reg:02 Read /dev/i2c-1-51 reg 2, read value:14 root@android:/data # ./i2c-util /dev/i2c-1 0x51 0x02 0 read salve:51 reg:02 Read /dev/i2c-1-51 reg 2, read value:14 root@android:/data # ./i2c-util /dev/i2c-1 0x51 0x02 0 read salve:51 reg:02 Read /dev/i2c-1-51 reg 2, read value:15 可以知道秒钟的值是变化的，基本上是一秒钟递增一次，I2C读取成功。 如果感兴趣的话，在执行读取命令的时候通过协议分析仪或者示波器来抓取I2C1的SCL/SDA的波形，来进行更加详尽的分析！^_ 方法二： 给出了一种复杂的解决办法（步骤从简，更多请参考开头的方法）： R:\wyb\pcf8563_i2c1_r8_ruoge_ov2640\lichee\linux-3.4\drivers\rtc\rtc-sun5i.c 给这个驱动文件增加设备节点：/dev/a20_r8_pcf8563 增加设备节点的方法请参考： http://blog.csdn.net/mirkerson/article/details/8844997 android驱动学习---led实验 然后在这个驱动文件的pcf8563_probe函数处截获它的client指针（struct i2c_client *client） client2 = client; 用户可以通过在userspace直接访问设备节点：/dev/a20_r8_pcf8563（open） 然后调用ioctl：ioctl(fd, 0x00000001, 0x02); 来获取第2个寄存器：秒钟的值了。 #include #include #include #include #include #include #include #include #include #include #include int fd; int main(int argc, char **argv) { fd = open("/dev/a20_r8_pcf8563", O_RDWR); ioctl(fd, 0x00000001, 0x02); close(fd); return 0; } 执行过程（直接从内核打印秒钟值了，也可以看到秒钟值大概也是一秒钟递增一次！）： root@android:/data # root@android:/data # ./read_pcf8563 [ 1397.060015] ****wyb drivers/rtc/rtc-sun5i.c:1169/r8_pcf8563_open()! open init.... [ 1397.071009] ****wyb drivers/rtc/rtc-sun5i.c:1130/r8_pcf8563_ioctl()! cmd=0x00000001 [ 1397.079076] ****wyb drivers/rtc/rtc-sun5i.c:1160/r8_pcf8563_ioctl()! cmd=0x00000001, value=0x00000046 [ 1397.088342] ****wyb drivers/rtc/rtc-sun5i.c:1177/r8_pcf8563_close()! close init root@android:/data # root@android:/data # ./read_pcf8563 [ 1398.409888] ****wyb drivers/rtc/rtc-sun5i.c:1169/r8_pcf8563_open()! open init.... [ 1398.411203] ****wyb drivers/rtc/rtc-sun5i.c:1130/r8_pcf8563_ioctl()! cmd=0x00000001 [ 1398.419273] ****wyb drivers/rtc/rtc-sun5i.c:1160/r8_pcf8563_ioctl()! cmd=0x00000001, value=0x00000047 [ 1398.428546] ****wyb drivers/rtc/rtc-sun5i.c:1177/r8_pcf8563_close()! close init root@android:/data # root@android:/data # root@android:/data # ./read_pcf8563 [ 1399.668173] ****wyb drivers/rtc/rtc-sun5i.c:1169/r8_pcf8563_open()! open init.... [ 1399.670939] ****wyb drivers/rtc/rtc-sun5i.c:1130/r8_pcf8563_ioctl()! cmd=0x00000001 [ 1399.679022] ****wyb drivers/rtc/rtc-sun5i.c:1160/r8_pcf8563_ioctl()! cmd=0x00000001, value=0x00000048 [ 1399.688299] ****wyb drivers/rtc/rtc-sun5i.c:1177/r8_pcf8563_close()! close init root@android:/data #
android获取手机cpu并判断是单核还是多核
01-04
代码如下:/** * Gets the number of cores available in this device, across all processors. * Requires: Ability to peruse the filesystem at “/sys/devices/system/cpu” * @return The number of cores, or 1 if failed to get result */ private int getNumCores() { //Private Class to display only CPU devices in the
android6.0系统 PowerManager深入分析（非常详细）
木叶风的博客
02-18 667
概述 一直以来,电源管理是电子产品设计中非常重要的环节，也是任何电子设备中最为重要的系统模块之一，优秀的电源管理方案，能够提供持久的续航能力，良好的用户体验，更能提升电子产品的竞争力。 移动设备的电量主要由两种元件消耗：CPU和显示屏，因此设法降低这两种元件的耗电量就是电源管理的关键，为移动设备设计的CPU大多有两种工作频率，为了省电，大部分时间内cpu都工作在降低频率下，只有进行密集计算时，...
androidWear/device/intel/spectralite/device.mk和androidWear/device/intel/spectralite/init.spectralite
abcdefg的专栏
09-04 381
可以进行拷贝文件： androidWear/device/intel/spectralite/device.mk # Unified build include device/google/clockwork/build/clockwork_unified_top_config.mk PRODUCT_COPY_FILES += \ device/intel/robby/ueventd
Android 7.0 耗电详情-应用消耗CPU电量统计原理
苏法迪的专栏
10-25 2425
1. 原理 应用CPU耗电计算 = APP运行中的每个CPU消耗时间和电量的总和，具体算法如下 获取每个CPU频率运行时间接口-BatteryStatsImpl.getTimeAtCpuSpeed 获取每个CPU频率消耗的电量-Profile.getAveragePowerForCpu 其中一些应用没有电量消耗问题或者电量不准确，重点看下 time_in_state 节点有没有生成和power...
Android app如何正确读写系统sys设备节点
热门推荐
u014341735的博客
04-25 1万+
Android app如何正确读写系统sys设备节点版权声明：本文为博主原创文章，允许转载，但请保留出处。Android 设备节点Android基于Linux内核。设备节点文件是设备驱动的逻辑文件，可以通过设备节点来访问设备驱动。很多设备信息都可存储在节点中。apk可以访问节点，获取设备信息或相关状态。读取设备节点应用层中，一般都能够读取设备节点。对于写节点这个操作，需要更高的root权限。(由于我
系统cpu主频查看设置
M120674的专栏
12-14 2645
一、 /sys/devices/system/cpu/cpu0 目录结构 /sys/devices/system/cpu/cpu0 Z91:/sys/devices/system/cpu/cpu0 # ls -al ls -al total 0 drwxr-xr-x 5 root root 0 2018-01-09 11:17 . drwxr-xr-x 13 root root 0 2018-01-09 11:17 .. lrwxrwxrwx 1 root root 0 2018-0...
Linux内核学习--电源管理
文艺小少年的博客
12-26 5267
目录 一、引言 二、调试手段 ------> 2.1、printf/printk ------> 2.2、proc ------------> 2.2.1、proc通过meminfo查找应用进程的内存泄漏问题 ------------> 2.2.2、proc/slabinfo ------> 2.3、smaps ------------> 2.3.1、虚拟内存 ------------> 2.3.2、驻留内存 ------------> 2.3.3、top 一
Android 系统 cpu0 目录查看 CPU 频率freq和策略policy
苏法迪的专栏
01-10 7079
一、 /sys/devices/system/cpu/cpu0 目录结构 /sys/devices/system/cpu/cpu0 Z91:/sys/devices/system/cpu/cpu0 # ls -al ls -al total 0 drwxr-xr-x 5 root root 0 2018-01-09 11:17 . drwxr-xr-x 13 root root
Android 高版本采集系统、进程CPU使用率的方式
Knight-ZXW的博客
08-24 2493
cpu 信息作为性能监控四大常用指标 (cpu、内存、网络、磁盘)之一，对衡量设备性能，分析、确定一些线上性能问题有着较为重要的作用。 本文简述了在Android平台下获取系统CPU使用相关信息的方式
新版Android开发教程.rar
12-14
� 采用了对有限内存、电池和 CPU 优化过的虚拟机 Dalvik ， Android 的运行速度比想象的要快很多。 � 运营商（中国移动等）的大力支持，产业链条的热捧。 � 良好的盈利模式（ 3/7 开），产业链条的各方：运营商、...
bpi_a64_android初步编译为LCD显示20170309_1442.7z
03-09
a64_android/lichee/brandy/u-boot-2014.07/arch/arm/cpu/armv7/sun50iw1p1/dram/libdram.o /home/wwt/a64/bpi_a64_android/lichee/brandy/u-boot-2014.07/arch/arm/cpu/armv7/sun50iw1p1/mmc/libmmc.o /home/wwt/a...
gc2135_parrotv1.1_r16m_验证完成VGA分辨率_20171010_1700没有外层目录.7z
10-10
开发板：深圳市索智科技有限公司SC3817R开发板，全志R16（CPU：Quad-Core Cortex-A7 CPU） http://www.allwinnertech.com/clq/r/R16.html 全志官网R16的简介 android4.4.2/linux3.4.39 2016/7/18 16:38 1、配置ov...
Android系统proc下查看cpuinfo的参数信息
苏法迪的专栏
01-09 1万+
一、命令 adb shell cat /proc/cpuinfo 我的脚本 Cpuinfo.bat，目的手机系统读取/proc/cpuinfo 文件中 CPU 的类型等多种信息 echo on adb shell cat /proc/cpuinfo > Cpuinfo.txt 导出数据如下 processor : 0 Processor : AArch64 Process
Android 后台服务监听按键(home,back,音量键)
苏法迪的专栏
03-23 1万+
0.启动1x1大小服务窗口进行监听变化，音量按键下按 不接受触摸屏事件。 public static final int FLAG_NOT_TOUCHABLE = 0x00000010; 当窗口可以获得焦点（没有设置FLAG_NOT_FOCUSALBE选项）时，仍然将窗口范围之外的点设备事件（鼠标、触摸屏）发送给后面的窗口处理。否则它将独占所有的点设备事件，而不管它们是不是发生在...
Android系统获取CPU和电池温度
苏法迪的专栏
01-31 1万+
Android系统获取CPU和电池温度等其他SOC温度信息 1.源码下载 https://github.com/sufadi/AndroidCpuTools 2.数据来源 adb shell "cat /sys/class/thermal/thermal_zone【编号】/type" adb shell "cat /sys/class/thermal/thermal_zo
Android 8.0 SE-Linux 问题解决-untrusted_app_25
苏法迪的专栏
05-11 1万+
1. 关键字 avc: denied 1.1 现象 01-03 10:31:35.585148 331 331 E SELinux : avc: denied { find } for service=xxx_applock pid=5499 uid=10087 scontext=u:r:untrusted_app_25:s0:c512,c768 tcontext=u:o...
Android 8.0 的广播无法接收 Background execution not allowed-PACKAGE_ADDED
苏法迪的专栏
06-06 9503
0. 前言 Android 8.0 的广播无法接收 Background execution not allowed-PACKAGE_ADDED，该现象已经确认。 基于对广播的严格控制，大幅度减少了静态广播给第三方应用的使用，也是出于限制后台启动的作用。 故类似 android.intent.action.PACKAGE_ADDED 已经无法通过静态广播来监听，但是我们可以通过动态广播注册监...
Android 获取 GPU 频率
苏法迪的专栏
02-08 9234
1. GPU 相关参数目录 /d/ged/hal/ Z91:/d/ged/hal # ls -all ls -all total 0 drwxr-xr-x 2 root root 0 1970-01-01 08:00 . drwxr-xr-x 4 root root 0 1970-01-01 08:00 .. -r--r--r-- 1 root root 0 1970-01-01 08:0...
/sys/devices/system/cpu/cpu*/online
最新发布
01-09
`/sys/devices/system/cpu/cpu*/online`是一个用于显示在线CPU核心的文件。在这个文件中，每个CPU核心都有一个对应的条目，用于指示该核心是否在线。 要查看在线的CPU核心，可以使用以下命令： ```shell cat /sys/devices/system/cpu/cpu*/online ``` 这将显示每个CPU核心的在线状态。如果一个核心在线，它的值将为1；如果一个核心离线，它的值将为0。 请注意，`/sys/devices/system/cpu/cpu*/online`文件中的`*`是一个通配符，用于匹配所有的CPU核心。因此，使用上述命令将显示所有CPU核心的在线状态。

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包

打赏作者

法迪

你的鼓励将是我创作的最大动力

¥1 ¥2 ¥4 ¥6 ¥10 ¥20
扫码支付：¥1
获取中
扫码支付

您的余额不足，请更换扫码支付或充值

打赏作者

实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值