On Tue, Jan 13, 2026 at 09:20:27AM +0100, Lorenzo Bianconi wrote:

quoted

Introduce en7581-npu-7996 compatible string in order to enable MT76 NPU
offloading for MT7996 (Eagle) chipset since it requires different
binaries with respect to the ones used for MT7992 on the EN7581 SoC.

Signed-off-by: Lorenzo Bianconi <lorenzo@kernel.org>
---
 Documentation/devicetree/bindings/net/airoha,en7581-npu.yaml | 1 +
 1 file changed, 1 insertion(+)

diff --git a/Documentation/devicetree/bindings/net/airoha,en7581-npu.yaml b/Documentation/devicetree/bindings/net/airoha,en7581-npu.yaml
index 59c57f58116b568092446e6cfb7b6bd3f4f47b82..96b2525527c14f60754885c1362b9603349a6353 100644
--- a/Documentation/devicetree/bindings/net/airoha,en7581-npu.yaml
+++ b/Documentation/devicetree/bindings/net/airoha,en7581-npu.yaml

@@ -18,6 +18,7 @@ properties:
   compatible:
     enum:
       - airoha,en7581-npu
+      - airoha,en7581-npu-7996

This does not warrant new compatible. There is some misunderstanding and
previous discussion asked you to use proper compatible, not invent fake
one for non-existing hardware.  Either you have en7996-npu or
en7581-npu. Not some mixture.

Hi Krzysztof,

We need to specify which fw binaries the airoha NPU module should load
according to the MT76 WiFi chipset is running on the board (since the NPU
firmware images are not the same for all the different WiFi chipsets).
We have two possible combinations:
- EN7581 NPU + MT7996 (Eagle)
- EN7581 NPU + MT7992 (Kite)

Please note the airoha NPU module is always the same (this is why is just
added the -7996 suffix in the compatible string). IIUC you are suggesting
to use the 'airoha,en7996-npu' compatible string, right?

Regards,
Lorenzo

Best regards,
Krzysztof