From: Vadim Fedorenko <vadim.fedorenko@linux.dev>
To: Dong Yibo <dong100@mucse.com>,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, corbet@lwn.net,
andrew+netdev@lunn.ch, danishanwar@ti.com,
geert+renesas@glider.be, mpe@ellerman.id.au, lorenzo@kernel.org,
lukas.bulwahn@redhat.com
Cc: netdev@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v16 4/5] net: rnpgbe: Add basic mbx_fw support
Date: Tue, 28 Oct 2025 15:17:46 +0000 [thread overview]
Message-ID: <13a02578-c021-4d5f-bf82-1ba6c62c5c90@linux.dev> (raw)
In-Reply-To: <20251027032905.94147-5-dong100@mucse.com>
On 27/10/2025 03:29, Dong Yibo wrote:
> Add fundamental firmware (FW) communication operations via PF-FW
> mailbox, including:
> - FW sync (via HW info query with retries)
> - HW reset (post FW command to reset hardware)
> - MAC address retrieval (request FW for port-specific MAC)
> - Power management (powerup/powerdown notification to FW)
>
> Signed-off-by: Dong Yibo <dong100@mucse.com>
Reviewed-by: Vadim Fedorenko <vadim.fedorenko@linux.dev>
next prev parent reply other threads:[~2025-10-28 15:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-27 3:29 [PATCH net-next v16 0/5] Add driver for 1Gbe network chips from MUCSE Dong Yibo
2025-10-27 3:29 ` [PATCH net-next v16 1/5] net: rnpgbe: Add build support for rnpgbe Dong Yibo
2025-10-27 3:29 ` [PATCH net-next v16 2/5] net: rnpgbe: Add n500/n210 chip support with BAR2 mapping Dong Yibo
2025-10-27 3:29 ` [PATCH net-next v16 3/5] net: rnpgbe: Add basic mbx ops support Dong Yibo
2025-10-27 3:29 ` [PATCH net-next v16 4/5] net: rnpgbe: Add basic mbx_fw support Dong Yibo
2025-10-28 15:17 ` Vadim Fedorenko [this message]
2025-10-27 3:29 ` [PATCH net-next v16 5/5] net: rnpgbe: Add register_netdev Dong Yibo
2025-10-30 2:21 ` Jakub Kicinski
2025-10-30 2:38 ` Yibo Dong
2025-10-30 15:16 ` Jakub Kicinski
2025-10-31 1:44 ` Yibo Dong
2025-10-31 2:05 ` Jakub Kicinski
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=13a02578-c021-4d5f-bf82-1ba6c62c5c90@linux.dev \
--to=vadim.fedorenko@linux.dev \
--cc=andrew+netdev@lunn.ch \
--cc=corbet@lwn.net \
--cc=danishanwar@ti.com \
--cc=davem@davemloft.net \
--cc=dong100@mucse.com \
--cc=edumazet@google.com \
--cc=geert+renesas@glider.be \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo@kernel.org \
--cc=lukas.bulwahn@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/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.