devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Steffen Trumtrar <s.trumtrar@pengutronix.de>
Cc: Conor Dooley <conor@kernel.org>,
	Andrew Lunn <andrew+netdev@lunn.ch>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>, Andrew Davis <afd@ti.com>,
	Heiner Kallweit <hkallweit1@gmail.com>,
	Russell King <linux@armlinux.org.uk>,
	netdev@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/3] dt-bindings: dp83867: add binding for output-impedance
Date: Thu, 27 Aug 2026 17:05:45 +0200	[thread overview]
Message-ID: <b10f5ca1-d0bb-4cf2-9cc3-9ed66ab427b0@lunn.ch> (raw)
In-Reply-To: <87a4q74ris.fsf@pengutronix.de>

> So, just allow values between 35 and 70 in the binding and then
> convert that value to something near the truth in the driver?

Yes. And you can add a comment that the values are not exact, due to
process issues.

	Andrew

  reply	other threads:[~2026-08-27 15:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-26 12:48 [PATCH v2 0/3] net: dp83867: add new output-impedance DT binding Steffen Trumtrar
2026-08-26 12:48 ` [PATCH v2 1/3] dt-bindings: net: dp83867: make exclusivity explicit Steffen Trumtrar
2026-08-27 12:49   ` sashiko-bot
2026-08-26 12:48 ` [PATCH v2 2/3] dt-bindings: dp83867: add binding for output-impedance Steffen Trumtrar
2026-08-26 16:01   ` Conor Dooley
2026-08-27  8:04     ` Steffen Trumtrar
2026-08-27 12:47       ` Andrew Lunn
2026-08-27 13:33         ` Steffen Trumtrar
2026-08-27 15:05           ` Andrew Lunn [this message]
2026-08-27 16:05       ` Conor Dooley
2026-08-27 12:49   ` sashiko-bot
2026-08-26 12:48 ` [PATCH v2 3/3] net: phy: dp83867: support setting output-impedance Steffen Trumtrar
2026-08-27 12:49   ` sashiko-bot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b10f5ca1-d0bb-4cf2-9cc3-9ed66ab427b0@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=afd@ti.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=conor+dt@kernel.org \
    --cc=conor@kernel.org \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=edumazet@google.com \
    --cc=hkallweit1@gmail.com \
    --cc=krzk+dt@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=robh@kernel.org \
    --cc=s.trumtrar@pengutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).