@all

Hi guys, I've changed SmartReflex efuse values calculations, will you please test .debs from here and report (especially those of you having problems with SR vdd1 enabled)

And PLEASE test it with dsp profile loaded, not with your custom profile or some crappatch/batterysuckpatch installed.

@hurrian - as it seems your device is one of the most unstable ones re SR, will you please test this kernel. I will really appreciate that.

BTW this kernel has some other goodies as well:

- device should no longer enter reboot mini-loop with charger/USB cable connected when you try to power-off/restart it.
- camera driver could capture directly to framebuffer memory (those of you who don't know what is that, just leave it)

Wish you all happy New Year

.....Christmas again?
Download in progress... and ready to try to make it crash!
(wishing your kernel will win...)

...
Did you prepared also the bootimg package?

Yes, shall I upload it?

EDIT:
Uploaded.

Yes, thanks.

There is one thing that i can't understand...
Why not add a number to the package version to identify a new release?

..flashing

Great improvement: the phone doesn't bomb a few seconds after loading the "dsp" profile.

I'll be back tomorrow when I test H.264 Baseline playback because (1) I think I broke my codecs somehow (I didn't, the video was just broken), and (2) I wiped my microsd card accidentally a few weeks ago. I'm going to encode some content tonight while I watch the fireworks. Happy new year, guys!

EDIT: Initial test result: phone doesnt bomb trying to play the video; dsp just clams up and closes the video stream gracefully. The video I played was whatever the highest quality setting was on the CSSU-T camera-ui2.

I'm going to retry the experiment with H.264 Baseline tomorrow.

At last . Getting closer.

Anyway, if dsp profile is stable you could also check what voltages SR is calculating compared to your custom profile.

@freemangordon

sorry ... while booting with vdd1=1:

[ 38.094970] bridge_deh_notify: ********** DEVICE EXCEPTION **********
[ 38.095001] bridge_deh_notify: DSP_SYSERROR, err_info = 0x102
[ 38.095184] print_dsp_trace_buffer:
[ 38.095184] ����\96\96\96\96�\04\01\14�% �6& h�% h:& @\80\03��\01���\1c�\1c��������T!T!_�_��\1c�\1cT!T! T!������������`\01��������P\8e�\10������_�_�\01�\1 4\14\10\10\10\0e\10PA�\10\15\10T!��\01\01�� \01�\14\14������������X\8e�\10T!4I�\10\8d�\10\10\8 0@�\10p\98J �6& ��������T!_�_���������_�_�_�_�����xJ�\10\18������� �T!����\020\0f\0e\01T� P� \08\13�\02\01\02\10\01`\01\02\10\15_\ff\ff\ff\908P �\10�d �\ff\ff\ff\8d�\10\10�\01<^�\10\1c^�\10@� \10�w�\10�a�\10�7& �w�\10\10d8P�\10\01\10�� [\02
[ 38.095245] U\04\80\05O _\ff�\ff`\92 o x�\01 \07
[ 38.095703] procwrap_detach: deprecated dspbridge ioctl

the profile is:
# DO NOT EDIT THIS FILE - CREATE A COPY OF IT FOR CUSTOMIZATION
# minimum frequency to use
MINFREQ=125
# maximum frequency to use
MAXFREQ=805
# list of frequency configurations: each "frequency:volt,dsprate"
FREQS="0:25,90 125:25,90 250:35,180 500:40,360 550:45,400 600:48,430 720:52,520 805:56,600 850:60,600 900:60,600 950:60,600 1000:60,600 1100:72,600 1150:72,600"
SMARTREFLEX_VDD1=1
SMARTREFLEX_VDD2=1
GOVERNOR=ondemand
UP_THRESHOLD=95
SAMPLING_RATE=300000
IGNORE_NICE_LOAD=0
POWERSAVE_BIAS=0

---------

New kernel, same profile, vdd1=0: NO crash.
>>
[ 10.527801] dspbridge_init: 600000 bytes @ 80e00000
>>

Recording video with vdd1=1 results in a black screen and the camera-ui crash.

Recording with vdd1=0 works but in dmesg appears a lot of:

[ 695.077026] memory_sync_page: no page for 46b50000
[ 695.077056] proc_memory_sync: InValid address parameters 46b10080 86200
[ 695.100433] memory_sync_page: no page for 46bbb000
[ 695.100463] proc_memory_sync: InValid address parameters 46b97080 86200
[ 695.114990] memory_sync_page: no page for 45180000
[ 695.115020] proc_memory_sync: InValid address parameters 4511c080 86200
[ 695.117980] memory_sync_page: no page for 4532b000

Now i'm going to retry with standard dsp profile...

UPDATE:
Same dsp crash during boot also with standard dsp profile...
Sorry going back disabling VDD1.

@xes: not so bad, DSP being unstable when overclocked is somehow expected. The very good news is that MPU is stable. Next year I will compile a new version which will make a little voltage boost when DSP is overclocked, thus making SR rock stable(hopefully).

EDIT:
memory_sync_page is a different story, it is not related to SR

EDIT2:
or you could move your DSP overclocking frequencies to higher MPU frequencies i.e. instead of 720,520 805,600 you could try 720,480 805,560 850,600

Post of the year 2011.

EDIT: Is there any way you can measure DSP load? I think that's a better metric of raising/lowering DSP voltages.

Nice suggestion.... i'll try this. Thanks!