devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Pengyu Luo <mitltlatltl@gmail.com>, konrad.dybcio@oss.qualcomm.com
Cc: andersson@kernel.org, chenxuecong2009@outlook.com,
	conor+dt@kernel.org, devicetree@vger.kernel.org,
	dmitry.baryshkov@linaro.org, gty0622@gmail.com,
	johan+linaro@kernel.org, konradybcio@kernel.org,
	krzk+dt@kernel.org, linux-arm-msm@vger.kernel.org,
	linux-kernel@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH 3/3] arm64: dts: qcom: sc8280xp: Add Huawei Matebook E Go (sc8280xp)
Date: Fri, 13 Dec 2024 13:27:03 +0100	[thread overview]
Message-ID: <3dfdf882-eb1d-498e-96b9-90c6cdcaa44c@oss.qualcomm.com> (raw)
In-Reply-To: <20241213122135.593760-1-mitltlatltl@gmail.com>

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

  reply	other threads:[~2024-12-13 12:27 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-11 15:37 [PATCH 0/3] arm64: dts: qcom: Introduce Huawei Matebook E Go Pengyu Luo
2024-12-11 15:37 ` [PATCH 1/3] dt-bindings: arm: qcom: Document Huawei Matebook E Go (sc8280xp) Pengyu Luo
2024-12-13 11:02   ` Krzysztof Kozlowski
2024-12-11 15:37 ` [PATCH 2/3] firmware: qcom: scm: Allow QSEECOM on " Pengyu Luo
2024-12-11 15:37 ` [PATCH 3/3] arm64: dts: qcom: sc8280xp: Add " Pengyu Luo
2024-12-12 17:13   ` Konrad Dybcio
2024-12-13  8:50     ` Pengyu Luo
2024-12-13 11:04       ` Konrad Dybcio
2024-12-13 12:21         ` Pengyu Luo
2024-12-13 12:27           ` Konrad Dybcio [this message]
2024-12-13 12:50             ` Pengyu Luo
2024-12-13 12:57               ` Konrad Dybcio
2024-12-13 13:50                 ` Pengyu Luo
2024-12-13 14:53                   ` Konrad Dybcio
2024-12-14 12:23       ` Pengyu Luo
2024-12-14 13:39         ` Dmitry Baryshkov
2024-12-14 14:48           ` Pengyu Luo
2024-12-14 16:01             ` Dmitry Baryshkov
2024-12-20 16:21           ` Johan Hovold
2024-12-21  5:26             ` Pengyu Luo
2025-01-08  8:49               ` Johan Hovold

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3dfdf882-eb1d-498e-96b9-90c6cdcaa44c@oss.qualcomm.com \
    --to=konrad.dybcio@oss.qualcomm.com \
    --cc=andersson@kernel.org \
    --cc=chenxuecong2009@outlook.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=gty0622@gmail.com \
    --cc=johan+linaro@kernel.org \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mitltlatltl@gmail.com \
    --cc=robh@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).