Linux wireless drivers development
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: David Heidelberg <david@ixit.cz>
Cc: "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>,
	"Mailing List"
	<devicetree-spec-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"Johannes Berg" <johannes@sipsolutions.net>,
	"Lorenzo Bianconi" <lorenzo@kernel.org>,
	"van Spriel" <arend@broadcom.com>,
	"Jérôme Pouiller" <jerome.pouiller@silabs.com>,
	"Bjorn Andersson" <andersson@kernel.org>,
	"Konrad Dybcio" <konradybcio@kernel.org>,
	"Andy Gross" <agross@kernel.org>,
	"Mailing List" <devicetree-spec@vger.kernel.org>,
	netdev@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
	linux-arm-msm@vger.kernel.org, "Janne Grunau" <j@jannau.net>
Subject: Re: [PATCH v4 1/5] dt-bindings: net: Add network-class schema for mac-address properties
Date: Thu, 20 Mar 2025 09:35:43 +0100	[thread overview]
Message-ID: <20250320-cocky-proficient-alligator-5da8a2@krzk-bin> (raw)
In-Reply-To: <20250319-dt-bindings-network-class-v4-1-2329336802b4@ixit.cz>

On Wed, Mar 19, 2025 at 08:42:46AM +0100, David Heidelberg wrote:
> From: Janne Grunau <j@jannau.net>
> 
> The ethernet-controller schema specifies "mac-address" and
> "local-mac-address" but other network devices such as wireless network
> adapters use mac addresses as well.
> The Devicetree Specification, Release v0.3 specifies in section 4.3.1
> a generic "Network Class Binding" with "address-bits", "mac-address",
> "local-mac-address" and "max-frame-size". This schema specifies the
> "address-bits" property and moves the remaining properties over from
> the ethernet-controller.yaml schema.
> 
> The "max-frame-size" property is used to describe the maximal payload
> size despite its name. Keep the description from ethernet-controller
> specifying this property as MTU. The contradictory description in the
> Devicetree Specification is ignored.
> 
> Signed-off-by: Janne Grunau <j@jannau.net>

Incorrect DCO chain, missing SoB.

...

> +  - Devicetree Specification Mailing List <devicetree-spec@vger.kernel.org>
> +
> +properties:
> +  address-bits:
> +    description:
> +      Specifies number of address bits required to address the device described

"Specifies number of address bits required to address the device
described by this node, e.g. size of the MAC address."

And drop the second sentence.

> +      by this node. This property specifies number of bits in MAC address.
> +    default: 48
> +    const: 48
> +

...

> +  mac-address:
> +    description:
> +      Specifies the MAC address that was last used by the boot program. This
> +      property should be used in cases where the MAC address assigned to the
> +      device by the boot program is different from the
> +      local-mac-address property. This property shall be used only if the value
> +      differs from local-mac-address property value.
> +    $ref: /schemas/types.yaml#/definitions/uint8-array
> +    minItems: 6
> +    maxItems: 6
> +
> +  max-frame-size:
> +    $ref: /schemas/types.yaml#/definitions/uint32
> +    description:
> +      Maximum transfer unit (IEEE defined MTU), rather than the
> +      maximum frame size (there\'s contradiction in the Devicetree
> +      Specification).
> +
> +

Just one blank line

> +additionalProperties: true
> 

Best regards,
Krzysztof


  reply	other threads:[~2025-03-20  8:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-19  7:42 [PATCH v4 0/5] dt-bindings: net: Add network-class.yaml schema David Heidelberg via B4 Relay
2025-03-19  7:42 ` [PATCH v4 1/5] dt-bindings: net: Add network-class schema for mac-address properties David Heidelberg via B4 Relay
2025-03-20  8:35   ` Krzysztof Kozlowski [this message]
2025-03-19  7:42 ` [PATCH v4 2/5] dt-bindings: net: Add generic wireless controller David Heidelberg via B4 Relay
2025-03-19  7:42 ` [PATCH v4 3/5] dt-bindings: wireless: bcm4329-fmac: Use wireless-controller.yaml schema David Heidelberg via B4 Relay
2025-03-19  7:42 ` [PATCH v4 4/5] dt-bindings: wireless: silabs,wfx: Use wireless-controller.yaml David Heidelberg via B4 Relay
2025-03-19  7:42 ` [PATCH v4 5/5] dt-bindings: wireless: qcom,wcnss: " David Heidelberg via B4 Relay

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=20250320-cocky-proficient-alligator-5da8a2@krzk-bin \
    --to=krzk@kernel.org \
    --cc=agross@kernel.org \
    --cc=andersson@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=arend@broadcom.com \
    --cc=conor+dt@kernel.org \
    --cc=davem@davemloft.net \
    --cc=david@ixit.cz \
    --cc=devicetree-spec-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=devicetree-spec@vger.kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=edumazet@google.com \
    --cc=j@jannau.net \
    --cc=jerome.pouiller@silabs.com \
    --cc=johannes@sipsolutions.net \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lorenzo@kernel.org \
    --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