From: <han.junyang@zte.com.cn>
To: <andrew+netdev@lunn.ch>, <davem@davemloft.net>,
<edumazet@google.com>, <kuba@kernel.org>, <pabeni@redhat.com>,
<horms@kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <netdev@vger.kernel.org>,
<han.junyang@zte.com.cn>, <ran.ming@zte.com.cn>,
<han.chengfei@zte.com.cn>, <zhang.yanze@zte.com.cn>
Subject: [PATCH net-next v2 0/3] dinghai: firmware handshake, MSI-X pools and async event queues
Date: Fri, 11 Sep 2026 11:56:32 +0800 (CST) [thread overview]
Message-ID: <20260911115632342CS2YMSVejTTmnYEU3XbRs@zte.com.cn> (raw)
From: Junyang Han <han.junyang@zte.com.cn>
This series continues the DingHai (ZXDH) PF driver bring-up: after PCI
probing, it verifies the firmware version contract, waits for the
RISC-V management core to become ready, sets up the MSI-X interrupt
pools, and creates the async event queues through which the firmware
will report events.
Some notes on the IRQ design:
The vector space is partitioned into per-purpose pools (async, RDMA,
vq). Event queues share a vector through an atomic notifier chain
attached to the IRQ, and the sharing degree is governed by pool
thresholds. The IRQ table hangs off a void *priv in the shared core
device: the PF, MPF and SF core devices each carry a different pool
layout behind that pointer, so a type-specific struct in en_pf.c keeps
the shared header free of PF-only details.
Changes in v2:
- Convert both firmware readiness polls to readx_poll_timeout()
(Andrew Lunn).
- Read the fw compat block field by field through ioread*() accessors
instead of an ioread32_rep() bulk copy, which misplaces the u8/u16
fields on big-endian; no __le annotations are needed since each
accessor converts from little-endian (Andrew Lunn).
- Use kref for the IRQ reference count (Andrew Lunn).
Junyang Han (3):
dinghai: add firmware version check and RISC-V readiness polling
dinghai: add MSI-X interrupt pools
dinghai: add async event queue for firmware notifications
drivers/net/ethernet/zte/dinghai/Makefile | 2 +-
drivers/net/ethernet/zte/dinghai/en_pf.c | 225 +++++++++++
drivers/net/ethernet/zte/dinghai/en_pf.h | 57 +++
drivers/net/ethernet/zte/dinghai/zxdh_eq.c | 145 +++++++
drivers/net/ethernet/zte/dinghai/zxdh_eq.h | 61 +++
drivers/net/ethernet/zte/dinghai/zxdh_irq.c | 412 ++++++++++++++++++++
drivers/net/ethernet/zte/dinghai/zxdh_irq.h | 72 ++++
7 files changed, 973 insertions(+), 1 deletion(-)
create mode 100644 drivers/net/ethernet/zte/dinghai/zxdh_eq.c
create mode 100644 drivers/net/ethernet/zte/dinghai/zxdh_eq.h
create mode 100644 drivers/net/ethernet/zte/dinghai/zxdh_irq.c
create mode 100644 drivers/net/ethernet/zte/dinghai/zxdh_irq.h
--
2.27.0
next reply other threads:[~2026-09-11 3:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-11 3:56 han.junyang [this message]
2026-09-11 3:59 ` [PATCH net-next v2 1/3] dinghai: add firmware version check and RISC-V readiness polling han.junyang
2026-09-14 7:20 ` Simon Horman
2026-09-11 4:02 ` [PATCH net-next v2 2/3] dinghai: add MSI-X interrupt pools han.junyang
2026-09-14 7:20 ` Simon Horman
2026-09-11 4:05 ` [PATCH net-next v2 3/3] dinghai: add async event queue for firmware notifications han.junyang
2026-09-14 7:20 ` Simon Horman
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=20260911115632342CS2YMSVejTTmnYEU3XbRs@zte.com.cn \
--to=han.junyang@zte.com.cn \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=han.chengfei@zte.com.cn \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=ran.ming@zte.com.cn \
--cc=zhang.yanze@zte.com.cn \
/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
all inboxes | Powered by JetHome®