Devicetree
 help / color / mirror / Atom feed
From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Mostafa Saleh <smostafa@google.com>
Cc: andersson@kernel.org, konradybcio@kernel.org, robh@kernel.org,
	krzk+dt@kernel.org, conor+dt@kernel.org,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, maz@kernel.org
Subject: Re: Support for Lenovo IdeaCentre Mini X (Purwa)
Date: Fri, 15 May 2026 13:28:00 +0200	[thread overview]
Message-ID: <abe8443b-9871-455c-95d9-d16975c0fbdf@oss.qualcomm.com> (raw)
In-Reply-To: <afOP2xXmEpV1eI3Z@google.com>

On 4/30/26 7:22 PM, Mostafa Saleh wrote:
> 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.

[...]

> 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.

Hm, I ran a quick diff and even though there's a lot of noise (mostly
due to the same things being named slightly differently), the actual
meat and potatoes aren't very different at all, e.g. the PHY regulators
are the same

Could you post the full dmesg with both DTs?

Konrad

      reply	other threads:[~2026-05-15 11:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-29 14:18 Support for Lenovo IdeaCentre Mini X (Purwa) Mostafa Saleh
2026-04-30 16:48 ` Konrad Dybcio
2026-04-30 17:22   ` Mostafa Saleh
2026-05-15 11:28     ` Konrad Dybcio [this message]

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=abe8443b-9871-455c-95d9-d16975c0fbdf@oss.qualcomm.com \
    --to=konrad.dybcio@oss.qualcomm.com \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.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=maz@kernel.org \
    --cc=robh@kernel.org \
    --cc=smostafa@google.com \
    /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