On 2026-01-13 10:12, Konrad Dybcio wrote:
On 1/13/26 10:08 AM, [email protected] wrote:
On 2026-01-13 10:01, Konrad Dybcio wrote:
On 1/12/26 9:13 PM, Barnabás Czémán wrote:
The device was crashing on boot because the reserved gpio ranges
was wrongly defined. Correct the ranges for avoid pinctrl crashing.
Fixes: 9b1a6c925c88 ("arm64: dts: qcom: sm6125: Initial support for
xiaomi-ginkgo")
Signed-off-by: Barnabás Czémán <[email protected]>
---
That's odd.. were you able to confirm that these values are alright
for
both the Note 8 and the 8T?
Yes, it was tested on both devices. The original devicetree was never
boot.
Fun..
arch/arm64/boot/dts/qcom/sm6125-xiaomi-ginkgo.dts | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm64/boot/dts/qcom/sm6125-xiaomi-ginkgo.dts
b/arch/arm64/boot/dts/qcom/sm6125-xiaomi-ginkgo.dts
index 666daf4a9fdd..163ecdc7fd6c 100644
--- a/arch/arm64/boot/dts/qcom/sm6125-xiaomi-ginkgo.dts
+++ b/arch/arm64/boot/dts/qcom/sm6125-xiaomi-ginkgo.dts
@@ -296,7 +296,7 @@ &sdhc_2 {
};
&tlmm {
- gpio-reserved-ranges = <22 2>, <28 6>;
+ gpio-reserved-ranges = <0 4>, <30 4>;
Any chance you know/could deduce what they're connected to and
describe
it, like in x1-crd.dtsi?
https://github.com/MiCode/Xiaomi_Kernel_OpenSource/blob/willow-p-oss/drivers/pinctrl/qcom/pinctrl-msm.c#L605
https://github.com/MiCode/Xiaomi_Kernel_OpenSource/blob/ginkgo-p-oss/drivers/pinctrl/qcom/pinctrl-msm.c#L610
GPIO0-3 sounds like QUP0 and GPIO30-33 sounds like QUP6
My guess would be one goes to a fingerprint scanner and one goes to
NFC eSE (or N/C for the device without NFC)
Could you scan the downstream devicetree for signals of that?
NFC is using gpio83, gpio84, gpio85 and gpio95.
Konrad
