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: <eb9c1489-4496-48b3-8709-739cd45c11b0@oss.qualcomm.com>
Date: Wed, 4 Feb 2026 10:20:54 +0100
From: Konrad Dybcio <konrad.dybcio@....qualcomm.com>
To: Roger Shimizu <rosh@...ian.org>, Bjorn Andersson <andersson@...nel.org>,
        Konrad Dybcio <konradybcio@...nel.org>, Rob Herring <robh@...nel.org>,
        Krzysztof Kozlowski <krzk+dt@...nel.org>,
        Conor Dooley <conor+dt@...nel.org>
Cc: linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] arm64: dts: qcom: qcs6490: Add Thundercomm AI Mini PC G1
 IoT

On 1/31/26 11:31 AM, Roger Shimizu wrote:
> Thundercomm AI MiniPC G1 IoT is single board computer with
> AI capability based on Qualcomm QCS6490 platform.
> 
> This device tree is confirmed to work as below:
> - GPU
> - HDMI output port
> - PCIe M.2 port (for external Wi-Fi or 5G connectivity)
> - UART / serial console port
> - UFS
> - USB Type-C port, with Display Port
> 
> Signed-off-by: Roger Shimizu <rosh@...ian.org>
> ---

[...]

> +/ {
> +	model = "Thundercomm AI Mini PC G1 IoT";
> +	compatible = "qcom,sc7280", "qcom,qcm6490";

You need to add a board-specific compatible here, see:

Documentation/devicetree/bindings/arm/qcom.yaml

> +	chassis-type = "embedded";

The allowed values are:

    enum:
      - desktop
      - laptop
      - convertible
      - server
      - all-in-one
      - tablet
      - handset
      - watch
      - embedded
      - television
      - spectacles

I think it's more of a desktop, but a) that's minor and b) you could
argue either way

[...]

> +		vreg_s1b_1p872: smps1 {
> +			regulator-name = "vreg_s1b_1p872";
> +			regulator-min-microvolt = <1840000>;
> +			regulator-max-microvolt = <2040000>;

Have you cross-checked the regulator settings against the original
vendor-provided sw?

[...]

> +&gpu_zap_shader {
> +	firmware-name = "qcom/qcs6490/a660_zap.mbn";

I'm assuming this means the thing can take Qualcomm- (vs OEM-)signed firmware
Could you please confirm that's the case?

[...]

> +&pon_pwrkey {
> +	status = "okay";
> +};

This one is already enabled

Konrad

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ