Re: Support for Lenovo IdeaCentre Mini X (Purwa)

[Mostafa Saleh <smostafa@google.com>]

Hi Konrad,

On Thu, Apr 30, 2026 at 06:48:33PM +0200, Konrad Dybcio wrote:
> On 4/29/26 4:18 PM, Mostafa Saleh wrote:
> > Hi,
> > 
> > I see that recently the support for “Lenovo IdeaCentre Mini X” was
> > added [1]
> > However, unfortunately that doesn’t work for my device, the board
> > resets once I try to boot the kernel from UEFI.
> > 
> > I believe that’s because it is another variant, as I have been using
> > my device tree for some time[2] which is hacked based on the crd
> > device tree with some trial and error. With that I can boot with
> > PCI/NVME/Ethernet and USB (there are also some other errors in the
> > log related PMIC), this device tree is based on purwa.dtsi unlike
> > the upstream one which use hamoa.dtsi.
> > 
> > Are there any plans to support the Purwa based variant? I am happy to
> > help with testing, but I can’t confidently send patches as my device
> > tree is based on trial and error rather than a data sheet.
> 
> Hello,
> 
> could you try
> 
> diff --git a/arch/arm64/boot/dts/qcom/hamoa-lenovo-ideacentre-mini-01q8x10.dts b/arch/arm64/boot/dts/qcom/hamoa-lenovo-ideacentre-mini-01q8x10.dts
> index bfb7cea56df9..845f303c3836 100644
> --- a/arch/arm64/boot/dts/qcom/hamoa-lenovo-ideacentre-mini-01q8x10.dts
> +++ b/arch/arm64/boot/dts/qcom/hamoa-lenovo-ideacentre-mini-01q8x10.dts
> @@ -8,7 +8,7 @@
>  #include <dt-bindings/gpio/gpio.h>
>  #include <dt-bindings/regulator/qcom,rpmh-regulator.h>
>  
> -#include "hamoa.dtsi"
> +#include "purwa.dtsi"
>  #include "hamoa-pmics.dtsi"
>  
>  / {
> 
> 
> for starters?

Thanks for the suggestion, I tired that now and it doesn't boot, because
PCI and USB timeout, most likely power issue:
[    0.449155] qcom-qmp-usb-phy 88e3000.phy: phy initialization timed-out
[    0.455886] phy phy-88e3000.phy.6: phy init failed --> -110
[    0.458571] qcom-qmp-pcie-phy 1bfc000.phy: phy initialization timed-out
[    0.461710] dwc3-qcom a400000.usb: error -ETIMEDOUT: failed to initialize core
[    0.468478] phy phy-1bfc000.phy.12: phy poweron failed --> -110
[    0.475826] dwc3-qcom a400000.usb: error -ETIMEDOUT: failed to register DWC3 Core
[    0.481982] qcom-pcie 1bf8000.pci: error -ETIMEDOUT: cannot initialize host
[    0.489748] dwc3-qcom a400000.usb: probe with driver dwc3-qcom failed with error -110
[    0.496742] qcom-pcie 1bf8000.pci: probe with driver qcom-pcie failed with error -110
[    0.536145] qcom_pmic_glink pmic-glink: Failed to create device link (0x180) with supplier a600000.usb for /pmic-glink/connector@0
[    1.610679] qcom-pcie 1c08000.pci: Link failed to come up. LTSSM: PRE_DETECT_QUIET
[    1.620224] qcom-pcie 1c08000.pci: error -ETIMEDOUT: cannot initialize host
[    1.627406] qcom-pcie 1c08000.pci: probe with driver qcom-pcie failed with error -110

However, with my device tree I see:
# dmesg | grep -i -e qcom-pcie
[    0.380703] qcom-pcie 1c00000.pci: host bridge /soc@0/pci@1c00000 ranges:
[    0.388163] qcom-pcie 1c08000.pci: supply vddpe-3v3 not found, using dummy regulator
[    0.399742] qcom-pcie 1c00000.pci:       IO 0x007e200000..0x007e2fffff -> 0x0000000000
[    0.407745] qcom-pcie 1c08000.pci: host bridge /soc@0/pci@1c08000 ranges:
[    0.419165] qcom-pcie 1bf8000.pci: supply vdda not found, using dummy regulator
[    0.419290] qcom-pcie 1c00000.pci:      MEM 0x007e300000..0x007fffffff -> 0x007e300000
[    0.419320] qcom-pcie 1bf8000.pci: host bridge /soc@0/pci@1bf8000 ranges:
[    0.419344] qcom-pcie 1bf8000.pci:       IO 0x0070200000..0x00702fffff -> 0x0000000000
[    0.419358] qcom-pcie 1bf8000.pci:      MEM 0x0070300000..0x0073ffffff -> 0x0070300000
[    0.426796] qcom-pcie 1c08000.pci:       IO 0x007c200000..0x007c2fffff -> 0x0000000000
[    0.426801] qcom-pcie 1c08000.pci:      MEM 0x007c300000..0x007dffffff -> 0x007c300000
[    0.530174] qcom-pcie 1bf8000.pci: iATU: unroll T, 8 ob, 8 ib, align 4K, limit 1024G
[    0.538333] qcom-pcie 1c00000.pci: iATU: unroll T, 8 ob, 8 ib, align 4K, limit 1024G
[    0.550954] qcom-pcie 1c08000.pci: iATU: unroll T, 8 ob, 8 ib, align 4K, limit 1024G
[    0.730680] qcom-pcie 1bf8000.pci: PCIe Gen.4 x4 link up
[    0.730996] qcom-pcie 1bf8000.pci: PCI host bridge to bus 0006:00
[    0.736837] qcom-pcie 1c00000.pci: PCIe Gen.1 x1 link up
[    0.745431] qcom-pcie 1c00000.pci: PCI host bridge to bus 0005:00
[    0.748835] qcom-pcie 1c08000.pci: PCIe Gen.3 x2 link up
[    1.075106] qcom-pcie 1c08000.pci: PCI host bridge to bus 0004:00

And
# dmesg | grep -i -e usb
[    0.268120] platform a400000.usb: Adding to iommu group 6
[    0.268154] platform a600000.usb: Adding to iommu group 7
[    0.501050] xhci-hcd xhci-hcd.1.auto: new USB bus registered, assigned bus number 1
[    0.503561] xhci-hcd xhci-hcd.1.auto: new USB bus registered, assigned bus number 2
[    0.503565] xhci-hcd xhci-hcd.1.auto: Host supports USB 3.1 Enhanced SuperSpeed
[    0.503920] hub 1-0:1.0: USB hub found
[    0.504275] hub 2-0:1.0: USB hub found
[    0.504461] qcom_pmic_glink pmic-glink: Failed to create device link (0x180) with supplier a600000.usb for /pmic-glink/connector@0
[    0.528540] xhci-hcd xhci-hcd.2.auto: new USB bus registered, assigned bus number 3
[    0.531145] xhci-hcd xhci-hcd.2.auto: new USB bus registered, assigned bus number 4
[    0.531150] xhci-hcd xhci-hcd.2.auto: Host supports USB 3.1 Enhanced SuperSpeed
[    0.531529] hub 3-0:1.0: USB hub found
[    0.532008] hub 4-0:1.0: USB hub found
[    0.776839] usb 3-1: new high-speed USB device number 2 using xhci-hcd
[    1.091522] hub 3-1:1.0: USB hub found
[    1.206774] usb 4-1: new SuperSpeed Plus Gen 2x1 USB device number 2 using xhci-hcd
[    1.300590] hub 4-1:1.0: USB hub found
[    1.642832] usb 4-1.2: new SuperSpeed USB device number 3 using xhci-hcd
[    1.662337] usb-storage 4-1.2:1.0: USB Mass Storage device detected

I can try to see the differences and build another dt on top of the
hamoa one, but that will also be based on trial and error rather than
actual knowledge, I am happy to test patches if you have other
suggestions.

Thanks,
Mostafa

> 
> Konrad