From: Avinash Bhatt <avinash.bhatt@intel.com>
To: devicetree@vger.kernel.org, linux-wireless@vger.kernel.org
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
johannes@sipsolutions.net, miriam.rachel.korenblit@intel.com,
linux-kernel@vger.kernel.org, kobi.guetta@intel.com,
emmanuel.grumbach@intel.com
Subject: [PATCH v3 0/3] wifi: iwlwifi: add Device Tree hardware integration information
Date: Wed, 13 May 2026 09:05:28 +0300 [thread overview]
Message-ID: <20260513060531.8130-1-avinash.bhatt@intel.com> (raw)
Add Device Tree support for Intel Wi-Fi hardware integration information
on platforms that do not provide UEFI variables or ACPI methods.
Patch 1/3 adds the DT binding schema for the Intel iwlwifi compatible
node. Patches 2/3 and 3/3 add the driver infrastructure and integrate
DT as the lowest-priority fallback after UEFI and ACPI; they are
included for reference to show how the binding is consumed by the
driver and will be merged through the regular iwlwifi upstreaming
process, not through the DT tree.
Changes since v2:
Binding (patch 1/3):
- Subject and title updated to describe the BE200 hardware
- Revision header cell removed from all properties; each property is
now a scalar uint32 or plain fixed-size array
- intel,wrds: reduced to 49 cells (mode word + 4x12 SAR values)
- intel,uats: reduced to 338 bytes (26x13 country nibble matrix)
- Removed allOf/items const: 0 constraints from all properties
- intel,srd: changed from integer enum to string enum
(active-scan/passive-scan/disabled)
- Removed "reserved, must be 0" annotations; bits with no assigned
meaning are not documented
- Added allOf: $ref: /schemas/net/wireless/ieee80211.yaml#
Driver (patch 2/3):
- Removed dsm_func_to_prop_name() and all IWL_DT_PROP_* defines;
each property function now calls of_property_read_*() directly with
the literal property string
- Driver updated to match binding changes (no revision cells,
string-based intel,srd, scalar uint32 DSM properties, 338-byte
intel,uats)
- Added iwl_dt_init() to validate DT node compatible at probe time;
all DT reads gated on fwrt->dt_compatible
- fw/dt.h now includes fw/runtime.h directly, making it self-contained
Fallback integration (patch 3/3):
- No changes from v2
Link to v2: https://patchwork.kernel.org/project/linux-wireless/patch/20260504095327.30892-1-avinash.bhatt@intel.com/
Link to v1: https://patchwork.kernel.org/project/linux-wireless/patch/20260429081403.46087-2-avinash.bhatt@intel.com/
Link to RFC: https://patchwork.kernel.org/project/devicetree/patch/20260408055709.11579-2-avinash.bhatt@intel.com/
Avinash Bhatt (3):
dt-bindings: net: wireless: Add Intel Wi-Fi 7 BE200 PCIe adapter
wifi: iwlwifi: dt: add Device Tree BIOS configuration infrastructure
wifi: iwlwifi: dt: use Device Tree as fallback BIOS configuration source
.../bindings/net/wireless/intel,iwlwifi.yaml | 248 +++++++++++++++++
MAINTAINERS | 1 +
drivers/net/wireless/intel/iwlwifi/Makefile | 1 +
drivers/net/wireless/intel/iwlwifi/fw/acpi.h | 5 +-
.../wireless/intel/iwlwifi/fw/api/nvm-reg.h | 4 +-
drivers/net/wireless/intel/iwlwifi/fw/dt.c | 332 +++++++++++++++++++
drivers/net/wireless/intel/iwlwifi/fw/dt.h | 161 +++++++++
drivers/net/wireless/intel/iwlwifi/fw/init.c | 4 +-
.../wireless/intel/iwlwifi/fw/regulatory.c | 3 +++
.../wireless/intel/iwlwifi/fw/regulatory.h | 3 +-
drivers/net/wireless/intel/iwlwifi/fw/runtime.h | 6 +-
drivers/net/wireless/intel/iwlwifi/mld/mld.c | 3 +++
.../intel/iwlwifi/mld/regulatory.c | 5 ++-
13 files changed, 772 insertions(+), 11 deletions(-)
--
2.34.1
next reply other threads:[~2026-05-13 6:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-13 6:05 Avinash Bhatt [this message]
2026-05-13 6:05 ` [PATCH v3 1/3] dt-bindings: net: wireless: Add Intel Wi-Fi 7 BE200 PCIe adapter Avinash Bhatt
2026-05-13 6:05 ` [PATCH v3 2/3] wifi: iwlwifi: dt: add Device Tree BIOS configuration infrastructure Avinash Bhatt
2026-05-13 6:05 ` [PATCH v3 3/3] wifi: iwlwifi: dt: use Device Tree as fallback BIOS configuration source Avinash Bhatt
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=20260513060531.8130-1-avinash.bhatt@intel.com \
--to=avinash.bhatt@intel.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=emmanuel.grumbach@intel.com \
--cc=johannes@sipsolutions.net \
--cc=kobi.guetta@intel.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=miriam.rachel.korenblit@intel.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