From: David Heidelberg <david@ixit.cz>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
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>, Kees Cook <kees@kernel.org>,
Tony Luck <tony.luck@intel.com>,
"Guilherme G. Piccoli" <gpiccoli@igalia.com>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, phone-devel@vger.kernel.org
Subject: Re: [PATCH 2/2] arm64: dts: qcom: add Xiaomi Mi 8 (dipper)
Date: Tue, 18 Aug 2026 11:38:23 +0200 [thread overview]
Message-ID: <b8cb7327-1e1b-4a44-ac97-dec9b6c32e9e@ixit.cz> (raw)
In-Reply-To: <8f05bf47-183f-4586-8ed2-eb2277f15c98@oss.qualcomm.com>
On 18/08/2026 11:27, Konrad Dybcio wrote:
> On 8/9/26 6:48 PM, David Heidelberg via B4 Relay wrote:
>> From: David Heidelberg <david@ixit.cz>
>>
>> Initial submission for one member of the prime Xiaomi Mi 8 family.
>> Mi 8 Pro (equuleus) and Mi 8 Explorer (ursa) are nearly identical.
>> Known differences are battery capacity and fingerprint sensor placement.
>> This submission includes basic abstraction for other developers to be
>> able easily extend it to support other variants.
>
> I had one of those. IIRC the Pro had a 3d IR scanner (vide face id)
> whereas the base one had a normal IR cam
>
> [...]
>
>> + reserved-memory {
>> + adsp_mem: memory@8c500000 {
>
> adsp@ etc. and drop labels where unused
>
> [...]
>
>> + linux,cma {
>> + compatible = "shared-dma-pool";
>> + alloc-ranges = <0 0x00000000 0 0xffffffff>;
>> + reusable;
>> + alignment = <0 0x400000>;
>> + size = <0 0x2c00000>;
>> + linux,cma-default;
>> + };
>
> Is this necessary?
>
>> + };
>> +
>> + vph_pwr: regulator-vph-pwr {
>
> This is out of order
>
> [...]
>
>
>> +&adsp_pas {
>> + firmware-name = "qcom/sdm845/Xiaomi/dipper/adsp.mbn";
>
> Would you know whether the FWs are common across the SKUs?
I don't, I have only one device (the dipper) available.
I'll see if I quickly figure out, if not, as no-one else having Mi8 family
volunteer to test, I would move it to dipper specific for now and can be moved
to common later.
>
> And more importantly, regulator settings? FWIW it's easiest to compare
> compiled DTBs (or even better, ones pulled from sysfs on a running
> system)
>
> [...]
>
>> +&tlmm {
>> + gpio-reserved-ranges = < 0 4>, /* SPI (Goodix Fingerprint) */
>
> odd space after <
I call it alignment, but sure :)>
>> + <81 4>; /* SPI (Synaptics Fingerprint) */
>
> No NFC eSE reservation?
It seems that vendor used different combinations of Goodix / Synaptics across
these ranges. Not even depending on the model. Same model can have different
wiring, but always honoring position 0:4, 81:4 as far goes my understanding. >
> [...]
>
>> +&usb_1_dwc3 {
>> + /* Until we have Type C hooked up we'll force this as peripheral. */
>
> Should be fairly trivial on 845, no?
>
>> + dr_mode = "peripheral";
>> +
>> + maximum-speed = "high-speed";
>> + phys = <&usb_1_hsphy>;
>> + phy-names = "usb2-phy";
>
> No SS?
Haven't thought about it, for now my goal is upstream basic telnet/ssh + FB.
Then display and touch - e.g. minimal u-boot and kernel development features and
then bring the rest.
>
> [...]
>
>> + bluetooth {
>> + compatible = "qcom,wcn3990-bt";
>> +
>> + /*
>> + * This path is relative to the qca/
>> + * subdir under lib/firmware.
>> + */
>
> Let's drop this comment, not very useful
Sure.
Then I'll also drop these from whole sdm845 in follow-up commit.
I'll address also the rest of the comments in the next version :)
Thanks for the review
David>
> Konrad
next prev parent reply other threads:[~2026-08-18 9:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-09 16:48 [PATCH 0/2] Introduce support for Xiaomi Mi 8 David Heidelberg via B4 Relay
2026-08-09 16:48 ` [PATCH 1/2] dt-bindings: arm: qcom: Add Xiaomi Mi 8 family compatibles David Heidelberg via B4 Relay
2026-08-09 16:48 ` [PATCH 2/2] arm64: dts: qcom: add Xiaomi Mi 8 (dipper) David Heidelberg via B4 Relay
2026-08-18 9:27 ` Konrad Dybcio
2026-08-18 9:38 ` David Heidelberg [this message]
2026-08-18 9:47 ` Konrad Dybcio
2026-09-15 13:48 ` David Heidelberg
2026-09-15 14:14 ` David Heidelberg
2026-08-18 9:27 ` Konrad Dybcio
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=b8cb7327-1e1b-4a44-ac97-dec9b6c32e9e@ixit.cz \
--to=david@ixit.cz \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gpiccoli@igalia.com \
--cc=kees@kernel.org \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phone-devel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=tony.luck@intel.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
all inboxes | Powered by JetHome®