From: Linus Walleij <linus.walleij@linaro.org>
To: 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 Lunn <andrew@lunn.ch>,
Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>,
Simon Horman <horms@kernel.org>
Cc: netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>
Subject: [PATCH 1/2] dt-bindings: net: ethernet-controller: Add mac offset option
Date: Fri, 20 Dec 2024 20:17:06 +0100 [thread overview]
Message-ID: <20241220-net-mac-nvmem-offset-v1-1-e9d1da2c1681@linaro.org> (raw)
In-Reply-To: <20241220-net-mac-nvmem-offset-v1-0-e9d1da2c1681@linaro.org>
In practice (as found in the OpenWrt project) many devices
with multiple ethernet interfaces just store a base MAC
address in NVMEM and increase the lowermost byte with one for
each interface, so as to occupy less NVMEM.
Support this with a per-interface offset so we can encode
this in a predictable way for each interface sharing the
same NVMEM cell.
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
---
.../devicetree/bindings/net/ethernet-controller.yaml | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/Documentation/devicetree/bindings/net/ethernet-controller.yaml b/Documentation/devicetree/bindings/net/ethernet-controller.yaml
index 45819b2358002bc75e876eddb4b2ca18017c04bd..608f89359ca844e5325e3cc81bd2677b0eccb08a 100644
--- a/Documentation/devicetree/bindings/net/ethernet-controller.yaml
+++ b/Documentation/devicetree/bindings/net/ethernet-controller.yaml
@@ -53,6 +53,18 @@ properties:
nvmem-cell-names:
const: mac-address
+ nvmem-mac-minor-offset:
+ $ref: /schemas/types.yaml#/definitions/uint32
+ minimum: 1
+ maximum: 255
+ description:
+ When a MAC address for a device with multiple ethernet interface
+ is stored in non-volatile memory, the address is often offsetted
+ for different interfaces by increasing the lowermost byte for each
+ interface subsequent to the first in order to save space in NVMEM.
+ This property can be used to add that offset when several
+ interfaces refer to the same NVMEM cell.
+
phy-connection-type:
description:
Specifies interface type between the Ethernet device and a physical
--
2.47.1
next prev parent reply other threads:[~2024-12-20 19:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-20 19:17 [PATCH 0/2] net: of: Support minor nvmem MAC offset Linus Walleij
2024-12-20 19:17 ` Linus Walleij [this message]
2024-12-31 13:35 ` [PATCH 1/2] dt-bindings: net: ethernet-controller: Add mac offset option Rob Herring
2025-01-13 14:59 ` Linus Walleij
2025-01-14 19:47 ` Rob Herring
2024-12-20 19:17 ` [PATCH 2/2] net: of: Support adding offset to nvmem MAC addresses Linus Walleij
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=20241220-net-mac-nvmem-offset-v1-1-e9d1da2c1681@linaro.org \
--to=linus.walleij@linaro.org \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=horms@kernel.org \
--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 \
/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).