[RFC PATCH 0/1] dt-bindings: net: wireless: intel,iwlwifi: add binding

[Avinash Bhatt <avinash.bhatt@intel.com>]

Hi DT maintainers and community,

We are the Intel wireless LAN driver team (iwlwifi). This is our first
attempt at a Device Tree binding and we are posting this RFC well ahead
of any formal submission to get early guidance and feedback.

Background:

Intel discrete Wi-Fi adapters are traditionally configured by platform
firmware via ACPI DSM methods. As ARM64 and other non-x86 platforms
gain adoption, we want to support platforms that use Device Tree instead
of ACPI for providing this OEM configuration data (SAR power limits,
regulatory overrides, 6 GHz country enablement, etc.).

Scope of this RFC:

This binding currently covers only the Wi-Fi 7 BE200 adapter (PCI ID
8086:272b). Support for other Intel discrete Wi-Fi devices may be added
in future revisions as we validate the binding on additional platforms.
Similarly, the set of properties documented here reflects what we have
implemented today -- some properties may be revised, renamed, or
extended based on feedback before the final submission.

What we are looking for:

 - Feedback on the overall approach and whether the property
   naming/structure follows DT conventions
 - Any concerns about the layout of multi-cell properties (revision +
   bitmap pattern used throughout)
 - Guidance on anything that would prevent this from being accepted
   upstream

The patch passes `make dt_binding_check` cleanly.

As this is our first DT binding submission, any feedback on conventions
or best practices we may have missed is very welcome.

Thanks in advance for your time,
Avinash Bhatt
Intel Wireless LAN Team

Avinash Bhatt (1):
  dt-bindings: net: wireless: intel,iwlwifi: add binding

 .../bindings/net/wireless/intel,iwlwifi.yaml  | 413 ++++++++++++++++++
 1 file changed, 413 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/net/wireless/intel,iwlwifi.yaml

--
2.34.1