[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <e43d9cf4-8e44-4918-a181-2a3daa9c9b3c@lunn.ch>
Date: Wed, 21 Jun 2023 16:13:07 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Guo Samin <samin.guo@...rfivetech.com>
Cc: Conor Dooley <conor@...nel.org>, linux-kernel@...r.kernel.org,
devicetree@...r.kernel.org, netdev@...r.kernel.org,
Peter Geis <pgwipeout@...il.com>,
Frank <Frank.Sae@...or-comm.com>,
"David S . Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Heiner Kallweit <hkallweit1@...il.com>,
Russell King <linux@...linux.org.uk>,
Yanhong Wang <yanhong.wang@...rfivetech.com>
Subject: Re: [PATCH v3 1/2] dt-bindings: net: motorcomm: Add pad driver
strength cfg
> When we need to deal with current values at different voltages,
> using register values in drives may be simpler, comparing the
> current value.
Register values in DT are only allowed in the worst case if its all
undocumented vendor magic. You have the needed documentation, and its
easy code to write, lookup a value in a table.
Andrew
Powered by blists - more mailing lists