[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <d4628648-8f21-4b57-8ca9-f08d89f5e399@lunn.ch>
Date: Thu, 9 Oct 2025 15:04:27 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Alexey Charkov <alchark@...il.com>
Cc: jjm2473 <jjm2473@...il.com>, robh@...nel.org, krzk+dt@...nel.org,
conor+dt@...nel.org, heiko@...ech.de, quentin.schulz@...rry.de,
kever.yang@...k-chips.com, naoki@...xa.com, honyuenkwun@...il.com,
inindev@...il.com, ivan8215145640@...il.com,
neil.armstrong@...aro.org, mani@...nel.org, dsimic@...jaro.org,
pbrobinson@...il.com, didi.debian@...ow.org, jbx6244@...il.com,
devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-rockchip@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 3/3] arm64: dts: rockchip: add LinkEase EasePi R1
> FWIW, the TRM for Rockchip RK3576 specifies that the values in
> tx|rx-delay control the number of delay elements in the internal
> delayline on the transmit and receive clocks, respectively (up to 200
> each).
200 is interesting:
tx_delay:
description: Delay value for TXD timing.
$ref: /schemas/types.yaml#/definitions/uint32
minimum: 0
maximum: 0x7F
200 != 0x7f
But i don't think the driver does any validation, so its not too
important.
Andrew
Powered by blists - more mailing lists