Cpufreq folder is missing


#1

Hi,

‘cpufreq’ folder is not present under any cpus folder. I need to tune it for high performance.

ls /sys/devices/system/cpu/cpu1/
cache cpuidle of_node online power subsystem topology uevent

please suggest.

Thanks


#2

Hi @Anonymous, could you tell which kernel branch are you using? And are you using kernel config hikey960_defconfig rather than defconfig?


#3

Hi Leo-yan,

please find below the kernel version
make kernelversion
4.4.76

If I use defconfig the board itself is not booting up.
I tried with default hikey960_defconfig, the cpufreq folder is not present.
please suggest.

Thanks


#4

Thanks for the info, I will check soon.


#5

Hi @Anonymous, I have checked the latest 4.4 Hikey kernel branch:
make kernelversion
4.4.83

So could you check if you are using latest code base for kernel 4.4:
https://android.googlesource.com/kernel/hikey-linaro branch: android-hikey-linaro-4.4


#6

okay I will try and let you know.


#7

Hi,

Sorry for late response.
Even with latest kernel 4.4.83 also the cpufreq folder is not present.

adb shell uname -a
Linux localhost 4.4.83-g85a6b50 #2 SMP PREEMPT Wed Sep 6 13:21:45 IST 2017 aarch64

adb shell "ls /sys/devices/system/cpu/cpu0/"
cache cpuidle of_node online power subsystem topology uevent

please suggest.

Thanks


#8

Hi @Anonymous, could you check below info are existed after the kernel booting up? And please note if you have updated your DTB?

dmesg | grep mailbox
[ 1.027567] hi3660-mbox e896b000.mailbox: Mailbox enabled

ls /sys/kernel/debug/clk/cpu-cluster.0
ls /sys/kernel/debug/clk/cpu-cluster.1

ls /sys/devices/platform/cpufreq-dt/


#9

Hi Leo-yan,

All files are present.
please find below info:

adb shell dmesg | grep mailbox
[ 0.415909] hi3660-mbox e896b000.mailbox: Mailbox enabled

Thanks


#10

But still cpufreq folder is not present.
adb shell "ls /sys/devices/system/cpu/cpu0/"
cache cpuidle of_node online power subsystem topology uevent


#11

Hi,

To cross verify my images, I tried images from below link, but device itself is not booting up.
http://builds.96boards.org/snapshots/hikey960/linaro/aosp-master/latest?dl=/snapshots/hikey960/linaro/aosp-master/latest/hikey960-img-247.zip

please suggest.

Thanks


#12

Hi @Anonymous, could you help to paste the log for booting failure? I want to check where the booting failure happen? And want to confirm the booting images (ARM-TF/UEFI firmwares) are you using?


#13

Hi,

Booting is stuck with below message:
load_kernel: boot_from_bl31: boot to trusted firmware. addr=0x0000000

– And want to confirm the booting images (ARM-TF/UEFI firmwares) are you using?
Are you talking about bootloader? I am using the default bootloader which came with the board.
Where can I get latest bootlader binary?

Thanks


#14

Hi @Anonymous, you could update the firmwares from Android AOSP repo:

https://android.googlesource.com/device/linaro/hikey/+/master/installer/hikey960/

You could refer the README and shell script for updating booting images:
https://android.googlesource.com/device/linaro/hikey/+/master/installer/hikey960/README
https://android.googlesource.com/device/linaro/hikey/+/master/installer/hikey960/flash-all.sh


#15

Hi Leo-yan,

After flashing images from below path the device is not booting up and not even going to fastboot mode, so after trying recovery steps fastboot mode is working.
https://android.googlesource.com/device/linaro/hikey/+/master/installer/hikey960/

Please share us any stable bootloader image link.

Thanks


#16

Hi @Anonymous,

From my understanding, the stable bootloader images are placed in: https://android.googlesource.com/device/linaro/hikey/+/master/installer/hikey960/; this folder is official releasing for Android AOSP on Hikey960, so this is why I suggest you to use the booting images in this folder. If you use recovery steps to burn images in this folder, the board should can boot up successfully. Otherwise this will be serious issue and we need fix ASAP.

BTW, there have some dependency between image sec_xloader.img and lpm3.img, so should flash these two images together. There also some changes in these two images to support CPUFreq driver. After you burn images in the folder: https://android.googlesource.com/device/linaro/hikey/+/master/installer/hikey960/, could you confirm now CPUFreq can work well or not?

We also has another repo to maintain booting images: https://github.com/96boards-hikey/tools-images-hikey960; the booting images are in this folder usually is same with Android AOSP images, but if Hisilicon wants to upgrade the booting images, the landing team will firstly update images into https://github.com/96boards-hikey/tools-images-hikey960, and after verification finally these booting images will be merged into https://android.googlesource.com/device/linaro/hikey/+/master/installer/hikey960/.


#17

Hi Leo,

Thanks for your support.
The bootloader from below location is not working, the device will not even boots up.
https://android.googlesource.com/device/linaro/hikey/+/master/installer/hikey960/

Images are working from below location :

Thanks


#18

Thanks for reporting back, @Anonymous.

Today I will leave my desktop, but I will try the Android AOSP image ASAP when I have chance to do that. Usually Android AOSP is important for maintenance.


#19

MD5SUM of files in these two branches are exactly the same. I just double-checked. So, the only difference is you may did a recovery-mode update using [2]; but you can only do a ‘fastboot-mode’ update using [1].

[1] https://android.googlesource.com/device/linaro/hikey/+/master/installer/hikey960/ branch: master
[2] https://github.com/96boards-hikey/tools-images-hikey960 branch: master

Anyway, you now recovered your hikey960 board using [2]. From this point on, I believe, ‘fastboot-mode’ update using [1] should work for you too.

PS: Considering in the mid of all your testings, you may have modified your board in some unwanted way, which caused [1] doesn’t boot. This may happen.


#20

Considering in the mid of all your testings, you may have modified your board in some unwanted way, which caused [1] doesn’t boot.
My board was working properly after using images from [2].
As you said I tried update using [1] through fastboot-mode, but again board is not booting up. Need to follow recovery step using [2].