On 13.12.2024 1:21 PM, Pengyu Luo wrote:
> I am not sure, huawei even provided the PMGK driver, but I think it is
> not loaded.
>
> If you talking about adsp cdsp and sdsp/slpi (this one should be
> unrelated), in the firmware driver files, some of them are same
> as the x13s one
>
> adspr.jsn
> adspua.jsn
> battmgr.jsn
> cdspr.jsn
>
> as for qcadsp8280.mbn should be different from x13s, in the old days,
> Gao and Chen used firmware from x13s totally, and the firmware didn't
> work (If I remember correctly, can't be loaded).
>
> As I know, the adsp firmware is tied with many things, even if huawei
> have moved many features to EC, the device still need it. (like normal
> usb function, audio? btw, this device can use audioreach-tplg.bin from
> x13s as well, I am not sure if it fits well.)
The jsn files are just descriptions of what "services" should be used
(including the battmgr service) for the userland utility, and nowadays
we have a kernel driver that does the same:
drivers/soc/qcom/qcom_pd_mapper.c
Start your ADSP with the firmware from your device and post the dmesg
output.
[...]
>>>>> + chosen {
>>>>> + #address-cells =3D <2>;
>>>>> + #size-cells =3D <2>;
>>>>> + ranges;
>>>>> +
>>>>> + framebuffer0: framebuffer@c6200000 {
>>>>> + compatible =3D "simple-framebuffer";
>>>>> + reg =3D <0x0 0xC6200000 0x0 0x02400000>;
>>>>> + width =3D <1600>;
>>>>> + height =3D <2560>;
>>>>> + stride =3D <(1600 * 4)>;
>>>>> + format =3D "a8r8g8b8";
>>>>> + };
>>>>> + };
>>>>
>>>> This should be redundant, as you should have efifb
>>>>
>>>
>>> I think no, it won't boot up without it(stuck at EFI stub: Booting Linux
>>> Kernel)
>>
>> Do you have CONFIG_EFI and CONFIG_FB_EFI enabled?
Very very weird. Are you booting with clk_ignore_unused pd_ignore_unused
in kernel cmdline?
Konrad
