From: Horatiu Vultur <horatiu.vultur@microchip.com>
To: <netdev@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Cc: <andrew@lunn.ch>, <hkallweit1@gmail.com>, <linux@armlinux.org.uk>,
<davem@davemloft.net>, <edumazet@google.com>, <kuba@kernel.org>,
<pabeni@redhat.com>, <robh+dt@kernel.org>,
<krzysztof.kozlowski+dt@linaro.org>, <michael@walle.cc>,
Horatiu Vultur <horatiu.vultur@microchip.com>
Subject: [PATCH net-next v3 2/2] dt-bindings: net: micrel-ksz90x1.txt: Update for lan8841
Date: Mon, 6 Feb 2023 09:23:02 +0100 [thread overview]
Message-ID: <20230206082302.958826-3-horatiu.vultur@microchip.com> (raw)
In-Reply-To: <20230206082302.958826-1-horatiu.vultur@microchip.com>
The lan8841 has the same bindings as ksz9131, so just reuse the entire
section of ksz9131.
Signed-off-by: Horatiu Vultur <horatiu.vultur@microchip.com>
---
Documentation/devicetree/bindings/net/micrel-ksz90x1.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/net/micrel-ksz90x1.txt b/Documentation/devicetree/bindings/net/micrel-ksz90x1.txt
index df9e844dd6bc6..2681168777a1e 100644
--- a/Documentation/devicetree/bindings/net/micrel-ksz90x1.txt
+++ b/Documentation/devicetree/bindings/net/micrel-ksz90x1.txt
@@ -158,6 +158,7 @@ KSZ9031:
no link will be established.
KSZ9131:
+LAN8841:
All skew control options are specified in picoseconds. The increment
step is 100ps. Unlike KSZ9031, the values represent picoseccond delays.
--
2.38.0
next prev parent reply other threads:[~2023-02-06 8:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-06 8:23 [PATCH net-next v3 0/2] net: micrel: Add support for lan8841 PHY Horatiu Vultur
2023-02-06 8:23 ` [PATCH net-next v3 1/2] " Horatiu Vultur
2023-02-06 13:30 ` Andrew Lunn
2023-02-06 8:23 ` Horatiu Vultur [this message]
2023-02-06 8:24 ` [PATCH net-next v3 2/2] dt-bindings: net: micrel-ksz90x1.txt: Update for lan8841 Krzysztof Kozlowski
2023-02-06 13:31 ` Andrew Lunn
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=20230206082302.958826-3-horatiu.vultur@microchip.com \
--to=horatiu.vultur@microchip.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=michael@walle.cc \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh+dt@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.