From: Mostafa Saleh <smostafa@google.com>
To: Jens Glathe <jens.glathe@oldschoolsolutions.biz>
Cc: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/7] arm64: dts: qcom: IdeaCentre Mini 01Q8X10 Hamoa + Purwa
Date: Tue, 8 Sep 2026 17:47:15 +0000 [thread overview]
Message-ID: <aqBKI0Fg3ZqYPOJh@google.com> (raw)
In-Reply-To: <9762659c-fbde-4887-8da8-200db7dfad09@oldschoolsolutions.biz>
On Tue, Sep 08, 2026 at 05:04:44PM +0200, Jens Glathe wrote:
> Hi Mostafa,
>
> On 9/8/26 14:09, Mostafa Saleh wrote:
> > I don't have a display connected (never managed/bothered to enable it).
> >
> > Can you please share your .config, I can test with it, just to eliminate
> > the possibility it's causing the issue.
> >
> > Thanks,
> > Mostafa
>
> This is my .config [1].
>
> [1]: https://pastebin.com/QhDizqCB
Thanks! I tested with your config plus
- CONFIG_EFI_ARMSTUB_DTB_LOADER=y otherwise I can't load my device
tree from UEFI shell
- CONFIG_SERIAL_QCOM_GENI=y, otherwise I can't see the console.
Booting in EL2 is similar to before with SMMUv2 errors.
Booting in EL1 hangs with timeouts and missing suppliers:
[ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x512f0011]
[ 0.000000] Linux version 7.3.0-rc1-next-20260904+ (smostafa@mostafa1.c.googlers.com) (Debian clang version 21.1.8 (3), Debian LLD 21.1.8) #2 SMP PREEMPT_DYNAMIC Tu6
[ 0.000000] KASLR enabled
[ 0.000000] Machine model: Lenovo IdeaCentre Mini 01Q8X10 (Purwa)
[ 0.000000] earlycon: qcom_geni0 MMIO:0x0000000000894000 (options '')
[ 0.000000] printk: legacy bootconsole [qcom_geni0] enabled
[ 0.000000] CPU features: SYS_ID_AA64MMFR0_EL1[63:60]: forced to 1
[ 0.000000] ITS@0x0000000017040000: Devices Table too large, reduce ids 32->19
[ 0.000000] ITS@0x0000000017040000: Devices too large, reduce ITS pages 1024->256
[ 0.163152] qcom-pcie 1c00000.pcie: supply vdda not found, using dummy regulator
[ 0.163313] qcom-pcie 1c08000.pcie: supply vdda not found, using dummy regulator
[ 0.168334] clk: Not disabling unused clocks
[ 0.168336] PM: genpd: Not disabling unused power domains
[ 0.170770] qcom-pcie 1c00000.pcie: supply vddpe-3v3 not found, using dummy regulator
[ 0.178347] qcom-pcie 1c08000.pcie: supply vddpe-3v3 not found, using dummy regulator
[ 0.184718] qcom-pcie 1c00000.pcie: supply vdda not found, using dummy regulator
[ 0.211932] Warning: unable to open an initial console.
[ 0.212057] qcom-pcie 1c00000.pcie: supply vddpe-3v3 not found, using dummy regulator
[ 0.213907] qcom-pcie 1c08000.pcie: supply vdda not found, using dummy regulator
[ 0.213928] qcom-pcie 1c08000.pcie: supply vddpe-3v3 not found, using dummy regulator
[ 0.244210] qcom-pcie 1c08000.pcie: supply vdda not found, using dummy regulator
[ 0.244275] qcom-pcie 1c00000.pcie: supply vdda not found, using dummy regulator
[ 0.251833] qcom-pcie 1c08000.pcie: supply vddpe-3v3 not found, using dummy regulator
[ 0.259418] qcom-pcie 1c00000.pcie: supply vddpe-3v3 not found, using dummy regulator
[ 10.213618] qcom-pcie 1bf8000.pcie: supply vdda not found, using dummy regulator
[ 10.214873] arm-smmu 3da0000.iommu: deferred probe timeout, ignoring dependency
[ 10.228713] arm-smmu 3da0000.iommu: probe with driver arm-smmu failed with error -110
With that config my device tree doesn't boot also and hangs similar
to above.
I believe we are testing on different SoCs from your fastfetch:
CPU: Qualcomm Snapdragon X Elite 1E80100 (8) @ 2.96 GHz
While mine:
CPU: Qualcomm Snapdragon X Elite 1P42100 (8) @ 2.96 GHz
I enabled CONFIG_QCOM_SOCINFO which shows:
[root@alarm ~]# cat /sys/devices/soc0/soc_id
635 # which does not exist in qcom,ids.h
[root@alarm ~]# cat /sys/devices/soc0/revision
1.0
Thanks,
Mostafa
>
> with best regards
>
> Jens
>
next prev parent reply other threads:[~2026-09-08 17:47 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-05 9:28 Jens Glathe via B4 Relay
2026-09-05 9:28 ` [PATCH 1/7] dt-bindings: arm: qcom: Distinguish IdeaCentre Mini 01Q8X10 SKUs Jens Glathe via B4 Relay
2026-09-08 9:04 ` Krzysztof Kozlowski
2026-09-05 9:28 ` [PATCH 2/7] arm64: dts: qcom: Split IdeaCentre Mini into a common DTSI Jens Glathe via B4 Relay
2026-09-07 8:49 ` Konrad Dybcio
2026-09-05 9:28 ` [PATCH 3/7] arm64: dts: qcom: Add Purwa IdeaCentre Mini 01Q8X10 Jens Glathe via B4 Relay
2026-09-07 8:49 ` Konrad Dybcio
2026-09-05 9:28 ` [PATCH 4/7] arm64: dts: qcom: ideacentre-mini: Build the Hamoa EL2 DTB Jens Glathe via B4 Relay
2026-09-07 8:49 ` Konrad Dybcio
2026-09-05 9:29 ` [PATCH 5/7] arm64: dts: qcom: ideacentre-mini: Fix the second M.2 3V3 rail Jens Glathe via B4 Relay
2026-09-07 8:55 ` Konrad Dybcio
2026-09-05 9:29 ` [PATCH 6/7] arm64: dts: qcom: ideacentre-mini: Wire up DP sound names and VA macro Jens Glathe via B4 Relay
2026-09-07 8:55 ` Konrad Dybcio
2026-09-08 5:09 ` Jens Glathe
2026-09-05 9:29 ` [PATCH 7/7] arm64: dts: qcom: ideacentre-mini: Drop the unused USB MP port Jens Glathe via B4 Relay
2026-09-07 8:56 ` Konrad Dybcio
2026-09-07 8:57 ` [PATCH 0/7] arm64: dts: qcom: IdeaCentre Mini 01Q8X10 Hamoa + Purwa Konrad Dybcio
2026-09-07 9:51 ` Mostafa Saleh
2026-09-08 9:03 ` Mostafa Saleh
2026-09-08 9:05 ` Krzysztof Kozlowski
2026-09-08 9:11 ` Mostafa Saleh
2026-09-08 9:57 ` Konrad Dybcio
2026-09-08 11:02 ` Mostafa Saleh
2026-09-08 12:00 ` Krzysztof Kozlowski
2026-09-08 9:34 ` Jens Glathe
2026-09-08 9:39 ` Jens Glathe
2026-09-08 11:00 ` Mostafa Saleh
2026-09-08 12:00 ` Jens Glathe
2026-09-08 12:09 ` Mostafa Saleh
2026-09-08 15:04 ` Jens Glathe
2026-09-08 17:47 ` Mostafa Saleh [this message]
2026-09-08 18:15 ` Jens Glathe
2026-09-09 12:47 ` Mostafa Saleh
2026-09-09 11:31 ` Konrad Dybcio
2026-09-09 12:14 ` Mostafa Saleh
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=aqBKI0Fg3ZqYPOJh@google.com \
--to=smostafa@google.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jens.glathe@oldschoolsolutions.biz \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®