From: Ivan Mikhaylov <fr0st61te@gmail.com>
To: Samuel Mendoza-Jonas <sam@mendozajonas.com>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Cc: netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, openbmc@lists.ozlabs.org,
Ivan Mikhaylov <fr0st61te@gmail.com>,
Paul Fertser <fercerpav@gmail.com>
Subject: [PATCH v2 3/5] dt-bindings: net: add mac-address-increment option
Date: Tue, 9 May 2023 14:35:02 +0000 [thread overview]
Message-ID: <20230509143504.30382-4-fr0st61te@gmail.com> (raw)
In-Reply-To: <20230509143504.30382-1-fr0st61te@gmail.com>
Add the mac-address-increment option for specify MAC address taken by
any other sources.
Signed-off-by: Paul Fertser <fercerpav@gmail.com>
Signed-off-by: Ivan Mikhaylov <fr0st61te@gmail.com>
---
.../devicetree/bindings/net/ethernet-controller.yaml | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/Documentation/devicetree/bindings/net/ethernet-controller.yaml b/Documentation/devicetree/bindings/net/ethernet-controller.yaml
index 00be387984ac..6900098c5105 100644
--- a/Documentation/devicetree/bindings/net/ethernet-controller.yaml
+++ b/Documentation/devicetree/bindings/net/ethernet-controller.yaml
@@ -34,6 +34,14 @@ properties:
minItems: 6
maxItems: 6
+ mac-address-increment:
+ $ref: /schemas/types.yaml#/definitions/int32
+ description:
+ Specifies the MAC address increment to be added to the MAC address.
+ Should be used in cases when there is a need to use MAC address
+ different from one obtained by any other level, like u-boot or the
+ NC-SI stack.
+
max-frame-size:
$ref: /schemas/types.yaml#/definitions/uint32
description:
--
2.40.1
next prev parent reply other threads:[~2023-05-09 11:35 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-09 14:34 [PATCH v2 0/5] Refactoring for GMA command Ivan Mikhaylov
2023-05-09 14:35 ` [PATCH v2 1/5] net/ncsi: make one oem_gma function for all mfr id Ivan Mikhaylov
2023-05-09 14:29 ` Simon Horman
2023-05-09 14:35 ` [PATCH v2 2/5] net/ncsi: change from ndo_set_mac_address to dev_set_mac_address Ivan Mikhaylov
2023-05-09 14:35 ` Ivan Mikhaylov [this message]
2023-05-10 14:48 ` [PATCH v2 3/5] dt-bindings: net: add mac-address-increment option Krzysztof Kozlowski
2023-05-10 23:31 ` Ivan Mikhaylov
2023-05-12 6:22 ` Krzysztof Kozlowski
2023-05-12 11:28 ` Ivan Mikhaylov
2023-05-12 9:24 ` Krzysztof Kozlowski
2023-05-16 11:47 ` Ivan Mikhaylov
2023-05-17 8:36 ` Krzysztof Kozlowski
2023-05-17 21:38 ` Ivan Mikhaylov
2023-05-17 19:26 ` Krzysztof Kozlowski
2023-05-29 20:59 ` Paul Fertser
2023-06-04 10:23 ` Krzysztof Kozlowski
2023-05-09 14:35 ` [PATCH v2 4/5] net/ncsi: add shift MAC address property Ivan Mikhaylov
2023-05-09 14:34 ` Simon Horman
2023-05-09 14:35 ` [PATCH v2 5/5] dt-bindings: net: ftgmac100: convert to yaml version from txt Ivan Mikhaylov
2023-05-10 14:50 ` Krzysztof Kozlowski
2023-05-11 0:15 ` Ivan Mikhaylov
2023-05-11 8:39 ` Krzysztof Kozlowski
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=20230509143504.30382-4-fr0st61te@gmail.com \
--to=fr0st61te@gmail.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=fercerpav@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=openbmc@lists.ozlabs.org \
--cc=pabeni@redhat.com \
--cc=robh+dt@kernel.org \
--cc=sam@mendozajonas.com \
/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