From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Linux ARM <linux-arm-msm@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Linux Devicetree <devicetree@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
"Aram M." <aram.minasyan@yahoo.com>
Subject: Qualcomm Snapdragon 8cx Gen 2 not supported yet?
Date: Thu, 22 Feb 2024 13:26:05 +0700 [thread overview]
Message-ID: <Zdbo_aXDZ8YLIiQh@archie.me> (raw)
[-- Attachment #1: Type: text/plain, Size: 1203 bytes --]
Hi,
Aram M. <aram.minasyan@yahoo.com> opened Bugzilla ticket requesting devicetree
support for sc8180xp [1]. He wrote:
> The Linux kernel 6.7.5 only boots in ACPI mode on DELL Inspiron 14 3420
> with Qualcomm Snapdragon 8cx Gen 2 (sc8180xp).
> A lot of hardware is not functional, this maybe due to missing device tree?
> Built in keyboard and PCIe devices not working, only runs on USB connected disk, keyboard & peripherals.
>
> Support for sc8180x & sc8280xp devices exist, but not for sc8180xp devices.
>
> Under arch/arm64/boot/dts/qcom in source tree the files
> sc8180x-pmics.dtsi, sc8180x.dtsi, sc8280xp-pmics.dtsi, sc8280xp.dtsi.
> exist, but none for sc8180xp, which would be used for specific hardware dts
> files?
> Maybe the hardware is similar enough to sc8180x? But of course I have no idea.
>
> It would be nice for the keyboard to function without the device tree, seems like module i2c_qcom_geni doesn't work without dtb?
>
>
> I have attached dmesg output.
Aram, can you submit devicetree patch supporting your device?
Thanks.
[1]: https://bugzilla.kernel.org/show_bug.cgi?id=218512
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
reply other threads:[~2024-02-22 6:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Zdbo_aXDZ8YLIiQh@archie.me \
--to=bagasdotme@gmail.com \
--cc=andersson@kernel.org \
--cc=aram.minasyan@yahoo.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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