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, avinash.bhatt@intel.com
Subject: [PATCH v2 0/3] wifi: iwlwifi: add Device Tree hardware integration information
Date: Mon, 4 May 2026 12:53:24 +0300 [thread overview]
Message-ID: <20260504095327.30892-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.
Changes in v2:
- Drop mailing list from maintainers in YAML binding
- Drop binding-purpose sentence from description
- Fix dtschema 2026.4 validation errors (items/minItems enforcement)
- Fix yamllint line length violations
- Add driver companion patches (2/3 and 3/3) for reference, showing how
the binding is consumed by the driver; these will be merged through the
regular iwlwifi upstreaming process, not through the DT tree
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: intel,iwlwifi: add binding
wifi: iwlwifi: dt: add Device Tree BIOS configuration infrastructure
wifi: iwlwifi: dt: use Device Tree as fallback BIOS configuration source
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 | 321 ++++++++++++++++++
drivers/net/wireless/intel/iwlwifi/fw/dt.h | 123 +++++++
.../wireless/intel/iwlwifi/fw/regulatory.c | 5 +-
.../wireless/intel/iwlwifi/fw/regulatory.h | 3 +-
7 files changed, 455 insertions(+), 7 deletions(-)
create mode 100644 drivers/net/wireless/intel/iwlwifi/fw/dt.c
create mode 100644 drivers/net/wireless/intel/iwlwifi/fw/dt.h
--
2.34.1
next reply other threads:[~2026-05-04 9:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-04 9:53 Avinash Bhatt [this message]
2026-05-04 9:53 ` [PATCH v2 1/3] dt-bindings: net: wireless: intel,iwlwifi: add binding Avinash Bhatt
2026-05-05 9:15 ` Krzysztof Kozlowski
2026-05-04 9:53 ` [PATCH v2 2/3] wifi: iwlwifi: dt: add Device Tree BIOS configuration infrastructure Avinash Bhatt
2026-05-05 9:18 ` Krzysztof Kozlowski
2026-05-04 9:53 ` [PATCH v2 3/3] wifi: iwlwifi: dt: use Device Tree as fallback BIOS configuration source Avinash Bhatt
2026-05-05 9:19 ` [PATCH v2 0/3] wifi: iwlwifi: add Device Tree hardware integration information Krzysztof Kozlowski
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=20260504095327.30892-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