From: Christian Marangi <ansuelsmth@gmail.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
Lorenzo Bianconi <lorenzo@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: Wed, 14 Jan 2026 17:29:28 +0100 [thread overview]
Message-ID: <6967c46a.5d0a0220.1ba90b.393c@mx.google.com> (raw)
In-Reply-To: <76bbffa8-e830-4d02-a676-b494616568a2@lunn.ch>
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.
Do you have any hint on how it's possible to read the PCI
device attached? I'm not aware of any API that can be used
to enumerate what pcie devices is present on the device?
Considering how tightly integrated things are in this SoC
I still feel firmware-names is the most effective solution
for this. The WiFi offload is mostly optional and sadly
due to Airoha limitation, it's not possible to have separate
blob for the single feature/support.
--
Ansuel
next prev parent reply other threads:[~2026-01-14 16:29 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 [this message]
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
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=6967c46a.5d0a0220.1ba90b.393c@mx.google.com \
--to=ansuelsmth@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--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=lorenzo@kernel.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