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: <0ef03e2e1eb383eb0501d000704333f850652a4d.camel@gmail.com>
Date: Wed, 07 Jan 2026 10:25:43 +0000
From: Nuno Sá <noname.nuno@...il.com>
To: Krzysztof Kozlowski <krzk@...nel.org>, Osose Itua
	 <osose.itua@...oirfairelinux.com>
Cc: netdev@...r.kernel.org, devicetree@...r.kernel.org, 
	linux-kernel@...r.kernel.org, michael.hennerich@...log.com, 
	jerome.oufella@...oirfairelinux.com
Subject: Re: [PATCH v2 2/2] dt-bindings: net: adi,adin: document LP
 Termination property

On Sat, 2025-12-27 at 13:29 +0100, Krzysztof Kozlowski wrote:
> On Mon, Dec 22, 2025 at 05:21:05PM -0500, Osose Itua wrote:
> > Add "adi,low-cmode-impedance" boolean property which, when present,
> > configures the PHY for the lowest common-mode impedance on the receive
> > pair for 100BASE-TX operation.
> > 
> > Signed-off-by: Osose Itua <osose.itua@...oirfairelinux.com>
> > ---
> >  Documentation/devicetree/bindings/net/adi,adin.yaml | 6 ++++++
> >  1 file changed, 6 insertions(+)
> > 
> > diff --git a/Documentation/devicetree/bindings/net/adi,adin.yaml
> > b/Documentation/devicetree/bindings/net/adi,adin.yaml
> > index c425a9f1886d..d3c8c5cc4bb1 100644
> > --- a/Documentation/devicetree/bindings/net/adi,adin.yaml
> > +++ b/Documentation/devicetree/bindings/net/adi,adin.yaml
> > @@ -52,6 +52,12 @@ properties:
> >      description: Enable 25MHz reference clock output on CLK25_REF pin.
> >      type: boolean
> >  
> > +  adi,low-cmode-impedance:
> > +    description: |
> > +      Ability to configure for the lowest common-mode impedance on the
> 
> Either this is ability or you configure the PHY, as written in commit
> msg. The latter suggests that's a SW property, not hardware, thus not
> for bindings.
> 

Looking at the datasheet this looks like a system level decision. With the above
it seems we'll actually use more power and it is suited for designs where there is
common-mode noise reaching the phy. So it feels like something we would put in DT... 

But I agree the commit message (and maybe the property description) should
be better in reflecting why this is used rather than just saying what are we enabling.

- Nuno Sá

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ