lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <176861636288.2528721.260536635040675678.robh@kernel.org>
Date: Fri, 16 Jan 2026 20:20:52 -0600
From: Rob Herring <robh@...nel.org>
To: Barnabás Czémán <barnabas.czeman@...nlining.org>
Cc: phone-devel@...r.kernel.org, Tony Luck <tony.luck@...el.com>, 
 devicetree@...r.kernel.org, Kees Cook <kees@...nel.org>, 
 "Guilherme G. Piccoli" <gpiccoli@...lia.com>, 
 Bjorn Andersson <andersson@...nel.org>, 
 Gabriel Gonzales <semfault@...root.org>, Conor Dooley <conor+dt@...nel.org>, 
 linux@...nlining.org, Konrad Dybcio <konradybcio@...nel.org>, 
 Konrad Dybcio <konrad.dybcio@....qualcomm.com>, 
 Krzysztof Kozlowski <krzk+dt@...nel.org>, linux-hardening@...r.kernel.org, 
 Dmitry Baryshkov <dmitry.baryshkov@....qualcomm.com>, 
 linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org, 
 ~postmarketos/upstreaming@...ts.sr.ht, 
 Biswapriyo Nath <nathbappai@...il.com>
Subject: Re: [PATCH v2 0/7] Initial Redmi Note 8T support and more


On Fri, 16 Jan 2026 16:54:42 +0100, Barnabás Czémán wrote:
> Redmi Note 8 and 8T are sibling devices the only difference
> is Redmi Note 8T have NFC.
> This patch series is commonizing Redmi Note 8 devicetree
> for a base for both devices.
> 
> The patch series also contains some fixes for Redmi Note 8:
> - Fix reserved memory ranges, they were wrongly defined.
> - Remove board-id, board-id is not neccessary for the bootloader.
> - Fix reserved-gpio-ranges the reserved ranges was wrongly
> defined what caused the device crash on the boot.
> - Remove unnecessary usb-extcon, gpio102 is related to DisplayPort
> what is not supported by these devices.
> - Use memory-region property for framebuffer.
> 
> Depends on:
> [1] https://lore.kernel.org/all/20251229142806.241088-2-krzysztof.kozlowski@oss.qualcomm.com/
> 
> Signed-off-by: Barnabás Czémán <barnabas.czeman@...nlining.org>
> ---
> Changes in v2:
> - Fix copyright in sm6125-xiaomi-ginkgo.dts as requested.
> - Use memory-region property for the framebuffer.
> - Add comment about the NFC.
> - Remove msm-id change in favor of [1].
> - Link to v1: https://lore.kernel.org/r/20260112-xiaomi-willow-v1-0-8e4476897638@mainlining.org
> 
> ---
> Barnabás Czémán (7):
>       arm64: dts: qcom: sm6125-xiaomi-ginkgo: Remove board-id
>       arm64: dts: qcom: sm6125-xiaomi-ginkgo: Correct reserved memory ranges
>       arm64: dts: qcom: sm6125-xiaomi-ginkgo: Set memory-region for framebuffer
>       arm64: dts: qcom: sm6125-xiaomi-ginkgo: Remove extcon
>       arm64: dts: qcom: sm6125-xiaomi-ginkgo: Fix reserved gpio ranges
>       dt-bindings: arm: qcom: Add Xiaomi Redmi Note 8T
>       arm64: dts: qcom: Add Redmi Note 8T
> 
>  Documentation/devicetree/bindings/arm/qcom.yaml    |   1 +
>  arch/arm64/boot/dts/qcom/Makefile                  |   3 +-
>  .../boot/dts/qcom/sm6125-xiaomi-ginkgo-common.dtsi | 301 +++++++++++++++++++++
>  arch/arm64/boot/dts/qcom/sm6125-xiaomi-ginkgo.dts  | 285 +------------------
>  arch/arm64/boot/dts/qcom/sm6125-xiaomi-willow.dts  |  15 +
>  5 files changed, 320 insertions(+), 285 deletions(-)
> ---
> base-commit: f417b7ffcbef7d76b0d8860518f50dae0e7e5eda
> change-id: 20260111-xiaomi-willow-448552f02762
> prerequisite-message-id: <20251229142806.241088-2-krzysztof.kozlowski@....qualcomm.com>
> prerequisite-patch-id: 1bc49c0e2bec1a47667df776e1ab265b0699ea35
> 
> Best regards,
> --
> Barnabás Czémán <barnabas.czeman@...nlining.org>
> 
> 
> 


My bot found new DTB warnings on the .dts files added or changed in this
series.

Some warnings may be from an existing SoC .dtsi. Or perhaps the warnings
are fixed by another series. Ultimately, it is up to the platform
maintainer whether these warnings are acceptable or not. No need to reply
unless the platform maintainer has comments.

If you already ran DT checks and didn't see these error(s), then
make sure dt-schema is up to date:

  pip3 install dtschema --upgrade


This patch series was applied (using b4) to base:
 Deps: looking for dependencies matching 1 patch-ids
 Deps: Applying prerequisite patch: [PATCH RFT] arm64: dts: qcom: sm6125-ginkgo: Fix missing msm-id subtype
 Base: f417b7ffcbef7d76b0d8860518f50dae0e7e5eda (use --merge-base to override)

If this is not the correct base, please add 'base-commit' tag
(or use b4 which does this automatically)

Warnings in base: 266
Warnings after series: 272
New warnings running 'make CHECK_DTBS=y for arch/arm64/boot/dts/qcom/' for 20260116-xiaomi-willow-v2-0-4694feb70cdb@...nlining.org:

arch/arm64/boot/dts/qcom/sm6125-xiaomi-willow.dtb: geniqup@...0000 (qcom,geni-se-qup): #address-cells: 2 was expected
	from schema $id: http://devicetree.org/schemas/soc/qcom/qcom,geni-se.yaml
arch/arm64/boot/dts/qcom/sm6125-xiaomi-willow.dtb: geniqup@...0000 (qcom,geni-se-qup): #size-cells: 2 was expected
	from schema $id: http://devicetree.org/schemas/soc/qcom/qcom,geni-se.yaml
arch/arm64/boot/dts/qcom/sm6125-xiaomi-willow.dtb: geniqup@...0000 (qcom,geni-se-qup): #address-cells: 2 was expected
	from schema $id: http://devicetree.org/schemas/soc/qcom/qcom,geni-se.yaml
arch/arm64/boot/dts/qcom/sm6125-xiaomi-willow.dtb: geniqup@...0000 (qcom,geni-se-qup): #size-cells: 2 was expected
	from schema $id: http://devicetree.org/schemas/soc/qcom/qcom,geni-se.yaml






Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ