linux-kernel - Re: [PATCH 3/4] arm64: dts: rockchip: Add HINLINK H68K

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: <ff06c2eb-5124-45bf-b4dc-a43f7558563d@lunn.ch>
Date: Mon, 1 Sep 2025 02:47:21 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Erik Beck <xunil@...omasoft.com>
Cc: Chukun Pan <amadeus@....edu.cn>, Heiko Stuebner <heiko@...ech.de>,
	Rob Herring <robh@...nel.org>, Conor Dooley <conor+dt@...nel.org>,
	Krzysztof Kozlowski <krzk+dt@...nel.org>,
	linux-arm-kernel@...ts.infradead.org,
	linux-rockchip@...ts.infradead.org, linux-kernel@...r.kernel.org,
	devicetree@...r.kernel.org
Subject: Re: [PATCH 3/4] arm64: dts: rockchip: Add HINLINK H68K

> Just so I am clear, the units are tenths of nanoseconds? So <0x02> is .2
> nanoseconds?
 
Quoting myself: 
 
> > One problem we have with rx_delay and tx_delay is that they are
> > magic. we have no idea what they mean.

I very much doubt 0x02 is 0.2 nano seconds. If you have an
oscilloscope which can handle the signals, you could measure it and
see how the delay changes with different values. But developers have
done that in the past, with mixed results.

	Andrew