public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Lorenzo Bianconi <lorenzo@kernel.org>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Christian Marangi <ansuelsmth@gmail.com>,
	Krzysztof Kozlowski <krzk@kernel.org>,
	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>,
	netdev@vger.kernel.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-mediatek@lists.infradead.org
Subject: Re: [PATCH net-next v2 1/2] dt-bindings: net: airoha: npu: Add EN7581-7996 support
Date: Fri, 16 Jan 2026 10:10:55 +0100	[thread overview]
Message-ID: <aWoAnwF4JhMshN1H@lore-desk> (raw)
In-Reply-To: <13947d52-b50d-425e-b06d-772242c75153@lunn.ch>

[-- Attachment #1: Type: text/plain, Size: 2163 bytes --]

> On Wed, Jan 14, 2026 at 11:35:10PM +0100, Lorenzo Bianconi wrote:
> > > > In the current codebase the NPU driver does not need to access the WiFi PCIe
> > > > slot (or any other external device) since the offloading (wired and wireless)
> > > > is fully managed by the NPU chip (hw + firmware binaries).
> > > 
> > > Are you saying the NPU itself enumerates the PCI busses and finds the
> > > WiFi device?  If it can do that, why not ask it which PCI device it is
> > > using?
> > 
> > nope, we do not need any PCI enumeration in the NPU driver at the moment
> > (please see below).
> > 
> > > 
> > > Or this the PCI slot to use somehow embedded within the firmware?
> > 
> > in the current implementation the NPU driver does not need any reference to
> > WiFi or Ethernet devices. The NPU exports offloading APIs to consumer devices
> > (e.g. WiFi or Ethernet devices). In particular,
> > 1- during NPU module probe, the NPU driver configures NPU hw registers and
> >    loads the NPU firmware binaries.
> > 2- NPU consumers (ethernet and/or wifi devices) get a reference to the NPU
> >    device via device-tree in order to consume NPU APIs for offloading.
> > 3- netfilter flowtable offloads traffic to the selected ethernet and/or WiFi
> >    device that runs the NPU APIs accessible via the NPU reference obtained via
> >    dts.
> > 
> > The issue here is the NPU firmware binaries for EN7581, loaded by the NPU
> > driver during NPU probe and used for offloading, depend on the WiFi chipset
> > (e.g. MT7996 or MT7992) available on the EN7581 board (we have two different
> > NPU binaries for MT7996 offloading and for MT7992 offloading).
> 
> Maybe i'm getting the NPU wrong, but i assumed it was directly talking
> to the Ethernet and WiFi device on the PCIe bus, bypassing the host?

correct

> If so, it most somehow know what PCIe slots these devices use?

I have low visibility on the NPU hw internals but I do not think there are
any registers in NPU mmio memory where we can read this info, but I will
confirm it (please remember the fw binaries are not load yet).

Regards,
Lorenzo

> 
>    Andrew

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2026-01-16  9:10 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-13  8:20 [PATCH net-next v2 0/2] airoha: Add the en7581-npu-7996 support Lorenzo Bianconi
2026-01-13  8:20 ` [PATCH net-next v2 1/2] dt-bindings: net: airoha: npu: Add EN7581-7996 support Lorenzo Bianconi
2026-01-14  8:35   ` Krzysztof Kozlowski
2026-01-14  9:01     ` Lorenzo Bianconi
2026-01-14  9:26       ` Krzysztof Kozlowski
2026-01-14 10:09         ` Christian Marangi
2026-01-14 10:34           ` Krzysztof Kozlowski
2026-01-14 10:39             ` Christian Marangi
2026-01-14 15:56               ` Andrew Lunn
2026-01-14 16:29                 ` Christian Marangi
2026-01-14 17:47                   ` Andrew Lunn
2026-01-14 18:16                     ` Lorenzo Bianconi
2026-01-14 20:15                       ` Andrew Lunn
2026-01-14 22:35                         ` Lorenzo Bianconi
2026-01-15 17:50                           ` Andrew Lunn
2026-01-16  9:10                             ` Lorenzo Bianconi [this message]
2026-01-17 17:53                               ` Lorenzo Bianconi
2026-01-17 19:27                                 ` Benjamin Larsson
2026-01-17 22:18                                 ` Andrew Lunn
2026-01-18  0:02                                   ` Benjamin Larsson
2026-01-19 11:07                                   ` Lorenzo Bianconi
2026-01-19 12:03                                     ` Christian Marangi
2026-01-19 14:04                                     ` Andrew Lunn
2026-01-14 10:39             ` Lorenzo Bianconi
2026-01-13  8:20 ` [PATCH net-next v2 2/2] net: airoha: npu: Add en7581-npu-7996 compatible string Lorenzo Bianconi
2026-01-14  0:32   ` Andrew Lunn

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=aWoAnwF4JhMshN1H@lore-desk \
    --to=lorenzo@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=andrew@lunn.ch \
    --cc=ansuelsmth@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=edumazet@google.com \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-mediatek@lists.infradead.org \
    --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