From: Krzysztof Kozlowski <krzk@kernel.org>
To: Lorenzo Bianconi <lorenzo@kernel.org>
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>,
Simon Horman <horms@kernel.org>, Felix Fietkau <nbd@nbd.name>,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, netdev@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH net-next v5 1/7] dt-bindings: net: airoha: npu: Add memory regions used for wlan offload
Date: Fri, 25 Jul 2025 09:11:54 +0200 [thread overview]
Message-ID: <20250725-amiable-strict-pudu-5cce71@kuoka> (raw)
In-Reply-To: <20250723-airoha-en7581-wlan-offlaod-v5-1-da92e0f8c497@kernel.org>
On Wed, Jul 23, 2025 at 07:19:50PM +0200, Lorenzo Bianconi wrote:
> Document memory regions used by Airoha EN7581 NPU for wlan traffic
> offloading. The brand new added memory regions do not introduce any
> backward compatibility issues since they will be used just to offload
> traffic to/from the MT76 wireless NIC and the MT76 probing will not fail
> if these memory regions are not provide, it will just disable offloading
> via the NPU module.
>
> Signed-off-by: Lorenzo Bianconi <lorenzo@kernel.org>
> ---
> .../devicetree/bindings/net/airoha,en7581-npu.yaml | 19 +++++++++++++++----
> 1 file changed, 15 insertions(+), 4 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/net/airoha,en7581-npu.yaml b/Documentation/devicetree/bindings/net/airoha,en7581-npu.yaml
> index 76dd97c3fb4004674dc30a54c039c1cc19afedb3..f99d60f75bb03931a1c4f35066c72c709e337fd2 100644
> --- a/Documentation/devicetree/bindings/net/airoha,en7581-npu.yaml
> +++ b/Documentation/devicetree/bindings/net/airoha,en7581-npu.yaml
> @@ -41,9 +41,18 @@ properties:
> - description: wlan irq line5
>
> memory-region:
> - maxItems: 1
> - description:
> - Memory used to store NPU firmware binary.
I still do not get why this cannot be kept backwards compatible. I
looked at your driver code and NPU offload support RFC, and they look
correct. Yet what stops any future developer from changing:
mt76_npu_init(mdev, pci_resource_start(pdev, 0),
pdev->bus && pci_domain_nr(pdev->bus) ? 3 : 2);
into:
ret = mt76_npu_init(...)
if (ret)
goto err...;
? Why would anyone NOT DO such change in the future?
I think I asked about this last time as well - why you cannot keep new
entries optional (minItems: 1)?
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-07-25 7:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-23 17:19 [PATCH net-next v5 0/7] net: airoha: Introduce NPU callbacks for wlan offloading Lorenzo Bianconi
2025-07-23 17:19 ` [PATCH net-next v5 1/7] dt-bindings: net: airoha: npu: Add memory regions used for wlan offload Lorenzo Bianconi
2025-07-25 7:11 ` Krzysztof Kozlowski [this message]
2025-07-23 17:19 ` [PATCH net-next v5 2/7] net: airoha: npu: Add NPU wlan memory initialization commands Lorenzo Bianconi
2025-07-23 17:19 ` [PATCH net-next v5 3/7] net: airoha: npu: Add wlan_{send,get}_msg NPU callbacks Lorenzo Bianconi
2025-07-24 10:09 ` Vadim Fedorenko
2025-07-27 8:42 ` Lorenzo Bianconi
2025-07-23 17:19 ` [PATCH net-next v5 4/7] net: airoha: npu: Add wlan irq management callbacks Lorenzo Bianconi
2025-07-23 17:19 ` [PATCH net-next v5 5/7] net: airoha: npu: Read NPU wlan interrupt lines from the DTS Lorenzo Bianconi
2025-07-23 17:19 ` [PATCH net-next v5 6/7] net: airoha: npu: Enable core 3 for WiFi offloading Lorenzo Bianconi
2025-07-23 17:19 ` [PATCH net-next v5 7/7] net: airoha: Add airoha_offload.h header Lorenzo Bianconi
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=20250725-amiable-strict-pudu-5cce71@kuoka \
--to=krzk@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=lorenzo@kernel.org \
--cc=nbd@nbd.name \
--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