Open Saikatsaha1996 opened 3 days ago
Hi! Well those pmic-glink errors are quite persistent and I have no idea how to fix them.
On the WDK it doesn't really affect anything (that I notice). On the HP Omnibook X14 (x1e laptop) I get exactly the same errors, but battery life is good and suspend / resume works. :man_shrugging:
Hi! Well those pmic-glink errors are quite persistent and I have no idea how to fix them.
On the WDK it doesn't really affect anything (that I notice). On the HP Omnibook X14 (x1e laptop) I get exactly the same errors, but battery life is good and suspend / resume works. 🤷♂️
Thank you so much for your response..
I actually have charging issue for my device.. so it can be reason for charging?
Even my device battery status also red & reporting unknown
This is something else. Looks like the adsp firmware is not loaded.
This is something else. Looks like the adsp firmware is not loaded.
Adsp loaded and booted up successfully armbian3.txt
[ 5.231943] remoteproc remoteproc2: powering up 17300000.remoteproc
[ 5.231951] remoteproc remoteproc2: Booting fw image qcom/sm8350/realme/porsche/adsp.mbn, size 17078428
[ 5.516803] remoteproc remoteproc2: remote processor 17300000.remoteproc is now up
hmm do you have the pd-mapper on in the kernel , or do you use pd-mapper and qrtr as user mode processes? Also, if there are defining jsn files, are they available (at the same place as the firmware) and loaded?
hmm do you have the pd-mapper on in the kernel , or do you use pd-mapper and qrtr as user mode processes? Also, if there are defining jsn files, are they available (at the same place as the firmware) and loaded?
Yea.. pd-mapper available.. https://github.com/Saikatsaha1996/build/blob/a4621a4808ff53b0104bee2ec3206dc4fcbcc415/config/boards/xiaomi-elish.conf#L76
And jsn file also available all firmwares https://github.com/Saikatsaha1996/firmware/tree/porsche/qcom/sm8350/realme/porsche
hmm do you have the pd-mapper on in the kernel , or do you use pd-mapper and qrtr as user mode processes? Also, if there are defining jsn files, are they available (at the same place as the firmware) and loaded?
Okay most probably charger_pd adsp.jsn file is missing? https://github.com/Saikatsaha1996/android_kernel_oneplus_sm8350/blob/9c86b0cf0172c8ca42ed377af48c0e877ba7a050/arch/arm64/boot/dts/vendor/qcom/lahaina.dtsi#L5591
hmm do you have the pd-mapper on in the kernel , or do you use pd-mapper and qrtr as user mode processes? Also, if there are defining jsn files, are they available (at the same place as the firmware) and loaded?
Okay got it this one right? https://github.com/Saikatsaha1996/firmware-realme-porsche/blob/porsche/lib/firmware/qcom/sm8350/porsche/battmgr.jsn
Finally qcom battmgr working.. with battmgr.jsn
but still device not charging..
are there other .jsn files? I don't know enough to assist in debugging it deeper.
are there other .jsn files? I don't know enough to assist in debugging it deeper.
But magically you give me a strong clues for fix my battery manager.. thank you so much 😁..
This is my total full firmwares.. no more jsn file available https://github.com/Saikatsaha1996/firmware-realme-porsche/tree/porsche/lib/firmware/qcom/sm8350/porsche
Still my device not charging.. only battery status reporting currect..
Hmm looks to me that there are other .jsn files (like adspr.jsn). For sc8280xp it is usually four files, but yours is sm8350:
Those 4 files are in the firmware directory, too. :man_shrugging: I would recommend to have them in the initramfs, like here example only, need to do this with your paths and firmwares). What I can tell (from binwalking UEFI updates) is that it appears to be usually these 4 .jsn files you need.
Hmm looks to me that there are other .jsn files (like adspr.jsn). For sc8280xp it is usually four files, but yours is sm8350:
Those 4 files are in the firmware directory, too. 🤷♂️ I would recommend to have them in the initramfs, like here example only, need to do this with your paths and firmwares). What I can tell (from binwalking UEFI updates) is that it appears to be usually these 4 .jsn files you need.
I already all does have.. like
https://github.com/Saikatsaha1996/firmware/blob/porsche/qcom/sm8350/realme/porsche/adspr.jsn
https://github.com/Saikatsaha1996/firmware/blob/porsche/qcom/sm8350/realme/porsche/adspua.jsn
https://github.com/Saikatsaha1996/firmware/blob/porsche/qcom/sm8350/realme/porsche/battmgr.jsn
https://github.com/Saikatsaha1996/firmware/blob/porsche/qcom/sm8350/realme/porsche/cdspr.jsn
https://github.com/Saikatsaha1996/firmware/blob/porsche/qcom/sm8350/realme/porsche/modemr.jsn
https://github.com/Saikatsaha1996/firmware/blob/porsche/qcom/sm8350/realme/porsche/slpir.jsn
https://github.com/Saikatsaha1996/firmware/blob/porsche/qcom/sm8350/realme/porsche/slpius.jsn
Hmm looks to me that there are other .jsn files (like adspr.jsn). For sc8280xp it is usually four files, but yours is sm8350: Those 4 files are in the firmware directory, too. 🤷♂️ I would recommend to have them in the initramfs, like here example only, need to do this with your paths and firmwares). What I can tell (from binwalking UEFI updates) is that it appears to be usually these 4 .jsn files you need.
I already all does have.. like
https://github.com/Saikatsaha1996/firmware/blob/porsche/qcom/sm8350/realme/porsche/adspr.jsn https://github.com/Saikatsaha1996/firmware/blob/porsche/qcom/sm8350/realme/porsche/adspua.jsn https://github.com/Saikatsaha1996/firmware/blob/porsche/qcom/sm8350/realme/porsche/battmgr.jsn https://github.com/Saikatsaha1996/firmware/blob/porsche/qcom/sm8350/realme/porsche/cdspr.jsn https://github.com/Saikatsaha1996/firmware/blob/porsche/qcom/sm8350/realme/porsche/modemr.jsn https://github.com/Saikatsaha1996/firmware/blob/porsche/qcom/sm8350/realme/porsche/slpir.jsn https://github.com/Saikatsaha1996/firmware/blob/porsche/qcom/sm8350/realme/porsche/slpius.jsn
Finally solved my device charging issue.. now device charging at full speed.. but still one issue present.. like battery charging indicator not showing.. only battery persentage increased & dmesg outputs..
That is way more talkative than the X13s :laughing: Honestly, no idea.
Hi ! I am Saikat Saha I am porting my downstream device to mainline.. I am facing some issues.. which you faced already.. My issue
I want to know how you fix it ? Please share some suggestions if possible..