All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Larsson <benjamin.larsson@genexis.eu>
To: Lorenzo Bianconi <lorenzo@kernel.org>, 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: Sat, 17 Jan 2026 20:27:21 +0100	[thread overview]
Message-ID: <4d4661f9-6820-453a-856f-bf5dedd8fb0b@genexis.eu> (raw)
In-Reply-To: <aWvMhXIy5Qpniv39@lore-desk>

On 17/01/2026 18:53, Lorenzo Bianconi wrote:
> Airoha folks reported the NPU hw can't provide the PCIe Vendor/Device ID info
> of the connected WiFi chip.
> I guess we have the following options here:
> - Rely on the firmware-name property as proposed in v1
> - Access the PCIe bus from the NPU driver during probe in order to enumerate
>    the PCIe devices and verify WiFi chip PCIe Vendor/Device ID
> - During mt76 probe trigger the NPU fw reload if required. This approach would
>    require adding a new callback in airoha_npu ops struct (please note I have
>    not tested this approach and I not sure this is really doable).
>
> What do you think? Which one do you prefer?
>
> Regards,
> Lorenzo

Please note that there might be nothing connected to the pcie bus thus 
nothing to enumerate and the mt76-driver might not be present. (Lots of 
fiber termination only products use this configuration).

For those cases I would prefer the v1 proposal.

MvH

Benjamin Larsson



  reply	other threads:[~2026-01-17 19:27 UTC|newest]

Thread overview: 27+ 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
2026-01-17 17:53                               ` Lorenzo Bianconi
2026-01-17 19:27                                 ` Benjamin Larsson [this message]
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 22:37                         ` Benjamin Larsson
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=4d4661f9-6820-453a-856f-bf5dedd8fb0b@genexis.eu \
    --to=benjamin.larsson@genexis.eu \
    --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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.