linux-kernel - Re: [PATCH 2/2] arm64: dts: meson: add initial device-tree for Tanix TX9 Pro

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAFBinCBeN-wjn-LBpgX9N_evzF1gL0nU8DPk5GSC28_s+tX+AA@mail.gmail.com>
Date: Sat, 4 Oct 2025 22:00:02 +0200
From: Martin Blumenstingl <martin.blumenstingl@...glemail.com>
To: Christian Hewitt <christianshewitt@...il.com>
Cc: Neil Armstrong <neil.armstrong@...aro.org>, Kevin Hilman <khilman@...libre.com>, 
	Jerome Brunet <jbrunet@...libre.com>, Rob Herring <robh@...nel.org>, 
	Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley <conor+dt@...nel.org>, devicetree@...r.kernel.org, 
	linux-arm-kernel@...ts.infradead.org, linux-amlogic@...ts.infradead.org, 
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/2] arm64: dts: meson: add initial device-tree for Tanix
 TX9 Pro

On Sat, Sep 27, 2025 at 2:50 PM Christian Hewitt
<christianshewitt@...il.com> wrote:
>
> Oranth Tanix TX9 Pro is based on the Amlogic Q200 reference design with
> an S912 chip and the following specs:
>
> - 3GB DDR3 RAM
> - 32GB eMMC
> - 10/100/1000 Base-T Ethernet
> - AP6356 Wireless (802.11 b/g/n/ac, BT 5.0)
> - HDMI 2.0a video
> - VFD for clock/status
> - 2x USB 2.0 ports
> - IR receiver
> - 1x Power LED (white)
> - 1x Update/Reset button (underside)
> - 1x micro SD card slot
>
> Signed-off-by: Christian Hewitt <christianshewitt@...il.com>
Reviewed-by: Martin Blumenstingl <martin.blumenstingl@...glemail.com>

> ---
> Checkpatch generates the 'phy-mode "rgmii" without comment'
> warning but this dts is using the same rgmii format as all
> other Amlogic boards, so I have omitted a comment.
So far we've been mimicking the vendor kernel (which sets up the MAC
to generate the delays and disables them on PHY level).
If we change it we should do so for all devices.


Best regards,
Martin