From: Rob Herring <robh@kernel.org>
To: Daniel Golle <daniel@makrotopia.org>
Cc: Felix Fietkau <nbd@nbd.name>,
Lorenzo Bianconi <lorenzo@kernel.org>,
Ryder Lee <ryder.lee@mediatek.com>,
Shayne Chen <shayne.chen@mediatek.com>,
Sean Wang <sean.wang@mediatek.com>, Kalle Valo <kvalo@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH net-next v3 1/2] dt-bindings: mt76: support setting per-band MAC address
Date: Fri, 11 Aug 2023 13:09:44 -0600 [thread overview]
Message-ID: <20230811190944.GA3730441-robh@kernel.org> (raw)
In-Reply-To: <d3130584b64309da28a04826100643ff6239f9ca.1690841657.git.daniel@makrotopia.org>
On Mon, Jul 31, 2023 at 11:23:16PM +0100, Daniel Golle wrote:
> Introduce support for setting individual per-band MAC addresses using
> NVMEM cells by adding a 'bands' object with enumerated child nodes
> representing the 2.4 GHz, 5 GHz and 6 GHz bands.
>
> In case it is defined, call of_get_mac_address for the per-band child
> node, otherwise try with of_get_mac_address on the main device node and
> fall back to a random address like it used to be.
>
> While at it, add MAC address related properties also for the main node.
>
> Signed-off-by: Daniel Golle <daniel@makrotopia.org>
> ---
> Changes since v2:
> * drop items list with only a single item
>
> Changes since v1:
> * add dt-bindings
>
> .../bindings/net/wireless/mediatek,mt76.yaml | 58 ++++++++++++++++++-
> 1 file changed, 57 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/net/wireless/mediatek,mt76.yaml b/Documentation/devicetree/bindings/net/wireless/mediatek,mt76.yaml
> index 252207adbc54c..7eafed53da1de 100644
> --- a/Documentation/devicetree/bindings/net/wireless/mediatek,mt76.yaml
> +++ b/Documentation/devicetree/bindings/net/wireless/mediatek,mt76.yaml
> @@ -37,6 +37,12 @@ properties:
> description:
> MT7986 should contain 3 regions consys, dcm, and sku, in this order.
>
> + '#address-cells':
> + const: 1
> +
> + '#size-cells':
> + const: 0
> +
> interrupts:
> maxItems: 1
>
> @@ -72,13 +78,23 @@ properties:
>
> ieee80211-freq-limit: true
>
> + address: true
What's this? Not a documented property.
> +
> + local-mac-address: true
> +
> + mac-address: true
You really need a ref to the schema defining these. But first we need to
split them out from ethernet-controller.yaml. Which I think there were
patches for, but it stalled out.
Anyways, it's fine for now if you're not up for that.
> +
> nvmem-cells:
> + minItems: 1
> items:
> - description: NVMEM cell with EEPROM
> + - description: NVMEM cell with the MAC address
>
> nvmem-cell-names:
> + minItems: 1
> items:
> - const: eeprom
> + - const: mac-address
>
> mediatek,eeprom-data:
> $ref: /schemas/types.yaml#/definitions/uint32-array
> @@ -213,6 +229,29 @@ properties:
> description:
> Half-dBm power delta for different numbers of antennas
>
> +patternProperties:
> + '^band@[0-2]+$':
> + type: object
> + additionalProperties: false
> + properties:
> + reg:
> + maxItems: 1
> +
> + address: true
> + local-mac-address: true
> + mac-address: true
> +
> + nvmem-cells:
> + description: NVMEM cell with the MAC address
> +
> + nvmem-cell-names:
> + const: mac-address
> +
> + required:
> + - reg
> +
> + unevaluatedProperties: false
> +
> required:
> - compatible
> - reg
> @@ -225,10 +264,13 @@ examples:
> #address-cells = <3>;
> #size-cells = <2>;
> wifi@0,0 {
> + #address-cells = <1>;
> + #size-cells = <0>;
> compatible = "mediatek,mt76";
> reg = <0x0000 0 0 0 0>;
> ieee80211-freq-limit = <5000000 6000000>;
> - mediatek,mtd-eeprom = <&factory 0x8000>;
> + nvmem-cells = <&factory_eeprom>;
> + nvmem-cell-names = "eeprom";
> big-endian;
>
> led {
> @@ -257,6 +299,20 @@ examples:
> };
> };
> };
> +
> + band@0 {
> + /* 2.4 GHz */
> + reg = <0>;
> + nvmem-cells = <&macaddr 0x4>;
> + nvmem-cell-names = "mac-address";
> + };
> +
> + band@1 {
> + /* 5 GHz */
> + reg = <1>;
> + nvmem-cells = <&macaddr 0xa>;
> + nvmem-cell-names = "mac-address";
> + };
> };
> };
>
> --
> 2.41.0
next prev parent reply other threads:[~2023-08-11 19:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-31 22:23 [PATCH net-next v3 1/2] dt-bindings: mt76: support setting per-band MAC address Daniel Golle
2023-07-31 22:24 ` [PATCH v3 2/2] wifi: mt76: support per-band MAC addresses from OF child nodes Daniel Golle
2023-08-01 8:04 ` [PATCH net-next v3 1/2] dt-bindings: mt76: support setting per-band MAC address Kalle Valo
2023-08-11 19:09 ` Rob Herring [this message]
2023-08-22 11:35 ` Daniel Golle
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=20230811190944.GA3730441-robh@kernel.org \
--to=robh@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=conor+dt@kernel.org \
--cc=daniel@makrotopia.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lorenzo@kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=nbd@nbd.name \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=ryder.lee@mediatek.com \
--cc=sean.wang@mediatek.com \
--cc=shayne.chen@mediatek.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;
as well as URLs for NNTP newsgroup(s).