[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9340a82a-bae8-4ef6-9484-3d2842cf34aa@lunn.ch>
Date: Wed, 14 Jan 2026 18:47:46 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Christian Marangi <ansuelsmth@...il.com>
Cc: Krzysztof Kozlowski <krzk@...nel.org>,
Lorenzo Bianconi <lorenzo@...nel.org>,
Andrew Lunn <andrew+netdev@...n.ch>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>, netdev@...r.kernel.org,
devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-mediatek@...ts.infradead.org
Subject: Re: [PATCH net-next v2 1/2] dt-bindings: net: airoha: npu: Add
EN7581-7996 support
On Wed, Jan 14, 2026 at 05:29:28PM +0100, Christian Marangi wrote:
> On Wed, Jan 14, 2026 at 04:56:02PM +0100, Andrew Lunn wrote:
> > > > Yes. What you plug into PCI is not a part of this hardware, so cannot be
> > > > part of the compatible.
> > > >
> > >
> > > Thanks for the quick response. Just to make sure Lorenzo doesn't get
> > > confused, I guess a v3 would be sending v1 again (firmware-names
> > > implementation series) with the review tag and we should be done with
> > > this.
> >
> > Since this is a PCI device, you can ask it what it is, and then load
> > the correct firmware based on the PCI vendor:product. You don't need
> > to describe the hardware in DT because it is enumerable.
> >
>
> Hi Andrew,
>
> I think it's problematic to create a bind between the NPU and
> PCIe.
But the NPU must already be bound to PCIe. How else does it know which
PCIe slot the WiFi card is on, so it can make use of it?
Andrew
Powered by blists - more mailing lists